This is the first post on a blog I’ve been meaning to start for a while, so it seems fair to explain what it’s for.
Writing as a debugging tool
There’s a particular feeling of having solved a problem without quite knowing why the solution works. The tests pass, the deploy goes out, everyone moves on. Six weeks later the same class of bug shows up somewhere else and none of that hard-won context is left.
Writing an explanation is the cheapest way I know to find the holes. The moment you try to put the sequence of events into sentences, the step you were hand-waving over stops being invisible. Half the posts I plan to write here will probably change my mind about the thing I was writing about.
What I expect to write about
- Backend and infrastructure work — services, databases, deployment, the boring machinery that everything else rests on.
- Problems that took me longer than they should have, written up so the next person spends less time on them.
- Opinions about the craft, clearly labelled as opinions.
No fixed schedule. I’d rather publish something occasionally that was worth writing than fill a calendar.
Say something
If you read something here and think I’ve got it wrong, tell me — that’s the most useful thing you can do with a blog post. You can reach me at faruk@masinovic.dev.