Hacker News Reader

Comment by jfabre | Hacker News Reader

It always baffled me to hear:" Oh we're gonna do microservices, because our monolith is a total mess and we're very unproductive". If you can't organize a monolith, what makes you think you will be able to organize microservices which are vastly more complicated to work with. How about you learn as a company the proper skills and habits to achieve logical modularity within a single process before you try doing that with multiple processes.

View on HN

I’m probably the last person on here to discover https://grugbrain.dev/, but I like the particular quote:

“grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too”

And I would also add:

The reason your monolith is a mess is because your organization has low standards on code quality and doesn't value it. It is not willing to invest in it, and probably your department didn't acquire the skills and habits to produce clean code in cheap manner. The developers who are used to good code usually leave you out of frustration. No one likes to be unproductive, especially productive people.

I wonder if part of why microseconds work for some companies is the hype helps justify the work to management.

> We need to convert to microservices.

Sounds like a cool shiny new approach enabling better scaling and organization.

> We need to refactor this mess.

Sounds like complaining, why is it a mess anyways?

These two things may essentially be doing the same thing, organizing/breaking up the code logically, one just might sound more appealing to management.

I hate how much I can relate to this.

"productive" means shipping code to these people. They are trying to minimize how often someone says "we are blocked on deploying that code"

You would need to provide me with a concrete example, because I've never really had the issue you're describing. I'm willing to bet it's fixable by having better management.

Reply on news.ycombinator.com