I think these books and resources should not be viewed as hard rules, but as sets of examples explaining guiding principles, and the internet is full of discussions that turn into religious wars over it.
It is always worth it for a programmer to dwell over what complexity is according to Osterhaur; it is worth it to reason over what Uncle Bob thinks is "clean" code, etc. I'm not benefiting from either by applying what they say dogmatically, but I improve my taste in what is good software to me, by discovering and trying many approaches. Without reading them I might never even have thought at a particular solution, or a particular frame of mind.
I also just began experimenting with plaintext. At the moment, I create regular apple reminders when I want to receive a notification, and for everything else I keep a markdown file `quicknotes-YYYYMM.md`, which I use also for some some throwaway notes.
Every month, I duplicate the file, remove what's been completed and the things I don't want to do anymore. The file is on iCloud Drive in the obsidian folder, so I can edit it also from my phone.
It is always worth it for a programmer to dwell over what complexity is according to Osterhaur; it is worth it to reason over what Uncle Bob thinks is "clean" code, etc. I'm not benefiting from either by applying what they say dogmatically, but I improve my taste in what is good software to me, by discovering and trying many approaches. Without reading them I might never even have thought at a particular solution, or a particular frame of mind.