I've been an engineer for a few years now. I write code every day.
But I realised recently that I've been consuming far more than I've been creating —
reading papers, watching talks, bookmarking articles — and almost none of it sticks.
The solution, as best I can tell, is writing.
Not writing for an audience. Writing as a forcing function for thinking.
If you can't explain something simply, you don't understand it yet.
This is the oldest trick in the book and I've been ignoring it.
What this blog is for
- Accountability — writing things down commits me to them.
- Learning — explaining forces understanding.
- Reflection — looking back at what I got wrong is how I get better.
This is not a blog about being impressive. It's a log of someone
trying to become a better engineer, one post at a time.
What I'll write about
Systems design, things I've read, mental models I'm building,
mistakes I've made, and ideas I'm chewing on.
Expect irregular posts. Expect rough edges.
The bar for publishing here is: would I want to read this in six months?
Let's see how this goes.