
Why Your AI Strategy Is Three-Quarters Wrong
Everyone's talking about AI productivity. Ship faster. Write more code. Automate the boring stuff. Kill the developers (well, kind of). And sure, that's real — I've seen it myself, having built several Claude Code plugins for my team at Dow Jones. AI genuinely makes you faster. But here's the thing: if your entire AI strategy is "make developers more productive," you're focusing on one quarter of the picture and ignoring the three quarters that actually matter for the long-term health of your engineering organisation. Bold claim? Absolutely. Let me earn it. The knowledge problem nobody talks about Before we get to AI, let me ask you something. Think about the best engineer you've ever worked with. The one who, when a production incident happens at 2 AM, somehow knows where the problem is before anyone else has finished reading the logs. The one who reviews your pull request and spots the architectural issue you didn't even know existed. Now ask yourself: how much of what makes that eng
Continue reading on Dev.to
Opens in a new tab


