Hacker News new | ask | show | jobs
by mrkeen 1 day ago
* My last monolith job had 4 hour release windows.

* You can't change anything of substance. The more people touching the same codebase as you statistically puts you way lower in the pecking order. Changes become political, not technical.

Sometimes the forces of stupidity cancel each other out. It was a 10+ year-old C# monolith, and the top dog wanted to switch to Python because "AI works better with it". I didn't have to waste any time worrying or arguing, since him keeping the system as a monolith made this change impossible.

1 comments

Why would a single deployment unit have to be written in exactly one language?
OK, count me onboard!

Can we convince the 2-3 other stakeholders in our deployment unit to go with this crazy plan? Or are there 40-60 other stakeholders we need to convince?

Why would the number of stakeholders be related to the number of deployment units?
why would a single deployment unit require more than one language?
Doesn't, but if you want to, you can