You don't need a harness
Why "you don't need a harness" makes sense for someone working on frontier models, but not as general advice, and which parts of a harness are worth keeping.
Software, mostly
I write about software development. Not often: only when I feel like it and when I think I have something worth sharing.
Recent
Why "you don't need a harness" makes sense for someone working on frontier models, but not as general advice, and which parts of a harness are worth keeping.
Sometimes we don't need ultra-sophisticated machinery to run a discovery exercise on legacy software, and AI can be a great help.
Events can reduce coupling, absorb load and help systems scale, but you pay for them in complexity.
We picked practices by weighing cost against benefit, and AI has changed both sides of the scale. A tour of which practices get cheaper, which feed the model's context and tools, and where to be careful.
Vague claims like some users are affected need enough context before they can support a decision.
The actor model is old, simple and rarely used. Its two primitives, how it handles concurrency, and how I used it in Akka.NET to build a small monitoring tool for on-premise installations.