WRITING & NOTES
Perspectives on software, AI, and the responsibility that comes with making technical decisions.
FIELD NOTES / 2026
Longer pieces on delivery, AI-assisted engineering, and the judgement that has to sit behind both.
I caught my AI writing notes for itself. Not just about my code. About me. Meet the Project Brain: a folder of markdown in every repo that carries our decisions, the pitfalls we already paid for, and the WHY from one story to the next.
Read the pieceNobody sets out to slow progress down. Alignment meetings, architecture reviews, risk controls and sprint planning each make sense on their own, but together they stretch momentum thin. Faster to Value is about creating space where execution happens closer to the moment an idea appears.
Read the pieceI can manage one or two deep AI workflows at a time if I start early. Beyond that, my brain pushes back — not because the AI is underperforming, but because the accountability never switches off. Prompting feels like an early interface, not a permanent one.
Read the pieceSomewhere between spicy autocomplete and the dark factory sits an honest question: where are we actually right now? For me it is rails everywhere — agent contracts, policy gates, architecture validation — and a human still carrying the decision.
Read the pieceIDEAS FROM MY RECENT LINKEDIN WRITING
AI can challenge your thinking and help you structure feedback. Before it becomes your advice, read it, verify it, and decide whether you stand behind it.
More tokens and more agents are not automatically better engineering. Use the tools where they create value, with attention to budget, context, and the work that follows.
Build early, release responsibly, and learn from actual use. Systems thinking and clarity of direction matter as much as the speed of producing code.
THE ARCHIVE / 2019
Original articles, kept at their existing addresses. Some opinions and project details belong to the time they were written.