11–20 of 57 posts
Earlier quoted context omitted.
Same here, 8 billable hours (four days a week), 6-8 productive hours, depending on how stressful the day is.
"Oh hey... someone else working 4 day weeks, just like Stavro... oh..."
Sometimes the tasks I'm assigned are merely to reconnoiter the feasibility of taking action, and not to actually develop or commit code changes.
In other cases I'll be asked to change something that required 30 seconds of effort. Maybe flipping the value of a configuration flag from true to false, et c.
On average, I'll deal with tickets that involve several hours of stepping through nested loops in a debugger and inspecting log output, or wading through long-running SQL queries, and then committing changes that improve upon an existing body of work.
More rare are the intermediate tickets, that might take days and weeks of effort, and roll up into a larger project spanning many weeks or months across multiple developers. Tickets that keep me continuously tasked for multiple days at a time experience differing degrees of productivity, depending on hundreds of variables, and some of those variables are the work environment.
If something's really important and difficult, and the colleagues I'm delivering it to possess an understanding that it requires my undivided attention, then I'm provided with exactly that. I'll ask for a quiet office to camp out in, with a door I can lock, if I need it.
No matter what, I'm in the office, regardless of whether I'm idle, during a dead zone of activity while we wait for other people to provide requests or complete planning through interminable daily hours-long meetings, or whether I'm swamped in a firestorm of emergencies that divide my attention across several immediate worries.
At the end of the day, I'm paid for my time, and sometimes that pay is what will retain me through period of waiting for my turn at the trigger. If you don't pay me for that time, then I'm a temp, and not a regular, full-time employee. That's how it works.
I'm not a founder, or a partner, so I don't receive bonuses or a share of profits based on the success of calculated risks. In exchange for that, I accept the status of a regular persistent relationship. Eight hours a day, 50% of my waking time on this plain of existence, on call as a resident expert.
I stopped worrying about a perfect, even flow of continuous, normalized engagement a long time ago. Almost every field out there has varying degrees of hurry-up-and-wait temperament, and that comes with the nature of human interaction.
It's not productive to mince parsimonious hours and minutes, in my opinion, when it doesn't reflect the realities of human interaction.
In our office we work around 8 hours per day. We use Agile (Scrum) but we count only 6 hours per day. We recognize that we spend around 2 hours in overhead tasks (informal meetings, tasks not listed in the sprint and some not-job related work.
about 8hours a day. 2hrs independent technical reading. 2hrs independent design/development. 4hrs code-review/training others/discussions.
I leave some videos running before I sleep so I could hear/learn something new before I sleep.
I also work through weekends.
I think it is too much, but as a Syrian, I don't have the birth advantage of having a first-world country passport, I have to keep both the job (allows me to have the visa), and I make a lot of money which I can spend on family and building my own dreams.
In our office we work around 8 hours per day. We use Agile (Scrum) but we count only 6 hours per day. We recognize that we spend around 2 hours in overhead tasks (informal meetings, tasks not listed in the sprint and some not-job related work.
side project: 20 hrs a week