Insights
Notes from building software that has to keep working
Written by the people doing the work, about problems we have actually hit. No listicles, no AI-generated filler.
Web6 min read
SEO, AEO and GEO: what actually changed
Answer engines and AI assistants changed how content gets found and cited. A practical guide to what is genuinely different and what is unchanged fundamentals.
ReadAI5 min read
How to tell if an AI feature is worth building
A practical test for AI proposals: measure the manual baseline first, define the cost of being wrong, and check whether a human can verify the output cheaply.
ReadERP6 min read
Ship your ERP one module at a time
Big-bang ERP launches fail for structural reasons, not technical ones. Incremental module delivery fixes the incentives — here is how to sequence it.
ReadNext step
Got a question none of these answer?
Ask it directly. If the answer is useful to other people we will probably write it up.
- 01An engineer reads itUsually within one business day.
- 02A 30-minute callProcess, constraints, deadline.
- 03An honest answerA way forward, or a clear no.