Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by mkopinsky on Tuesday September 20, 2011 @11:04PM
(#3020562)
Until 4PM, you've also been working on things that are value-adds on some level. Your choice not to make use of the small time windows (which aren't actually so small) is your own choice, not a direct function of the office.
Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by Retric on Tuesday September 20, 2011 @11:46PM
(#3020667)
Depending on what you are working on 15 minutes may be enough time to make some progress, but anything with a moderate level of complexity is going to take longer than that before gain enough context to start.
Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by mkopinsky on Tuesday September 20, 2011 @11:57PM
(#3020689)
If you take notes, you can gain context from 9:00-9:30, and rev up again quickly from 10:00-10:03. The time doesn't need to be wasted time.
(Not that this is necessarily easy to do, or perfect, but I think we can accomplish more than we think in this manner.)
Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by Retric on Wednesday September 21, 2011 @12:20AM
(#3020750)
Notes like all other forms of documentation is suspect. If it's a complex problem that you don't already have a solution to you really do need to sit there and think "Why did I think this when I wrote it." otherwise it's easy to create flip flopping bugs. AKA fix bug 357, fix bug 372, hey wait bug 385 looks like 357 ahh that's right I need to set the flag to X, hmm wait bug 392 looks a lot like bug 372 etc.
PS: And when you have 15 minutes to work it's next to impossible to figure out how to fix 392 without also creating 357 yet again.
Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by mkopinsky on Wednesday September 21, 2011 @10:00AM
(#3021997)
What I meant by "notes" was just scribbling down your thoughts as you go along - things like "$property modified between file.php:500 and :600? WTF". Enough data to jog your memory when you get back to your desk and then throw away once you solve the bug and document the fix in a real fashion.
Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by mcantor on Tuesday September 20, 2011 @11:12PM
(#3020578)
You're right! However, it's inefficient for a developer to always be doing that much non-development work. And it is possible to get real work done during the small windows, but only certain types of real work. Occasionally you can fit in a bunch of good bug-fixes. Other times you're able to organize things into discrete small tasks up-front, and you can get a few of those things done with each small window. But, it's impossible to really achieve flow in those circumstances. The lack of flow is really the gist of my argument.
Re:A Fifth of Telecommuters Work Less Than An Hour Per Day
by mkopinsky on Tuesday September 20, 2011 @11:46PM
(#3020666)
With the schedule you described, it doesn't sound like you're purely a developer. Either a lot of this stuff needs to move from your plate to someone else's, or you need to accept that you do a lot of non-development work.
Note that of the distractions you describe, a lot of them are things that you would have still had if you were working from home. The emails and the IMs are still there, although I guess they might be more ignoreable since you don't have the threat of the person showing up at your desk. :-)
It's now 11:15. The developers start lunch at around 11:30 - noon every day, so there's no reason to get started on anything now. You get back from your hour lunch break at 12:45. There's a meeting on your outlook calendar at 1 o' clock, but you read the description and decide to skip it since there are already enough developers on the docket to give enough input. You're just gathering momentum at 1:05 when the Project Manager who organized the meeting appears at your desk, asking you to come to the meeting.
"I have a lot on my plate; the other two devs know enough about the system to keep the ball rolling."
"Well," she counters, "I really need everyone's input for this meeting." (Just like every other meeting.)
"There are 20 people on the invite list... if there are any problems, I'm sure I can just follow up with you after you send out the meeting minutes."
"Look, I really need you here for this; this isn't a skippable meeting." (None of hers are.) Finally you fold--you didn't take this job because you were a go-getter who knows how to tell people "no" repeatedly. The meeting is scheduled for 1PM - 2PM, but (like most meetings at this company), it goes until 2:30.
You get back to your desk and there are a dozen new IMs and e-mails blinking on your screen. You fantasize about just closing everything and working, but you've been here long enough to know that un-answered IMs and e-mails will result in people walking over to your desk, just like the jilted business user from this morning. For a couple of months you managed to put your foot down, mark yourself as "busy" in Outlook for the afternoon, and tell people that you simply won't deal with any non-critical problem during that period, but hearing complaints about issue turnaround time come through your boss was too much of a drain.
You answer IMs, follow up on e-mails, flip through high-priority code reviews and take care of other necessary busywork for about an hour and a half.
At 4PM, you get started on your work.