I keep a log for each project and write down the problem I'm trying to solve followed by the idea I think solves it. If I hit a roadblock, I write that down as the new problem. Now I have to solve that before I can pop the stack and get back to the original problem.
On and on and on. I might be building a CI/CD pipeline for a simple web extension cuz I've realized that manual deploys of it are boring and it's keeping me from updating the project. Once that's done I return to the original problem and geez it's annoying to work in this vanilla js project structure. Let me just set up a transpiler and organize the project...
I call it extreme yak shaving, cuz you do things you could never justify in a workplace, but it's my personal time and it's what works to keep me going on side projects.
Better yet by forcing yourself to write down why you're blocked you can self reflect on trends. I learned that when the dev experience gets too rough on a project, I abandon it. So now I'm happy to pause project features to build out dev exp. Very different than how I behave at work, where I guess the paycheck motivates me thru the tough times.
On and on and on. I might be building a CI/CD pipeline for a simple web extension cuz I've realized that manual deploys of it are boring and it's keeping me from updating the project. Once that's done I return to the original problem and geez it's annoying to work in this vanilla js project structure. Let me just set up a transpiler and organize the project...
I call it extreme yak shaving, cuz you do things you could never justify in a workplace, but it's my personal time and it's what works to keep me going on side projects.
Better yet by forcing yourself to write down why you're blocked you can self reflect on trends. I learned that when the dev experience gets too rough on a project, I abandon it. So now I'm happy to pause project features to build out dev exp. Very different than how I behave at work, where I guess the paycheck motivates me thru the tough times.