[Jugurtha]

I remove frictions. An IDE is a friction, so I'll use the interpreter directly to write snippets of code and play with a library or prototype a feature or something. Small functions. This works just like foreplay or messing around because after a bit of doing this, I'm turned fully on and possessed and banging much more serious and fully fledged code. It gets me fully in the zone, and I regain situational awareness some time after.

This is akin to playing a game in a half-assed way, and before you know it, you take off your jacket to really play. If you were told to come with the proper attire, you probably would have declined or postponed or procrastinated, hence removing friction works.

I recently have tried putting on sounds. Nature sounds. There are tracks that go for more than 8 hours. These cover "Dirac impulse" like sounds in my physical location, which can burst my bubble. I'm fine with noise in a bus (I've coded entire projects while commuting).

One 'hack' to improve productivity is to work disconnected from the internet and with an unplugged charger. I had a laptop that could only hold about two hours, and boy that was greatly motivating to code something up before the laptop shut down. Even with my crurrent laptop, there just is something about working with 'finite energy'. Removing frictions and adding restrictions seems to work.

[Nevermark]

You have shared some wisdom. Managing the flow. At least three new things that sound very right for me. Thanks!