3 ms·
I tend to do something like this for most tickets I work on (that have choices to be made). I work through all the details and make sure I understand them all,
by RHSeeger 2y ago
I tend to do something like this for most tickets I work on (that have choices to be made). I work through all the details and make sure I understand them all, then note what the difference choices are for various things. Where there's a choice to be made that requires "customer" input but that I have a pretty solid idea what the right choice is so am going to move forward on that, I'll make note of it, etc. It also gives me time/space to document ambiguities in the requirements.
I am.. overly verbose in tickets. That being said, it's come in handy many times in the past; some of which are me trying to figure out why I made a specific choice.
- simonw 2y ago"I am.. overly verbose in tickets." So am I, and I'm proud of it. I see a GitHub issue thread as effectively infinite storage for the ideas, decisions and research behind a change I make to a codebase. Here's a recent example - 51 comments and they were almost all me talking to myself https://github.com/simonw/llm/issues/617 https://github.com/simonw/llm/issues/617