I found it a good idea to have a person or a few people who will hold you accountable actively by asking you how’s that plan going on, and maybe even doing a proper retrospective every few weeks.
I can totally see how it can help people, don't get me wrong - I've seen it work and logically it should; I've just not had any luck with it, but it could just be me.
It could be the environment I'm in, I'm not surrounded with other devs or anyone very close, so my idea-spewing ends up with people who might not understand most of what I'm trying to convey.
That aside, great post and article, so thanks for sharing! :)
I really resonate with 4, 6 ( Sometimes we just have to treat ourselves ) and lately found 8 to be a very important step. I try to 'reset' my work environment be it for web dev, game dev, or something physical, so at the end of a session code gets pushed up to the repo, folders sorted and applications closed, with a revised TODO or note in place for the next time I visit the task. I find it avoids clutter and noise - allowing me to easily dive into a project next time without distraction.
1 is a great point too, and something I want to adopt into tackling procrastination. I do something similar to fight anxiety - and it helps.
Have you tried to find something like an accountability buddy?
(accountability buddy—a person who has similar goals or interests, and you’d be both happy to see each other succeed, and you’d meet with that person to discuss each other’s progress on your long-term goals periodically)
I haven't to be honest (nor has it crossed my mind) I normally avoid exploring such things due to ... well, anxiety XD But as I work through that and try to grow as a person (and developer) it certainly makes sense.
Thanks for the idea, I will try it
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.