My Notes on Three Years of Coding with AI
A non-hype version of what daily AI-assisted coding actually looks like after three years, written like a conversation over coffee.
Available now for Elixir work. Two weeks. One problem. $6,000. Details →
Hello! My name is Mike Zornek. I describe myself as both a developer and teacher, and I've been building digital products for over 25 years.
From the suburbs of Philadelphia, I code in Elixir . When I am not coding, I enjoy watching Phillies baseball and playing video games (mostly laid-back simulations and RPGs).
New here? Here are some quality posts to get you started.
A non-hype version of what daily AI-assisted coding actually looks like after three years, written like a conversation over coffee.
A tour of some small personal choices behind clean, readable Elixir code I strive for.
A concrete walk through a real Phoenix problem: showing timestamps in each reader's own time zone.
Why data ownership and offline-friendly software matter to me, and where local-first is heading. It's a problem space I'm digging into right now.
The simple async standup format I've leaned on for years to keep a team honest, human, and unblocked.
An abandoned dependency was blocking a major upgrade I needed. Here are the two ways I retire one, and when a shim beats a big-bang rewrite.
I have hardened LocalCents with more automated Elixir quality checks than I have ever run. The whole guardrail setup, wired in a real repo.
Notes on how my use of AI has changed over three years, and what's working and what isn't inside LocalCents.
We all nod along to "good code" but rarely define it. Here are the four attributes I look for, and the practices that protect each one.
How I track work, from issue statuses and types to pull request conventions, with sample PR templates you can copy.
You open a project you did not write, hit a wall, and find no one left to ask. The habits that spare the next developer that moment.
Inherited a live codebase with no one left who built it? Here's the checklist I run through in week one — before touching a single feature.