https://github.com/anordal/shellharden/blob/master/how_to_do_things_safely_in_bash.md
I still don't think you should, but if you're going to write programs in bash, you should at least try and know what you're doing to prevent shooting yourself in the foot.
On a simplicity kick. Seriously, stop complicating things when they're too simple for you. A program really can just be a series of nested function calls and no more. Resist the temptation to "simplify" an already simple problem.
https://www.dreamsongs.com/RiseOfWorseIsBetter.html
One of the older essays with interesting things to discuss. Worth a read and deep contemplation.
https://www.ariel.com.au/jokes/The_Evolution_of_a_Programmer.html
Less practical and more comedic.
This is the only software philosophy you need.
I've rarely felt more like I could have written a post than this. Stop over complicating everything.
Absolutely invaluable insights into managing and creativity.
Great introduction to many core computing.
https://sirupsen.com/shitlists
Such a simple concept that gives you so much return. I've used this to great effect in many large projects.
https://www.mit.edu/~xela/tao.html
A fun combination of Taoism and software development. Truly something valuable to the career programmer.
https://gist.github.com/kislayverma/d48b84db1ac5d737715e8319bd4dd368
If you're writing SaaS you really need to understand these concepts.
https://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to
The amount of time it takes to remove code you didn't write in most code bases is way too high. Too many people think the source code is the valuable part of the company when it is quite clearly the mental model in the heads of the programmers that provides at least ten times the value.
A Rich Hickey talk is always a good time.