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.
Notes from watching ElixirConf US 2026 on a virtual ticket, and some talks I'd point you to first.
Your CI history already knows which tests flake. This prompt pulls the evidence, names the tests, and works out what the re-runs cost.
Why phoenix_test makes Phoenix feature tests read better and fail more usefully.
An educational side project: a local-first expense tracker built with Automerge CRDTs in Elixir, Phoenix, and Tauri, plus how I surface sync conflicts.
Every sprint is a tug-of-war between the roadmap and the work that keeps the lights on. Here is the 45/45/10 split I plan against, and why.
A couple of new habits have stuck: weekly planning, and a signal log to track where my consulting outreach lands.
What agent skills are, and a walkthrough of the one I lean on to update Elixir dependencies and open a documented pull request.