-
Asked by to Edward, Ian, Mathew, Naomi, sakshisharda on 14 Jun 2014. This question was also asked by .
-
Ian Stephenson answered on 14 Jun 2014:
It’s really hard to say…
in a “regular” job you get given hours which are easy to count up. If you work in a shop then they record when you arrive, and when you go home and the hours between are the time you worked.
When you do a science based job that you love, you’re always doing it. (right now its just after midnight on Friday night! I’ve spent the evening writing code, and answering questions). It might look like I get in late, or go home early, but I’ve often woken up at 4 in the morning, and figured out how to solve a problem, then gone back to sleep. The next morning all I want to do is try out the solution, even if its the weekend.
If you measured the hours I sit at my desk at work it would be pretty low, but most of the real work takes place when I’m not “working”
-
-
Mathew Piasecki answered on 14 Jun 2014:
That’s a tricky one to answer, but I’d say much more than the average 40 hours. What makes it different is the fact that it doesn’t all feel like work. So if I’m at home and decide to read something related to my work then do I class that as ‘work’?
Probably not. -
Naomi Osborne answered on 15 Jun 2014:
I probably work 37-40 hours a week. I work 8am until 4.30-5pm Monday to Thursday but I get to leave at around 3pm on Fridays which is a great bonus! Occasionally I take work home with me, but this isn’t very often 🙂
Comments