2026-10 - W2
Structured Concurrency Looms - YouTube
Maybe we’ll have the structured concurrency in java 28??? 🤞
If you thought the speed of writing code was your problem, you have bigger problems - Andrew Murphy - YouTube
Theory of Constraints: Every system has exactly one constraint. The throughput of the system is determine by the throughput of that constraint. Optimising anything that is not the constraint doesn’t just fail to help. It makes the system worse, more WIP, deeper queues, older context, later feedback.
I’m sorry, but you still have to think | It’s all about the bit
You still have to think critically. It’s good to know what you’re doing. Don’t make hasty assumptions based on a single metric. If you want a reliable system you should know when to fail. Also, benchmarks are hard.
Living in the Weimar era of Ruby - Julik Tarkhanov
How to effectively debug when you no longer understand the code
Really long essay, but worth your time.
Are Harnesses Worth the Cost?
What changes with model capability is not whether independent sensors are needed, but when they run. For models whose unaided attempts produce inconsistent outcomes, running sensors continuously during development provides executable attention that broadens the set of models a team can use successfully. For frontier models capable of solving the brief in one pass, running those same sensors once as an independent final acceptance gate provides the verification every system requires without the development overhead.
Redesigning source control at Anthropic \ Anthropic
Interesting read.
Fancy Curl Sites
That’s… a neat way of reading a website. Awesome from a terminal guy.
Recreational Programming - Christopher Phiri
red — Vim keys. Agent inside.
Interesting editor.
Le logiciel propriétaire, c’est terminé ? | Eventuallycoding
There are indeed more and more personal software being created.
GitHub - CLoaKY233/siltop: Terminal system monitor for Apple Silicon Macs: CPU, GPU, power, temperatures, processes.
An alternative to btop, but for Macs.
Speeding up code review with `small-change` | Irrational Exuberance
PR avalanche mitigation, from Will Larson. Not much ground breaking discovery, just doing like everyone else, by classifying PRs.
The Brain Sandwich – Terrible Software
Interesting wording.
The idea is very simple, and can be summarized by: whenever you work on something, you should use:
- Your brain, and then
- AI, and then
- Your brain
How to be more ambitious: A tutorial for humans with models
I think of ambition in four types: Speed, Altitude, Depth, and Range.
- Speed: The same work in less time, the bread and butter for AI’s economic value: If you need some code written, I’ll do it faster with Claude. Well established and requires little creativity in how you approach AI, so I’ll skip this one.
- Altitude: Going up in abstraction and considering the outcome rather than the individual task.
- Depth: Considering a task the way a field-leading expert would. Rather than operating at the task’s layer, we go one level deeper and touch the underlying data, tools, and problems.
- Range: Drawing on multiple fields rather than just the one the task might need at the surface, using knowledge, tools, and techniques you normally wouldn’t.