3 ms·
I've found that the most important thing is not engaging in marathon sessions, full stop. My code is better, I'm healthier, and I get more done per working minu
by jaggederest 8y ago
I've found that the most important thing is not engaging in marathon sessions, full stop. My code is better, I'm healthier, and I get more done per working minute.
Take a break every hour or so, minimum ten minutes, and step away. Make coffee, ponder the infinite, pet your cat, listen to some Chicago or Slayer, whatever suits your preferences.
- core-questions 8y ago> Chicago or Slayer Really covering a wide gamut here!
- jaggederest 8y agoMozart to Mötley Crüe, you know how it goes.
- mukuro 8y agoAgreed, and since 99% of programming doesn't even involve writing code, it might be healthier to "program" away from the screen, while going on a walk for example.
- marcus_holmes 8y agoMy code quality also improves when I limit my sessions to a few hours at most. After about 8 hours or so, I feel like I'm getting a lot done, but I almost always have to refactor significant chunks of that code later. If I limit my sessions to implementing one feature or process, and then going away from the screen to think about it more, my results are better.
- tribesman 8y ago> My code is better, I'm healthier, and I get more done per working minute. It's not about what you are. What market asks is, are you better than others who you can be replaced with? The ones who are ready to scarifice themselves, their health and deliver more code then you. Let's not pretend that his worries are unfounded.