I keep having to re-learn this: queue your yaks, don't stack them.

If you find a new bug while debugging something, file an issue, and continue with your debugging, Don't complicate things by trying to do many things at a time.

Apart from the complexity of doing many things at once, if you mix things in a branch, and the main thing you were doing in that branch turns out to be a mess, the other bug fix can easily get lost when you discard the branch or rebase it.

Lost yaks are sad.

Show thread

@liw github issues have been probably the best thing ever for my own project dev

@liw yak recursion can quickly suck up all available resources

@liw @liw I've chosen a massive yak to shave (web browsers)...

Please don't bother me with any others.

@liw yeah left to my own devices I’ll rewrite an entire code base unless I do this :)

@liw I'm liking this but not retooting. While I 100% agree with what you say, I think this is something you really only "get" when you've done it a few times.

@maltimore @liw just keeping a file of yaks-to-shave-eventually and throwing stuff in there instead of working on it immediately has been a big improvement for me. i still wind up stacking sometimes, but at least i have a mechanism for avoiding it.

@brennen @maltimore This is what the GTD system calls the "someday/maybe"list.

@liw Sigh, I've got yaks that have been waiting in that queue for years.

Sign in to participate in the conversation

Lars and friends