1 Commit per Day

Found the “1 Commit per Day” Idea in this Video:

For me, it sounds a bit like the Book The One Thing: https://www.amazon.de/dp/1848549253/. Haven't read it yet, but it is on my list. Or Atomic Habits: https://www.amazon.de/Atomic-Habits-Proven-Build-English-ebook/dp/B01N5AX61W

This “rule” is interesting regarding a side project. Like writing a book, where you write 1 sentence per day. After a year, you have 365 sentences and maybe a short-story or the first chapter of your book. So if you write 1 commit per day, no matter what, you make progress on your side project even if it is a change in your README.md.

My first try on a similar rule was to do something on my side project for at least 30 minutes each day. But i never “found” time for it. Because I have to force me to do something for at least 30 minutes. That is a massive blocker in my head. Same for planing my day or week in advance in my calendar. Where I need to put my To-dos into the calendar and add specific time blocks to block time. Maybe it could work for me, but with a Family, it will take more time to manage these blocks and move them around instead of just doing something from my To-dos.

What I like more, is to just start and see where it is going. Like this blog post. I started writing this post about the Video but then, it is growing more and more. Something I didn't plan to do. For me, it is easier to just start and not force me to plan it. For example, I planned to write at least 1 mastodon post per day, but this is not working for me. Instead, I write, when I feel to. Clearly this results in fewer post, but who cares as long as I feel good about it. Same with this blog. I planned to write at least 1 post per week. Sadly, it feels like a burden, and I would rather not do something that is a burden if I have control over it.

In the end, I'm happy with how this post turned out. A bit self-reflective, that's what I was hoping for, will come out, when I start writing more. :)

2/100 of #100DaysToOffload