Starting This Thing

Alright, I'm doing this. Starting a blog in the end of 2025 feels stupid - like showing up to a party five years too late - but I keep having the same conversations and I'm tired of typing them out over and over.

Last week I was on yet another call trying to explain why a startup with 3 users doesn't need microservices, and halfway through I realized I've had this exact conversation probably a dozen times this year. Same with "your Postgres database is fine actually", "no you don't need Kubernetes", and my personal favorite: "that new JS framework won't fix your organizational problems."

I've had this domain sitting around for like eight months doing nothing. Every time I thought about writing something I'd get stuck on dumb questions - what's my brand? what's my content strategy? who's my audience? - all the overthinking that stops you from just doing the thing. Then I'd go read another blog post about "how to start a successful tech blog" which is exactly the kind of meta nonsense that doesn't help anyone.

So screw it. I'm just going to write when I have something to say and hopefully save myself (and maybe someone else) some time.

What this is

I work as a consultant. That means I see a lot of different companies, codebases, and ways people solve problems. Sometimes the same mistakes keep happening. Sometimes something actually works well. Sometimes I learn something that changes how I think about a problem.

I'll probably write about:

• Architecture decisions but the real kind, not the LinkedIn kind. Like "we picked X and here's what broke" or "this seemed smart until it wasn't"
• Why simpler is almost always better (our industry has a complexity addiction and it's exhausting)
• Actual trade-offs instead of "best practices" that ignore context
• Team and process stuff because that's usually where the real problems are, not the tech stack

No promises on posting schedule. No grand plan. When something's worth writing about, I'll write it. When it's not, I won't.

I'm not trying to be a thought leader or build a personal brand or whatever. I'm just a developer who's been doing this long enough to spot patterns and wants to write them down somewhere other than Slack messages that disappear.

If you read something here and think "that's completely wrong", good. I'd rather have an actual conversation than post obvious stuff everyone agrees with.

Anyway. First real post coming whenever I get around to it.

Rangelov