// ARTICLES
Practical notes on AI-assisted engineering, Rust, systems, and the habits behind better software work.
Article
Most mornings used to cost me twenty minutes before I'd written a line of code. Calendar, Gmail, Slack, the CI dashboard, the Notion page holding the running plan — five surfaces, all telling me different fragments of the same story, all needing reconciliation in my head.
Article
Last Tuesday I asked Claude to "review the auth module." Eight months ago that prompt would have given me a thoughtful walk-through — flagged the obvious issues, made a few suggestions I half-expected. This time I got six generic bullets. Two were useful. The rest read like checklist filler someone left in the room.
Article
I open a new Claude Code session. I ask it to refactor the auth flow before the next release. It comes back with a clean, well-structured answer that uses none of my existing helpers, contradicts my session model, and quietly assumes JWTs when I've been on opaque tokens for two years.
Article
You opened Claude Code this morning and typed the same context you typed yesterday: stack rules, error handling, review preferences, and what not to touch. By lunch, you had repeated a version of that preamble four more times.
Article
Most mornings used to cost me twenty minutes before I'd written a line of code. Calendar, Gmail, Slack, the CI dashboard, the Notion page holding the running plan — five surfaces, all telling me different fragments of the same story, all needing reconciliation in my head.
Article
I have a folder on my laptop called `~/os`. It is the most boring directory I own — eight markdown files, no code, no fancy structure. It is also the single highest-leverage thing I have built in the last year, and I almost did not build it because it looked too simple to be worth the time.
Article
I know engineers with twenty years of experience who can't ship a Claude app in an afternoon. Not because they lack skill — they're better programmers than I am. They lack reps.
Article
You spent the weekend wiring up an agent. It scrapes the GitHub issue, drafts a fix, opens a PR, posts a Slack message. It is genuinely impressive. You demoed it on Monday and a colleague asked whether they could borrow it.
Article
The common wisdom says AI removes boilerplate. That's backwards. AI + Boilerplates + strong error checking = Accelerated workflow. Rust's compiler catches AI mistakes at compile time. The industry is shifting from vibe coding to context engineering. Structure doesn't slow AI down — it makes it reliable.
Article
After a year of intensive AI-assisted development — hundreds of coding sessions, thousands in API costs, production systems shipped — one pattern kept emerging: the developers shipping fastest weren't using cleverer prompts. They were using tools that caught mistakes before production. Today I'm releasing The AI-Augmented Developer's Rust Series: two volumes teaching full-stack Rust development specifically for developers using AI coding assistants. Volume 1 covers Rust fundamentals through the lens of AI-augmented development. Volume 2 builds a complete Ethereum wallet with Yew (WebAssembly) and Axum. Studies show up to 40% of AI-generated code contains bugs. Rust's compiler catches these at compile time — memory safety issues, data races, unhandled errors. Google's data shows 1000x fewer memory vulnerabilities and 4x lower rollback rates. The bundle is $47. Buy once, own forever.
