1) As the article states, work on your side project first in the morning before your work. You will be too tired after work. Yes, this means your not really giving 100% at work. Hopefully your good enough at your job that this is OK.
2) Create little task lists, with short little tasks... Then knock those tasks out one by one. If you find yourself procrastinating about some task do another little task first, then later make a quick spur of the moment decision to go do the procrastination task.
3) It's OK to dream about the best case scenario, but also have realistic side goals: "worst case scenario, I've built a cool engine for my next project."
4) DO create the right amount of tests (too little and your going to be creating buggy crap code, too many and you're bogged down updating your tests constantly)... get a feel for what your right amount is.
5) Don't type so much, think more... think through designs... use paper, be messy and redraw... all of this is faster than building the wrong thing.
6) I think its OK to be quirky. Make the thing YOU want to make. This is another way to monetize: your mental health is worth a lot and personally I find bringing shit that I want to exist into the world just the way I want them to be is a good trick for staying happy.
Does anyone know what app the author is using to create nested tasks for 'lightweight sprint'?
https://www.wetteronline.de/apps
If everyone gives them one star Apple will kick their app out of Appstore.
However, I am currently still sticking to pipenv as it seems to be closer to pip/venv and lot easier to migrate to. I also found UX quite nice. However, I keep hitting into bugs from time to time.
On the side note, glad to know that my small effort (I operate that site) is useful for people I highly respect.
I was very surprised when I saw it on HN front page today.
I don't want the perfect tool, just one that isn't horrendous.
Atlassian changed their strategic focus from on-premise to cloud, and they are making lots of improvements, including performance.