|
|
|
|
|
|
by S_A_P
2619 days ago
|
|
|
I actually posted this during a change management meeting. I was required to be there despite my portion of the meeting being 10 minutes of the hour. There are varying descriptions of "work", but my day usually lines up like so: 4:30am wake up
5:30 leave
6 arrive at the office
6-9 heads down coding
9-11 status, project, and various other meetings and help/administrative work
11-12 take lunch at the desk while I code
12-2 any follow up various other meetings
2-6 more code/tech work Or course Im not 100% utilized. Nobody is. If I were to work 8, I would have no time to actually work on the project I have deliverables due on. Meetings are toxic, but also necessary, and Im manager and technical in this role so I have to split my time. Saturdays I usually get a solid 8-10 hours of work in with few interruptions. I don't feel badly at all for posting here during billing hours, and if anything my invoices are conservative on real hours worked. |
|
|
I guess that’s what I mean; it’s not necessarily obvious when is work time and when is not. Even as you’re posting on HN during your meeting as you understand it is not valuable for you to be 100% “present” and it would be more valuable to explore ideas and culture on HN as you listen, so it is also true that many will be working on ideas as they eat dinner with their families, solving problems while they sleep, and planning their dependency graph during their commute. I just don’t think “hours worked” is an honest metric any more than 4 years at college shows that you were anything more than present.
Those 4 years could have been rigorous and honest and intense and valuable with a B average to show for it, or you could have been partying and have an A for your effort. Time spent might be required, but it also doesn’t matter.