chinmay185

"You either die before Product Market Fit or live long enough to see the effects of Conway’s Law in your system architecture."

This is what I ended up saying to a colleague in one of my conversations.

This was in a context of refactoring a legacy system where we used Conway's Law as a lever instead of thinking of it as a constraint and inevitability. Without an external measure, software entropy will kick in and systems will succumb to it.

But if you're thrown into such a system or you inherit it, how do you navigate refactoring of such systems? You can't fight Conway's Law, instead use it as a lever to refactor legacy systems.

I finally ended up writing about this. Have a read.

I’ve spent the last 15+ years in the trenches, first as a backend product engineer and now running an SRE/DevOps firm. One thing that consistently annoys me is the "Certification Hoarders"

These people _just_ do certifications, not actual work. Like, they can talk about all the theoretical stuff that's covered in certifications but they don't have any production experience. They haven't really _applied_ their knowledge on actual work.

Since I run my own boutique tech services company, I decided to address this "gap" by building an engineering laboratory we call Prayogshala.

Engineers should focus on "lities" - availability, maintainability, reliability, so we decided to build these habits in them ourselves.

Thanks for all these links.

Thanks. I am mainly interested in learning about dynamic programming and graph algorithms.

Thanks. very useful. appreciated.

I feel 128gb is not enough. Given a choice, would you instead have gone for 512gb with 16gb ram?

Happened with me for some of the projects I have worked on.