Programming
Well, this is quite the topic. I’ll have to figure out how to structure this later. For now, this is "unstructured programming" har har har.
-
dsl (domain-specific language(s))
-
if-else-stack (interpreted if/else logic without a tree)
-
Do it the dumb way first and build-it-twice and Leopard-Free Programming
-
Assembly and bare-metal and rpi pico
-
shell (mostly UNIX, mostly Bash) and text-generation
-
NIH (Not Invented Here)
-
ical-vtimezone bullcrap
Dave’s Programming Language Advice
There is no one true programming language. They all have strengths and weaknesses. I have learned to embrace multiple-tools.
Having said that, I think every programmer should pick at least one "scripting language" for quick, one-off utilities and learn it deeply. Be able to read a text file line-by-line in that language. That alone will let you do an unbelievable number of amazing, useful things with your computer.
Then, whether or not you need to learn something Web-native like JavaScript or PHP or a "systems" language like C or Zig will depend on your specific needs.
First, you gotta see what’s out there. Check out the Forths and Haskells and Lisps and Prologs of the world. Try the ancient Unix utilities. Learn what’s already available on your system.
But then specialize. Don’t keep language hopping forever. It’s like Linux distro-hopping: fun at first, but after a while the hopping itself becomes the hobby - you’re not doing anything else. If that’s your thing, cool, but be sure you want that to be your thing!