3 ms·
1. Keep notes. Depending on context, that might be comments written on the ticket, a notes file (that I delete when I open a PR), or todo notes (with my initia
by dave4420 2y ago
1. Keep notes.
Depending on context, that might be comments written on the ticket, a notes file (that I delete when I open a PR), or todo notes (with my initials) that I either resolve or defer to another ticket before opening a PR (and I have a `git todo` alias to find them all).
Partly this is just so I don’t have to rely so much on my memory. Partly this is communication to the rest of the team.
Sometimes I leave a comment on my ticket at the end of the day saying what I’d say about it in standup the next day. Which is good for me when I come back after the weekend, and good for the rest of the team if I spend a day or two off ill. It makes it easier for someone to pick up where I left off in my absence, if necessary.
2. Review my own PRs before I ask anyone else to.
If I can fix all the obvious nits before someone else looks at it, that frees them up to notice more fundamental issues that I’m blind to.
3. Commit early, commit often. Especially if I’m having a bad brain day.
- stemcanuck 2y agoI want to know more about note taking! I'll give you my example, when I am driving to work I might realize something or during lunch. In that case, what do you do?
- dave4420 2y agoIf I realise something during lunch, and I don’t have my laptop next to me, I’ll write a note to myself on slack (which I have on my phone). No reason you couldn’t use a note taking app, if you remember to check it later. When I commute, I commute by train. Leave yourself a voice memo, if you’re driving?