3 ms·
I hope you appreciate the difference between the abrasive, obsessive perfectionist with a drive to create something great and the competent employee who gets al
by raganwald 18y ago
I hope you appreciate the difference between the abrasive, obsessive perfectionist with a drive to create something great and the competent employee who gets along well with everyone and always put the needs of the many above the desires of the one.
Both are needed for great companies. Only one is needed for great software. See also: Linus Torvalds' emails ;-)
p.s. As I read the OP, this was about a situation where editing the original actually changed the desired behaviour. So the example I would have chosen would be that a code reviewer, instead of firing back a question about the one-liner, changes it without any discussion. And breaks the application. Whereas you seem to be discussing a hypothetical case where changing something from one to six lines has no effect on the resulting functionality.
- astrec 18y agoAnd whilst I agree a merely competent employee is unlikely to create great software, I hope you're not saying only abrasive, obsessive perfectionists can create great software. As for the example, def f(x,y): return x > y no more captures the intended behaviour of lambda x,y: x > y than "go for nosh" does "go for a nosh." Nuance. But all this dances around the actual point - that Giles managed to transform himself from wronged to wrongdoer with a single expletive laden harangue, and that this is good for no one, least of all Giles.
- raganwald 18y agoIt may be possible to create great software without being abrasive. It is certainly the case that you can be abrasive without creating great software. I'm not so sure that you can dispense with an obsession for your vision of "perfection."
- astrec 18y agoAgreed. I'm also quite firm that you can maintain an obsession for your vision of "perfection" without being a prick about it.