4 ms·
A lot of the time I am not writing code, but I am working all the time. My job is not to write code, but rather to come up with solutions, do research. A lot of
by numbers_guy 3y ago
A lot of the time I am not writing code, but I am working all the time. My job is not to write code, but rather to come up with solutions, do research. A lot of the job is just thinking things through.
- dyingkneepad 3y agoSo you never waste a few minutes to an hour doing not-work things such as browsing Hacker News, Facebook, trash talking Elon Musk with your coworkers at the watercooler, etc? (not saying you don't, just curious, I know some rare individuals on Earth are like this)
- EligibleDecoy 3y agoNot speaking for anyone else, but breaks are important. I am more productive working a cycle of 50 minutes “work” then taking 10 minute breaks. I would count my walking outside to get fresh air (or decompressing with some HN) work as it’s helping me solve problems. But then again, sleep is super important to being productive but I wouldn’t call that work either.
- paulcole 3y agoHe’s claiming that his mind is always subconsciously thinking about solving problems even when he’s doing those things. It’s kind of a humblebrag.
- idontwantthis 3y agoIt's also a justification for slacking off, but also just true and points out why 8 hour days are silly, and offices are silly.