4 ms·
I agree. Very often I see this set forth as a problem with management, but it seems to me that other engineers are also a significant part of the problem. I try
by biocomputation 10y ago
I agree. Very often I see this set forth as a problem with management, but it seems to me that other engineers are also a significant part of the problem. I try really, really hard to never be that engineer. If someone sees defects in something I wrote, regardless of the scope, I'm totally fine with whatever they do to make it better, up to and including totally replacing my work.
- calinet6 10y agoIt's the whole system that forms the basis for the problem: management, engineers, PMs, Designers, everyone who touches the problem space. If you want to improve, you need to make sure each part of the system is aligned around the same goal. Sounds hokey, but it is the reality. That means, as well, that it's both your responsibility and others' responsibility at the same time. Sure, you shouldn't be "that engineer," but you should also realize the kinds of things in the system that make someone become "that engineer," or lead them to be "that engineer" in some situations, or on the positive end, how certain engineers avoid it altogether. Then try to reproduce those factors and spread them. The problem is never individual. It's never about a good coder or a bad coder or anything like that. There are always multiple internal and external factors.