|
I typically work 9 to 10 hours a day, but I am a consultant with a set number of billable hours per year. 8 hours per day for all of the actual "working days" (5 days/week excluding federal holidays) make up my billable hour total. Any daily time in excess of 8 hours gets logged as comp time. My time off comes by burning that accrued comp time.
|
|
|
|
|
Retired last year.
When I was working, I probably "worked" (i.e., was on the network) about 30-35 hrs/week. Of that, maybe 20 were actually coding, testing, etc--the rest surfing the net, going for a walk, whatever.
Still accomplished more than anybody else. Couldn't stand the boredom and working with idiots any more. Fortunate to have enough saved up to not need to work, so don't.
|
|
|
|
|
We have plenty of meetings, so my time at work isn't always productive ito actually developing.
|
|
|
|
|
If you're paid for it, it's time working. Now, time you're actually doing development can be less... if it's a lot less, and you don't like it, time to move on.
I spent a couple years with a new boss who used me as an informal gofer in addition to the development I was doing. I went to a lot of meetings and basically kept him from being mired in the noise. I never realized how much I hated it until he was laid off and they reorganized me back to my usual developer's position.
Software Zen: delete this;
|
|
|
|
|
What I like to do is bank hours on the weekend for the next week so I can take some time off during the week. While salaried, the power that be want to see hours worked on each client ticket, so we have "timecards" -- JIRA tickets.
That said:
I (the whole company) works from home full time.
I have no SO (not sure I even want one!)
The cats sleep most of the time.
It's getting cold outside, so I'm restructuring my daily exercise routine.
So the reality is, I put in as many hours as I'm motivated to (well, yeah, a minimum of 40) but often will do more (even 60 to 70, there's no end of tickets and/or interesting side projects not directly related to customer tickets) and bank the hours for the following week.
AND the peace and quiet of working on the weekend---priceless!
|
|
|
|
|
But when I was, there were weeks when it was <20, and weeks when it was >65, depending on how interesting it was. I guess it balanced out in the end.
|
|
|
|
|
|
I used to be able to report the number of hours I was in the office, but working from home is different.
|
|
|
|
|
Actually, more than enough... It's too much time wasted for a boring job, where cow-orkers don't want to learn anything and have bugs celebrate Easter (day of resurrection) every day.
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
So... Why not look for another job if you hate it so much? 
|
|
|
|
|
Enjoy dreaming!
A different job - that means the same crap with a slightly different colour.
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
It does with that attitude.
Environments can be completely different, even when the work is the same.
And even when the work is the same, different teams do it in different ways.
It's all about the people.
All I know is you definitely hate your current job and you might like another one.
That's a risk I'd be willing to take (and took in the past).
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
50 hours a week is normal, maybe more depending on weekend plans/chores and what deadlines are looming. I also have a sometime Saturday job (avg. 2x month) where I'm able to spend the majority of my time writing code for the primary job.
