Good question. No. I log during every stage. To clarify how it works, it's not a minute by minute logging. It's logging at every stage that one might normally pause and think. "Hmm.. ok that step is done, now on to the next.. which is..." . So when I'm in the flow which happens rarely, it'll be like:

11:47 - Alright. Time to implement the functionality to read the JWT token and store it and cache it for future requests.

11:52 - Test has been setup and is failing as expected. Let's pass this!

12:20 - Phew. Finally got that working. Making the function testable was a little harder than expected. Had trouble mocking the call to requests so that I don't actually get a token from the service for each test. Any way, that's done. Now I need to test if it actually works when running. How should I do that though?

12:26 - I have an idea! <there's be a flow chart diagram here and a bullet point list>

12:40 - NICE! It worked!

Does that help clarify how I might go about logging? I find that the flow doesn't come all that often and most tasks I'm working on requires me to pause and think often. And the maximum time of work to pause is usually 20-25 minutes.