Blog

  • Spec-Driven Development: Hands-On Lifecycle Guide

    This walkthrough is written from the perspective of the person who owns the requirements: the Business Analyst, Product Owner or Product Manager. The team, adoption and presentation sections are also useful to Project Managers planning how SDD fits delivery. 1. What SDD is, in one picture In spec-driven development the spec, not the code, is…

    Continue reading →

  • Do we need a frontend at all?

    Every organisation has a legacy application that people depend on, that badly needs a refresh, and whose ageing technology makes that refresh hard to do. The instinct is to rebuild the interface on something modern. Before committing to that, I wanted to check an assumption hiding inside it — that the answer to a bad…

    Continue reading →

  • A day with an undocumented legacy app

    Most companies have one. Critical to the business, running on a frontend that aged badly, and documented nowhere. Replacing it gets discussed every year and never scoped, because nobody can say what it would take. I ran an experiment on one of them with Claude, to find out whether that question was actually hard or…

    Continue reading →

  • The cat sat on the…

    There are many ways to explain AI. Neural networks. Transformers. Large language models. Attention mechanisms. Embeddings. Agents. RAG. MCP. And, if you want to keep things simple, use that one example everyone loves: “The cat sat on the…” You’ve probably seen it. It’s one of those wonderfully simple examples used to explain how language models…

    Continue reading →

  • The AI Service Desk: Filling the L1 Gap Before You Hire for It

    It starts with “just a quick question” Every product and engineering team knows the pattern. Someone pings a chat thread with “I need a new ___”, “I have a problem with ___”, or “can you check the ___”. Then comes the back-and-forth: what exactly is broken, which environment, did it ever work, what did you…

    Continue reading →

  • Infobip Shift 2026 / conference recap

    Five themes dominated the sessions I attended, below are my thoughts. https://shift.infobip.com/ The sessions on AI-assisted development confirmed something I’d already tested myself. I’ve published small apps this way, but the real value for me is speed to a working artifact — a demo, a prototype, a proof of concept I can put in front…

    Continue reading →

  • A feature engineering experiment from my garden

    Can AI tell good Ajvar from bad Ajvar? This year, I grew vegetables, again. Nothing particularly revolutionary about that. Mostly peppers, and a few other things. Then came the inevitable question: What do you actually do with all of it? The answer, at least in this part of Europe, is obvious: Make ajvar. But while…

    Continue reading →

  • AI is not a feature strategy

    A chatbot here.A recommendation engine there.AI-generated content.A predictive model.A copilot added to an existing product. It looks like progress. But adding AI to products is not the same as having an AI strategy. Features answer “what?” An AI feature strategy usually starts with a technology: “Where can we add AI to our product?” This can…

    Continue reading →

  • What actually happens inside a neural network

    Most explanations stop at the diagram or jump straight to the calculus. I wanted the bit in between, so I animated it. Six minutes, eight examples. One real input travels through a five-layer network, every weighted sum resolves into an actual number, the loss gets calculated, and the error flows back through every weight. Then…

    Continue reading →

  • I built a Chrome extension so I could stop reading clickbait

    My first published extension. Vibe coded, built for myself, now yours too. Every morning I do the same thing: coffee, then three or four news portals. And most mornings I end up annoyed. Half the headlines are clickbait. Of the ones that aren’t, plenty bury the single sentence that actually matters at the very end,…

    Continue reading →