I learned most of what I know from people who had no reason to share it but did anyway. A blog post from some engineer explaining exactly the bug I'd been stuck on. A Stack Overflow answer that saved me an afternoon. Source code I could read and actually learn from.
That's the whole reason I'm doing this.
I've spent over a decade building things - web, mobile, SaaS, backends that had to hold up under real load, and more recently AI. A lot of that knowledge just sits in my head, or in Slack threads from three jobs ago that nobody's going back to read.
Why I'm writing
Free, public writing by other engineers is how I got here. No course, no bootcamp - mostly just people who decided their knowledge was worth putting on the internet. I'm not where I am without that.
So I'm putting mine out there too. If something I write saves someone a few hours on a problem I've already solved, that's a good enough reason.
What I'll cover
Ten years across a lot of different terrain:
- Web and mobile product development
- SaaS - building it, scaling it, keeping it alive
- Backend systems and what happens when they break under load
- AI integrations - what's actually useful and what isn't
- The stuff that doesn't fit neatly anywhere: decisions, tradeoffs, hiring, the unglamorous parts
The real version. Not the retelling where everything worked out.
How often
When I have something worth saying. Not on a schedule.
If you want to follow along, there's an RSS feed.
Top comments (0)