6 ms·

I'd make a stronger assertion: top developers do have a life outside coding. My experience is that people who stay until 9 writing code because they're "passio

I'd make a stronger assertion: top developers do have a life outside coding. My experience is that people who stay until 9 writing code because they're "passionate" write a lot of code and implement a lot of features for a while, but the quality of the code is low because they're always tired when writing it. And after a year or so, a combination of burnout and the unmaintainability of their code forces them to quit, leaving the next group of programmers with something truly horrible. If that's your definition of "top developer" you can have all of them. IMHO, a top developer is someone who can produce a quality product from inception to completion, which requires being well-rested, taking care of their own needs, and having enough social life to be able to make their code decisions in their social context (because every program runs in a social context).

nickpsecurity 10y ago
Further, I'd say most of the evidence indicates this. A sampling of it follows. We know regular sleep improves quality of life and thinking. We also know many people who don't have it think that's not true but prove otherwise in tests. ;) Quiet office vs cubicle research long ago showed being able to focus with minimal interruptions improved productivity. A person with friends and family trying to code nonstop will be closer to cubicle vs someone who does it less but allocates time to not be bothered. Finally, there's also data from experiments like Fagan's Inspection Process, Mill's Cleanroom, and Altran/Praxis' Correct-by-Construction that teams of smart people on regular schedule using the right methods and tools produce the highest quality software you can get. So, evidence is vastly in favor of a more moderate approach to developing software in one's free time. Even for a person who practically lives on a computer. The brain needs novel experiences and breaks from things. Just works better that way as connecting new dots is the basis for creativity. Gotta feed it more dots. :)
- pantypants 10y ago
  I work from home whereas before I worked in an open plan office. As a developer. I do less hours now at home, but I only work the productive hours. If I'm not 'feeling it' I do something else, I don't have to sit there looking like I'm working, theres no-one watching me and judging me. I don't sit there until I get bored in that state to the extent I'll churn out code with a fuzzy head and so create inefficient inelegant code. If coding is all you do, I guarantee you're writing bad code. An hour when I'm in the zone is worth 2 days when Im not. If it takes me a day of taking a break to get into the zone its a net gain.

nickpsecurity 10y ago

Further, I'd say most of the evidence indicates this. A sampling of it follows. We know regular sleep improves quality of life and thinking. We also know many people who don't have it think that's not true but prove otherwise in tests. ;) Quiet office vs cubicle research long ago showed being able to focus with minimal interruptions improved productivity. A person with friends and family trying to code nonstop will be closer to cubicle vs someone who does it less but allocates time to not be bothered. Finally, there's also data from experiments like Fagan's Inspection Process, Mill's Cleanroom, and Altran/Praxis' Correct-by-Construction that teams of smart people on regular schedule using the right methods and tools produce the highest quality software you can get. So, evidence is vastly in favor of a more moderate approach to developing software in one's free time. Even for a person who practically lives on a computer. The brain needs novel experiences and breaks from things. Just works better that way as connecting new dots is the basis for creativity. Gotta feed it more dots. :)

pantypants 10y ago
I work from home whereas before I worked in an open plan office. As a developer. I do less hours now at home, but I only work the productive hours. If I'm not 'feeling it' I do something else, I don't have to sit there looking like I'm working, theres no-one watching me and judging me. I don't sit there until I get bored in that state to the extent I'll churn out code with a fuzzy head and so create inefficient inelegant code. If coding is all you do, I guarantee you're writing bad code. An hour when I'm in the zone is worth 2 days when Im not. If it takes me a day of taking a break to get into the zone its a net gain.