Blog

By 2030, software engineers will abandon traditional coding in IDEs to instead use AI agents as navigators, fundamentally transforming how code gets written.

When I volunteered at Coderdojo, we taught kids to code. In 80% of the cases, that meant building video games with Scratch. While that is cool, the coaches got really excited when a child wanted to do something more exotic. Unity, robotics, or even just JavaScript. Finally, something they could also sink their tech teeth into! I remember a girl who wanted to build a robot. The volunteers got fired up. We brought Arduino kits and soldering material. We wanted children to short-circuit and burn LED lights to teach them how electronics worked. Quite a few of them did. ...

Using Claude Code to drive Gemini’s image generation for consistent animated sprites, recreating the classic Flying Toasters screensaver.

Like all online topics these days, coding agents are divisive. Some zealots predicted the end of the software developer around 8 months ago. Others consider those agents to be as useless and atrocious as Microsoft Teams. Most of us are somewhere on the spectrum between those extremes. Over the last few weeks, I have been taking advantage of Anthropic’s holiday offerings and have been spending an unhealthy amount of time with Claude Code. It’s fun, it’s productive, but it also teaches us something about the state of the art. Or rather: about the perceived state of the art. ...

A retro arcade shooter where Claude Code wrote all the game code and DALL-E generated every sprite. No human code written.

Predictions about AI development over the coming year — CLI agents will dominate, AI generators will become standard, and LLM improvements will plateau.

The weary pilgrim tosses his last coin into the well, whispering his deepest desire to the dark waters. He hopes some hidden magic might make it real. The dream of the wishing well is as old as humanity. The genie in the bottle, the magic wand, the monkey’s paw. People have always wanted to speak their desires into existence. AI code generators like Lovable or V0 are just the latest way to meet this age-old desire. ...

Organizations should evaluate AI tools based on compliance, community support, and team management capabilities — not just productivity gains.

There’s a world of difference between Andrej Karpathy’s vibe coding and the kind you’d see from most product managers. The former understands what the machine is doing under the hood. The latter talks about specs without understanding the inner workings of the product increment. A better name for that workflow would be “blind vibe coding”. It’s hard to overstate just how different non-techies talk to their Cursor agent. From the original prompt to the intermediate feedback, a technical background makes everything easier, more informed and better. It’s tough to put myself in the shoes of those who lack those technical chops. ...

AI tools are overhyped, but their results undeniable. They turbocharge software engineers. Product managers, on the other hand, struggle to find the same productivity boost. Sure, they can create an interactive mockup in Lovable, but that’s of very limited use on brownfield products. So what can a PM do? There is a tempting, popular idea out there that leads to a dead-end street. The cardinal sin of AI-powered product management is having Claude generate your Product Requirement Documents for you. It’s unfortunate how popular that sin is getting. ...