3 ms·
Sounds like every multinational org with 100k+ emplyees, certainly this fits my own. Fun part is, there is no realistic way out of this. It only takes one obscu
by saiya-jin 5y ago
Sounds like every multinational org with 100k+ emplyees, certainly this fits my own. Fun part is, there is no realistic way out of this. It only takes one obscure critical legacy app to add so much integration mess into whole ecosystem that nobody ever will be re-doing those.
Plus business won't put in the budget necessary for practically no change from their point of view.
- marginalia_nu 5y agoI've worked at a 500 employee-company that had many of these issues, mostly from misguided attempts at copying the way FAANG worked without any regard for our own needs or scale. The entire code was a tangled mess of git submodules, transitive dependencies and the build system was contingent on a domain-specific language that was partially developed in-house and partially based on some unstable open source project, incredibly janky, and only two people got to see the sources for it or even knew how it really worked. Dumpster fire doesn't even begin to describe the outcome. There was always this strange spooky-leftpad-at-a-distance thing where stuff just kept inexplicably breaking, and nobody ever quite knew what had gone wrong, who to talk to, or when it was gonna get fixed.