About
I write about things I ran into while building.
Sometimes it starts from something small — a weird behavior, a pattern that didn’t feel right, or a system that broke in a way I didn’t expect.
I try things, break them, and figure out what actually works.
Most of what I write isn’t planned.
It’s usually something like:
- “why does this feel off?”
- “why did this fail?”
- “what actually made it work?”
And I follow that until I understand it well enough to explain it.
I don’t try to cover everything. Just the parts that made me stop and think.
If there’s a pattern here, it’s probably this:
Turning small ideas into deeper technical insights, and trying to understand the “why” behind them.