Also I’m not saying the authors view is wrong - everyone is different. And certainly my work situation is rare. I am not a planning person (my job as a prototyping engineer meshes well with this). So if all this Kanban stuff is too much for you, consider just working on stuff! :)
Anyway whatever the approach I’m glad this author is communicating what works for them about projects. A lot of people I talk to struggle with this.
With regards to planning, I wouldn't say I'm a planning person either. I have just found this minimal amount of process has really helped me focus on getting stuff done without taking away any passion/creativity. As you said everyone is different so YMMV, for me if a reader could take one thing from my journey is discipline yourself to a limited amount of concurrent projects, it has done wonders for me and I definitely see friends not moving anywhere because they have too many projects competing on their limited free time.
One thing I’ve realized is that I am good at setting small goals and usually getting them done in one sitting (sometimes failing and staying up too late). I try to tell people this. Get a raspberry pi and in the first sitting, just get far enough to ssh in. Then you’re done for the night! Next time you have a system waiting and you can get an LED to blink or serve a simple web page. Then later build one more bit, etc. I find it really rewarding to succeed in small bits!
Still haven't found a way to come back to projects once there's any sort of interruption.
I keep my journals in Workflowy, organized as follows: root folders for projects, subfolders for years, sub-subfolders for months, and the records at the bottom level.
It's not necessary to write daily. Write only if you have a message to your "future you" that could help him / her pick up the project after an interruption. Describe open problems, dilemmas you're facing, dead-ends you've encountered, decisions you've made, and next actions.
It's not necessary to write proper prose. Writing in caveman language is perfectly fine, as long as the future you can understand that.
Kanban has been one. I've started it for things I'm learning, although it's not strictly. I'm using GitHub issues to track various different learning projects. Mostly I'll have an issue that lists a series of videos in a series or blog post series and I'll tick each one off as I do them and take notes in a comment. That has helped with falling off the wagon. I might slow down, but I remember eventually "oh I only got halfway through that series! Let's do the next one now" and continue to make progress.
Projects where I make things have been a little different. I've found making an ecosystem of interrelated projects helps with bothering to complete things because as one project drags on and the enthusiasm for it dies, the will to keep going is fueled by the passion and excitement for starting the next project. I think I might call this concept a "Project Stack". The next project just so happens to rely on the current one, so it needs to be finished. Wish I had discovered this hack sooner.
The other thing that has worked well is flipping from nights to mornings. And back again. Waking up first thing in the morning and working on my project for 1.5 hrs before work has definitely made me make progress after the enthusiasm wore off and I would have gone in search of shinier things. There's just something about there being no excuses. Not tired. No one needs me to do anything as they're all still asleep. Don't feel the need to entertain myself as it hasn't been a long day. Might as well make another step of progress. But then after awhile I start feeling the mornings become less productive and I slow down because really I'm a night owl at heart. So I switch back! This gives a renewed sense of energy.
I'm a few days out from finishing project 2 in a "project stack" about 5 to 8 projects deep. Can't wait to start number 3.
If you have time to read more about this, check out my blog post here https://iam.mt/working-on-side-projects/