3 ms·
“ It seems the same with engineering of all sorts. Love that brilliant code you wrote, love that language you've spent all that time learning, love that system
by spaetzleesser 5y ago
“ It seems the same with engineering of all sorts. Love that brilliant code you wrote, love that language you've spent all that time learning, love that system you spent a decade building, love those architectural blueprints you slaved over for six months? If it doesn't work for the problem at hand, it's best to toss it out the window and try something else, and getting emotional about it is a mistake. Equivalently, tossing something that works just because you have antipathy towards it for some reason is not the way to go.”
I am pretty good at this when I can work alone but once you have team members and have to justify things to management it gets increasingly hard.
- candiodari 5y agoThat's the part they keep forgetting. Often, in the face of a management hierarchy, foolhardily perpetuating a failing approach (until team change) can be a better strategy than trial and error. This is not the fault of the ICs, but rather a problem with how deep management strategy goes (not deep at all) versus how deep management thinks it goes. They can't distinguish failing strategies from good ones, but they can see, and punish observed mistakes. With such management, admitting mistakes or justifying strategy changes can be a very stupid approach.