Coding flow state

After a few months of not coding, there comes a time in which new habits need to be reformed and rebuilt to get back into a session of coding productivity

There is a book from Cal Newport dubbed "Deep Work". The summation of it is this - any form of intense work can be done in 3 hour spurts at a time, but requires some conditions

Namely, there needs to be minimal to no distraction, a short term goal of what needs to be achieved, and trigger points of initializing that flow state

This is some of the ways I use to initiate them

Leave uncommented notes when coding after a session is finished

After working on a feature or a ticket (be it personal or for work), leaving a set of uncommented notes about what needs to be worked on next, or hashed out pseudocode, effectively leaving a set of things of what has to be worked on next.

It's almost like assigning homework to yourself in a way, or not finishing a TV show episode on a cliffhanger and leaving it halfway in

This creates a sense of excitement of finishing that goal, that task, in a way that drives momentum forward

Create environments where certain work is done

With work from home being an option these days, it can be easy to mix a home based environment with that of a work one. Normally environments can trigger this state, and my preferred place to doing work has generally been a coffee shop

Depending on the day, I tend to explore new places at the same time (or revisit places I like already) - this gives a sense of adventure even in a 9-5 routine

Music

Musical sound tracks provide an audio cue into what type of work is done. It helps tune out all the other things going on (in this case a coffee shop)

My preferred go to has always been some form of chill-hop, and it has a limited timer such that it acts as a pomodoro at the same time