3 ms·
> having a "context" log, where you write the current progress, and what to do next yup critical. I do this and even if it gives me a 10-minute head start at t
by awinter-py 6y ago
> having a "context" log, where you write the current progress, and what to do next
yup critical. I do this and even if it gives me a 10-minute head start at the beginning of a work session, that means way more successful work sessions in a crazy week
I've started splitting my high-level todo list (tradeoffs + optimization) from my 'stream' todo list (next 5 linear things) -- the latter is useful for context + obstacles.
Writing down obstacles + setbacks also helps here.
- BiteCode_dev 6y agoWe are used to put what we have done in git messages. But for WIP commits, it makes sense to also put what to do next. This way git log is your journal.
- awinter-py 6y agototally I've had people get mad at me for 'nextup' comments in commits, but at minimum, given how central git is to our workflow, the commit is the right time to track work
- BiteCode_dev 6y agoThere is really no reason to get mad at that, if they want it in the final history, you can always edit it out with rebase when merging on stable. But I don't see how it hurts.
- tobyhinloopen 6y agoI usually write my progress and “what’s next” in the issue. Not saying it’s better or worse