http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/ as stimulating as black coffee and just as hard to sleep after. Tue, 20 Jul 2010 08:19:01 +0000 hourly 1 http://wordpress.org/?v=3.0 http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/comment-page-1/#comment-73 Andy Bailey Wed, 19 Dec 2007 20:18:23 +0000 http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/#comment-73 it's important to let a client know that too because if you say you charge 50$ an hour for coding updates and you tell the client it'll be ready in a couple of days they might think you are going to charge for 2x8x50 for the job! (I speak from experience) it’s important to let a client know that too because if you say you charge 50$ an hour for coding updates and you tell the client it’ll be ready in a couple of days they might think you are going to charge for 2x8x50 for the job! (I speak from experience)

]]> http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/comment-page-1/#comment-72 Mike Mon, 17 Dec 2007 03:47:49 +0000 http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/#comment-72 This is true for engineering as well. This is true for engineering as well.

]]> http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/comment-page-1/#comment-71 Andy Sun, 16 Dec 2007 23:24:25 +0000 http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/#comment-71 Working in a support/development role I can agree with this completely. I get to work at 8 o'clock and there are days where it can take till well past 10 to just get to actually reading my email. Replying to them can take most of the day if im not careful. If I could actual sit and spend 50 % of my time on programming and product development I would be lucky Working in a support/development role I can agree with this completely. I get to work at 8 o’clock and there are days where it can take till well past 10 to just get to actually reading my email. Replying to them can take most of the day if im not careful. If I could actual sit and spend 50 % of my time on programming and product development I would be lucky

]]> http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/comment-page-1/#comment-70 Alex93053 Sun, 16 Dec 2007 23:00:07 +0000 http://www.gridpulse.com/2007/12/15/an-eight-hour-work-day-doesnt-mean-eight-hours-of-coding/#comment-70 This is exactly how my days go too - and you're right about the part where you have to help coworkers since you're most likely working on the same goals. If management knows what they are doing, they will plan and assign the roles in such a way that there is little downtime. If I'm spending a big part of my time helping a colleague on a regular basis, then the colleague may end up pulling down the whole team. This is exactly how my days go too – and you’re right about the part where you have to help coworkers since you’re most likely working on the same goals. If management knows what they are doing, they will plan and assign the roles in such a way that there is little downtime. If I’m spending a big part of my time helping a colleague on a regular basis, then the colleague may end up pulling down the whole team.

]]>