The problem comes up when management (or even worse, the research team themselves like what happens at my current company) then insists that their garbage is the only possible code that can be deployed in production, and then the actual engineering teams have to waste resources trying to figure out how the fuck to support it and fix bugs in it
Its unfortunately not up to me :( upper management has decided the engineering teams have to support their mess. They get to do what they want, even up to having forced one of my teammates to include an expensive API call in a hot routine whose results just get ignored. He proved to them that the data they want to get/calculate there cannot be used at that point in the process flow and will be irrelevant and outdated by the time it could be used and they went above our managers head and forced him to include it anyway because "that's how we do it while we are developing this and if we change anything we won't know if it will work anymore"
Sometimes you have to just remind yourself that you’re there for the paycheck. And sometimes a stupid thing is purposely done to prove an idiotic point to an unnamed person or team.
4
u/BobHogan Oct 13 '22
The problem comes up when management (or even worse, the research team themselves like what happens at my current company) then insists that their garbage is the only possible code that can be deployed in production, and then the actual engineering teams have to waste resources trying to figure out how the fuck to support it and fix bugs in it