3 ms·
Many development problems having zip to do with code. Trying to fix the code without addressing those (which are often outside your ability to change) is pointl
by coldcode 10y ago
Many development problems having zip to do with code. Trying to fix the code without addressing those (which are often outside your ability to change) is pointless. Organizational issues, terrible overweight processes, political infighting, poor decision making by management or product teams, or even dreadful hiring practices all can make the code terrible but can't be fixed my trying to change the programmers.
- mkanat 10y agoMaybe. I've interacted with a lot of companies on this subject and I've found that not to be the case, though. There's usually more that an individual engineer can do about the system than sometimes they believe. It's not that there aren't management problems--there are and they are real and they do cause many or most of the failures in the software engineering industry in part. However, purely blaming management for the quality of your code is an irresponsible attitude that won't actually get you anywhere. And I don't mean "irresponsible" in the sense that you should be blamed for it, I'm taking about responsibility as the ability to be cause over your own situation, the ability to be the source of the things that you yourself produce. If you're sitting around saying that somebody else is responsible for your production all the time, then you're not going to be able to be at cause over it or come t change it in the way that you want. So yes, there are management flaws and they do cause this sort of trouble, but there's also another attitude that you can take toward it and ask yourself, "What CAN I do about my code, like for real?"