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.
[ Parent
| on HN ]
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.