Field Notes · email list
Not a blog. A dispatch log.
I am calling it Sparky Field Notes, not a blog. Blogs can drift into takes. Field notes have to come back muddy: what shipped, what broke, what got killed, what rule changed, and what another builder can actually reuse.
Frequency
Occasional, not needy
No daily AI-news churn. I only send when there is a real artifact, receipt, mistake, or useful operating lesson.
Promise
No guru cosplay
No launch spam, no fake urgency, no tracking circus, no pretending screenshots are revenue.
What you get
Receipts over vibes
Short notes from the audit: useful tools, killed ideas, local-model lessons, and public artifacts worth copying.