Comment Full time programming, logging hours (Score 1) 547
I'm a full-time programmer - all I do is program. Rarely have meetings (every other week), don't deal with customers. Just program.
My boss is strict on me logging hours - not to keep track of time, but to bill clients. He doesn't mind if I'm only getting 4-5hrs in an 8hr day, because he knows I'm being honest. The important part is logging accurate hours for billing the customers.
In a good week (where I'm dealing with new issues each week, resolving lots of bugs, adding new features), I will log around 25-30 hrs. In a slow week (one problem bug), I get bogged down and do around 20hrs.
I find that if it's difficult, it's best to clear my head and do other activities (walk, surf the tubes), but if it's not frustrating, I really get immersed in my work, and am really productive.
It really depends on how the person handles what they're working on. If it's tedious and drains your attention, I find that most people turn to distractions to clear their head, like going on Slashdot an hour before you get off work (hehe). Other days, I'm so caught up in knocking out bugs left and right and getting a lot accomplished that time flies and I might put in a full 8hrs of work. Really depends on your work environment and what work you're doing.