3 ms·

> brilliant one who is constantly going down rabbit holes unnecessarily Ha, sounds like an oxymoron

qume 8y ago
I see that, but one type of really good dev is one who is super focused on the small details, and it seems to be human nature that it's hard to do that well and keep the big picture in your head at the same time. I think these guys are totally capable of thinking big picture, but they are often just not in that 'mode' and hence the tendency to inadvertently find themselves writing code that if they took a breather and sat back and re-evaluated, probably wouldn't write.
frank_nitti 8y ago
Maybe - I think the missing component is their level of "laziness" as Bill Gates defined it. A brilliant, but "lazy", coder will find the most efficient way to compose a solution that meets the requirements. But it's definitely not an oxymoron to say that some brilliant coders can go down rabbit holes at the expense of their own (and company's) time and productivity. They may spend lots of time reading white papers, improving a design/implementation/test-suite beyond what is required, etc. It's just these coders don't place a high value on being as efficient as possible from a PM's perspective, but might be able to solve a problem 10x as difficult as the guy who is closing his tickets within hours of assignment.
- Retric 8y ago
  'efficient as possible' is only measurable in terms of the task at hand. Being smart educated and hardworking does not necessarily make you better at your job if you spend most of your effort tilting at windmills. At times it really is better for everyone to just move on from a comfortable position and stretch your wings as it where.
- megaman22 8y ago
  I like to call it strategic laziness. Knowing what to do, and more importantly what not to do is key.
- ropeadopepope 8y ago
  This reminds me of the following by General Freiherr von Hammerstein-Equord: > "I divide my officers into four classes as follows: The clever, the industrious, the lazy, and the stupid. Each officer always possesses two of these qualities. > Those who are clever and industrious I appoint to the General Staff. Use can under certain circumstances be made of those who are stupid and lazy. The man who is clever and lazy qualifies for the highest leadership posts. He has the requisite nerves and the mental clarity for difficult decisions. But whoever is stupid and industrious must be got rid of, for he is too dangerous."
  - gp7 8y ago
    I'm clever and stupid.
- hinkley 8y ago
  Or you know, writing an entire library instead of filing four PRs against an existing one, with a user base, documentation, stack overflow entries and resume appeal. Nothing more dangerous than a smart but bored developer.
- rhacker 8y ago
  I would much rather be refactoring code from that guy... I seem to be refactoring the industrious and stupid code.

qume 8y ago

I see that, but one type of really good dev is one who is super focused on the small details, and it seems to be human nature that it's hard to do that well and keep the big picture in your head at the same time. I think these guys are totally capable of thinking big picture, but they are often just not in that 'mode' and hence the tendency to inadvertently find themselves writing code that if they took a breather and sat back and re-evaluated, probably wouldn't write.

frank_nitti 8y ago

Maybe - I think the missing component is their level of "laziness" as Bill Gates defined it. A brilliant, but "lazy", coder will find the most efficient way to compose a solution that meets the requirements. But it's definitely not an oxymoron to say that some brilliant coders can go down rabbit holes at the expense of their own (and company's) time and productivity. They may spend lots of time reading white papers, improving a design/implementation/test-suite beyond what is required, etc. It's just these coders don't place a high value on being as efficient as possible from a PM's perspective, but might be able to solve a problem 10x as difficult as the guy who is closing his tickets within hours of assignment.

Retric 8y ago
'efficient as possible' is only measurable in terms of the task at hand. Being smart educated and hardworking does not necessarily make you better at your job if you spend most of your effort tilting at windmills. At times it really is better for everyone to just move on from a comfortable position and stretch your wings as it where.
megaman22 8y ago
I like to call it strategic laziness. Knowing what to do, and more importantly what not to do is key.
ropeadopepope 8y ago
This reminds me of the following by General Freiherr von Hammerstein-Equord: > "I divide my officers into four classes as follows: The clever, the industrious, the lazy, and the stupid. Each officer always possesses two of these qualities. > Those who are clever and industrious I appoint to the General Staff. Use can under certain circumstances be made of those who are stupid and lazy. The man who is clever and lazy qualifies for the highest leadership posts. He has the requisite nerves and the mental clarity for difficult decisions. But whoever is stupid and industrious must be got rid of, for he is too dangerous."
- gp7 8y ago
  I'm clever and stupid.
hinkley 8y ago
Or you know, writing an entire library instead of filing four PRs against an existing one, with a user base, documentation, stack overflow entries and resume appeal. Nothing more dangerous than a smart but bored developer.
rhacker 8y ago
I would much rather be refactoring code from that guy... I seem to be refactoring the industrious and stupid code.