3 ms·
I'm frustrated for sure. I am looking for some pointers tho. How do people handle this "patch on patch" code. It reminds me a lot of the sunken cost fallacy.
by throwaway_fred 5y ago
I'm frustrated for sure. I am looking for some pointers tho.
How do people handle this "patch on patch" code. It reminds me a lot of the sunken cost fallacy.
How do you approach this to the people who wrote it?
- jimmyvalmer 5y agoHow to handle garbage code? You do your job, which is declutter and refactor. You know you're doing it right if the lines deleted exceeds the lines added. Unfortunately, the bigger the ball of mud, the greater the inertia both political and technical. Even software can't escape basic laws of physics.
- sdevonoes 5y agoPerhaps FAANG pays so much exactly because of this? I mean, they want the best of the best because maintaining patchy code (without breaking production) is difficult and painful. At least, in my experience in non-FAANG companies: they pay the big bucks to do the difficult stuff (e.g., maintain legacy patchy code without breaking production and bringing money to the company) not for doing the easy stuff (e.g., starting from scratch some cute microservice using DDD and Hexagonal Architecture).