>>> With the current market for engineers, if you aren't enjoying your work most of the time, you're doing something wrong and should probably find a more interesting project to work on. Fire yourself if you have to.
Yup, I'm starting a new job in 1.5 week, extremely excited :)
>>> Even leave things for tomorrow.
That is also very true, blogged about it too a while ago as well [0]. Trying to get something done for 3hrs can be replaced by 1hr burst next day, as long as 'tomorrow' doesn't become a procrastination. What is important is to make sure that you are actually having a break, your mind is totally away from work.
And yeah, I agree about the timers. I sometimes use a pomodoro timer app and trying to make it a habit, planning to make a physical arduino one. Some day :)
> Trying to get something done for 3hrs can be replaced by 1hr burst next day
I've often found that impossible bugs that I struggle with for hours on end and just can't figure out no matter what I do, get solved in 10 minutes next morning.
Now how do I teach this to junior developers? I've worked on teams where juniors will frequently overwork themselves in an effort to "pay their dues" or whatnot, or just because they feel they should offset their lack of skill with stronger work ethics and I am fairly convinced it's counterproductive. But I can't seem to find words to explain this to them. Or maybe I'm wrong and the "leave it for tomorrow" only works when you've reached a certain level of skill.
Programming largely is creative, with some degree of standard and quite autopilot code. Creative work can't be produced by staring at a blinking cursor.
I agree with counter productivity, and I strongly agree with companies who approach this with 'just get it done, whenever you want'. Twitter certainly does so, Netflix I believe does.
>>> Or maybe I'm wrong and the "leave it for tomorrow" only works when you've reached a certain level of skill.
I think there is some skill involved, or more accurately, experience. The problems we are solving are often unique but still share something in common. After solving a bunch of them, you have a gut feeling when something's going right, and when you must to take a step back.
And it has to do with corporate people and managers, not everyone understands how programming works. Young developers are afraid to look lazy in front of their non-technical managers. It's often important just to appear working hard, e.g. reading HN in terminal ;)
>>> With the current market for engineers, if you aren't enjoying your work most of the time, you're doing something wrong and should probably find a more interesting project to work on. Fire yourself if you have to.
Yup, I'm starting a new job in 1.5 week, extremely excited :)
>>> Even leave things for tomorrow.
That is also very true, blogged about it too a while ago as well [0]. Trying to get something done for 3hrs can be replaced by 1hr burst next day, as long as 'tomorrow' doesn't become a procrastination. What is important is to make sure that you are actually having a break, your mind is totally away from work.
And yeah, I agree about the timers. I sometimes use a pomodoro timer app and trying to make it a habit, planning to make a physical arduino one. Some day :)
[0] "3. Take a break and don’t feel guilty about it" http://blog.gedrap.me/blog/2014/05/19/4-things-i-learned-the...