about — shit claude told me

I'm an engineering and product leader. I manage teams of developers who build real software for real companies. In late 2024, I realized that if I was going to tell my teams to adopt AI-assisted development tools, I needed to actually understand them myself — not from a demo, not from a blog post, not from a vendor pitch. From the terminal.

So I started using Claude Code. Every day. On everything.

I didn't set out to build products. I set out to learn. The projects were the excuse. What you're reading is the journal.

two reasons

Sharpening the sword. The tools change. The languages change. The patterns change. If you stop learning, you become the person in the meeting who asks "can't we just use jQuery?" Claude Code is the most significant shift in how software gets written since version control. That's not hype — it's what I learned by using it every day for three months.

Leading by learning. I lead product and engineering teams. When I tell a team "we should be using AI-assisted development," I need to know what that actually means in practice. Not the pitch deck version. The real version. The version where Cognito auth breaks for the third time and you're writing SECOND_AUTH_INVESTIGATION.md at 11pm. I can't ask my teams to learn something I haven't learned myself.

the pattern

Every project on this site follows the same arc:

Ambitious idea. "I'm going to reverse-engineer a Bluetooth protocol" or "I'm going to build a web-based music studio"
Surprisingly fast progress. Claude Code gets you 70-80% of the way in a fraction of the time you'd expect
Vibe code into the weeds. The last 20% is where things get weird. "Yeah just add that." "Can you fix that real quick." Suddenly you have a semi-broken thing that mostly works if you don't look too hard
Move on. Because the point was never the product. The point was what you learned building it

This pattern repeats across 40+ projects over ~3 months. And each time through the loop, the starting point is a little higher. The prompts are a little sharper. The architecture decisions are a little better.

what this site is

A developer's journal of learning AI-assisted development
Technical deep-dives wrapped in honest storytelling
A reference for engineering leaders going through the same thing
Evidence that the best way to learn a tool is to build 40 things with it, even if none of them are finished

what this site is not

A product showcase (nothing here is "finished")
An AI hype blog ("the future of coding is...")
A tutorial site (these aren't step-by-step guides)
A portfolio (I have a job, this isn't for recruiters)

the stack

This site is hosted on AWS (S3 + CloudFront) and was, naturally, built by Claude. The domain was registered, the infrastructure was deployed, and the posts were written in CLI sessions. The irony is not lost on me.

contact