Risk-oriented enterprise teams may block AI coding agents (and agents in general) based on fear of the unknown while ignoring fundamental controls that actually reduce blast radius. The real risk isn't the agent—it's the policy friction that lets competitors ship while you debate.

For years my blog ran Bootstrap 3.2.0 despite needing almost none of it. A single day with Claude Code fixed that—and a whole lot more.

Startups scout ahead, big companies follow. The AI developer tools market is playing out the Innovator's Dilemma in real-time—and we're all just deciding between Quarter Pounders and Whoppers.

I want you to imagine the place that you live in.

I have a confession to make...

I created an OpenID Connect and OAuth spec graph in a Mermaid diagram in a GitHub repository.

LLMs didn't make code literacy optional—they raised the bar for what you need to learn so that you can effectively steer these AI assisted tools.

Asking an AI agent a question is a whole different ballgame from letting it take action.

Or: why your "just grab every Slack link since 2017" request is going to hurt.

I was on a call with a colleague, walking through some Wardley Maps I'd drawn for various AI tools. Partway through my overview, he stopped me and asked a question I've heard a couple of times before: "How do you find out about these things?" I paused, realizing that the answer has less to do with any magic trick and more to do with habits— essentially, what I choose to read, watch, and listen to on a daily basis. In other words, it comes down to my information diet.