Being a founder is one of those roles where you're giving feedback on basically everything, while also trying to get a couple of things done each day on your own. Two weeks ago, I was working on a really hairy problem with @maestromac . We were making slow but steady progress, and learning a lot together. It was one of those problems where it'd take you 30 minutes each time to re-orient yourself to what you were dealing with, and what new solution you were trying out. It was, and is, a real doozy.
But then! A few days into it, a totally administrative/business/non-technical problem came flying my way. It was something that needed my full attention, so I dropped everything else I was working on. That took away several days and now it's been over a week since I coded. Each time I take a break from coding, I feel like I've taken many steps backwards and it's hard to get back into the headspace. This time in particular, I dreaded facing this relentless problem.
I really didn't want another coding-dry-spell week to fly by, so to get back in the groove, I've decided to update some documentation instead. I find that the magic of pushing something straightforward and seeing it pass all the tests and make its way to production, is the small win that I need to feel inspired again.
I'm only now realizing that documentation, or updating copy, or fixing a teeny tiny bug is almost always what I need to do for smoother context switching. I think this will help me drag my feet less 😅