Slashdot Mirror
The P.G. Wodehouse Method of Refactoring
covertbadger notes a developer's blog entry on a novel way of judging progress in refactoring code. "Software quality tools can never completely replace the gut instinct of a developer — you might have massive test coverage, but that won't help with subjective measures such as code smells. With Wodehouse-style refactoring, we can now easily keep track of which code we are happy with, and which code we remain deeply suspicious of."
This thread seems to be full of asshat managers. Your job is to provide the developers with management not to guide them like sheep. Despite the shepard-like delusions you've picked up from the authority granted by your role, the programmers have insight into the project that you lack and they're generally much, much smarter than you when it comes to engineering. A good manager realizes this and listens to the developers when they say this needs to be done right and there is no good enough solution that won't result in catastrophe down the road.
Asshat managers love to say things like, "this engineer lacks business sense" or "he's very smart but he's not business smart" - as if business smarts is a superset of, say, engineering smarts? The notion is preposterous and is nothing more than a delusion you asshat managers reinforce with each other because your narcissistic personality disorders demand superiority to your "underlings". Oh, how they put our company at risk with their refusing to do things half-assed! Listen to yourselves!