Why now
I've spent almost a decade writing production code — Node.js, Python, Flutter, React, AWS. leading migrations, debugging incidents, and designing architectures. A lot of that learning happened in small experiments before it became production work.
These labs are my way to make that process visible: test an idea, document the decision, explain the trade-offs, and keep the useful parts available for later.
What you'll find here
- Architecture in practice — real decisions, real trade-offs, no hype.
- Implementation labs — prototypes, API experiments, data flows, and infrastructure notes.
- Field notes — weird bugs, useful patterns, and tools worth using.
- Engineering leadership — lessons from leading squads and migrations while staying close to the code.
Cadence
I'll publish when a lab has something worth keeping: a working approach, a failed assumption, or a useful decision record. Small, focused, practical.
If any topic interests you, ping me on LinkedIn. Let's talk.