Do you have them publicly available somewhere? I'd be interested in that, especially your `next` function telling you which to-do is coming up next without you having to look at _all_ tasks again.
Every day.
Whenever I clock out in the afternoon, I turn it off.
When I want to do private stuff, I turn it on again, and turn it off when I'm done. The only thing with uptime worth mentioning in the house is my Pi Zero running PiHole.
Splitting up commits is totally underrated and seen rarely. I see colleagues over and over again plumbing 4 kinds of changes into the same commit. Good luck reverting the one change that caused an outage.
I have yet to see a good documentation strategy. We have quite some awareness about the problem but I don't see an easy exit.
Currently, we have a similar dumpsterfire running. Project / guideline / bla documentation hanging around in Confluence, technical documentation snippets in git repositories "near" the code they belong, some folks scourging themselves with Sharepoint and there's no solution in sight.
Me and some colleagues have developed quite some tendencies against natural language documentation because it basically becomes stale as soon as you publish it into your org.