AI

Your team closed 47 tickets last sprint. Deployment frequency is up. Lead time is down. The sprint review looked clean. And you have no idea whether your team is getting better at what matters. Every metric on that dashboard measures motion. None of them measures whether the team made the right decision. In an era where AI generates the first draft of almost everything, code, architecture proposals, incident summaries, and product specs, that gap is no longer academic. It is the difference between a team that compounds in judgment and a team that accelerates toward the wrong destination. ...

For decades, the path was obvious. A junior engineer joined a team, got handed a bug nobody else wanted, fixed it, broke something else, fixed that too, and over a few years accumulated the scar tissue that turned into judgment. Senior engineers were not trained; they were grown, slowly, by the system itself. That system has stopped working at both ends. At the entry point, juniors aren’t being hired. AI makes a senior dramatically more productive and a junior only marginally so, which makes the rational move, for any single team, in any single quarter, to skip the junior hire and let an experienced engineer with AI do the work two juniors used to do. Industry-wide, the pipeline is being shut off before it starts. ...

The Lesson That Used to Be Unavoidable Every senior engineer I respect has a similar war story. They wrote a Python script that was too slow, and someone told them to learn what a list comprehension actually does under the hood. They built a React app that re-rendered itself into a coma, and they had to crawl back into the DOM to figure out why. They shipped a service that fell over the first time real traffic hit it, and they spent a weekend learning what a connection pool is. ...

Working with AI to generate code is extremely satisfying. In a matter of minutes, you get something that looks great and, in most cases, does what you wanted it to do and even more. But many times, what looks ready for production is far from being production-safe. A large-scale study conducted by two researchers at FernUniversität in Hagen analyzed 7,703 files from public GitHub repositories explicitly attributed to AI tools. Using CodeQL, the researchers identified 4,241 CWE instances across 77 different vulnerability types. While 87.9% of the analyzed AI-generated code contained no identifiable CWE-mapped vulnerabilities, the risk came from code that appeared to work fine. It compiled, it solved the visible task, but it still carried hidden assumptions, unsafe patterns, and security debt. ...

I recently argued on the JFrog blog that trusted AI requires more than model quality. It requires visibility, provenance, governance, and a real system of control around the things models consume, build, and ship. That is the foundation. This post is about what you build on top of it. Because visibility is necessary. Without it, you cannot govern anything. If you cannot see which models are running, where they came from, how they behave, and what they touch, you do not have a governance posture. You have hope dressed up as architecture. ...

A developer recently gave Claude Code write access to a live Meta Ads account. The agent’s read-only analysis was genuinely valuable; it correctly identified the cheapest campaign as having the worst ROI. The insight was good. The judgment about what to do next was absent. The agent executed autonomously, triggered API rate limits through automated publishing, and resulted in the account being permanently banned. The read was right, the write destroyed the business relationship. ...

Anyone Can Prompt. Not Everyone Can Engineer. What the AI coding revolution actually changes, and what it doesn’t. The Translation Layer Is Gone I recently watched an IBM video that made a point I’ve been thinking about ever since. The speaker walked through the entire history of programming languages, from machine code and assembler, through COBOL and FORTRAN, to object-oriented, web, and scripting languages, and made a simple observation: every generation moved a little closer to the way humans actually think and speak. ...

What Is This Chronicles of the Elder Realm is a solo high-fantasy text adventure powered by AI. You create a hero, get three AI-generated companions, and explore a procedurally generated world. An AI Dungeon Master narrates the story, runs combat, and reacts to everything you do. The game is built with vanilla JavaScript, runs entirely in the browser, and is fully open source. Play the Game Note: You’ll need an API key from one of the supported AI providers (Anthropic Claude, OpenAI, Google Gemini, or xAI Grok) to play. Enter it in the game’s Settings screen. Your key stays in your browser and is never sent anywhere except the AI provider. ...

This week I wanted to take a little break from the heavy stuff. It has been a month, the war is still raging, and me, my wife, and our four kids are still at home. I have been doing my best to balance, well, everything. Work, family, stress, routine, and the constant background noise of reality. I needed a bit of an escape. When I was younger, meaning about five minutes ago 😄, I really loved quest games. I also played a bit of Dungeons & Dragons when I was young. With the progress of AI, I kept thinking how cool it would be to use AI as the dungeon master. A quick Google search makes it clear that I am definitely not the only person who had this idea. But still, I have Claude, so why not just build it myself? ...

A recent Sequoia piece made an argument that immediately felt familiar to me. Not because it repeated the phrase “Judgment Driven Development” word for word. But because it pointed at the same shift from a different direction. The article is here: Services: The New Software. Its claim is simple: the next generation of great companies may not look like software vendors at all. They may look like software and AI powered service providers. Instead of selling tools to people who do the work, they will sell the work itself. Instead of selling accounting software, they will close the books. Instead of selling legal tooling, they will draft the NDA. Instead of helping a team perform a process faster, they will increasingly perform the process directly. ...