4 ms·
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 n
by mkopinsky 15y ago
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.)
- Retric 15y agoNotes 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.
- mkopinsky 15y agoWhat 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.