Articles
Short essays on shipping software, prompting, and engineering practice. Written for engineers who'd rather read code than hot takes about it.
Field perspective · Part 2
A specific category of engineering investment — the elaborate techniques built to compensate for code’s rigidity — has stopped paying for itself. Identifying which parts of a stack still need it, and which parts were over-built for flexibility that never arrived, is now one of the more valuable things a team can do.
Field perspective · Part 1
Your company already records almost everything it says to itself. AI can now read all of it at once — and the organisations that move first will see themselves more clearly than their competitors can.
From the trenches · Part 1
A short reflection on building a small but realistic AI assistant where the customer’s data never leaves their own infrastructure — and what that constraint reveals about the modern AI stack.
by Dr Martin Bosticky
The Pragmatic Prompter · Part 1
Most AI-generated code looks plausible, compiles fine, and then slowly poisons your codebase with hallucinated assumptions. Three structural prompt changes fix that — before a single line gets written.
by ru5ty