OK, for those who do responsible "due diligence" work on all the third party libraries you add, include, and update, …
What about your tool/languages libraries?
What about the operating system itself?
Remember: "Operating Systems" started out as "Here are some useful library routines that others wrote, and we all share."
@JeffGrigg @inthehands @vashbear
I'm also amused when I solve a problem with core OS tools and calls, often with little effort above reading the docs and understanding the underlying model.
There's always someone who needs an epipen, though, after I use m4.
I do see where the micro-kernel people are coming from.
We had a koan in one group: "You must know how to write a binary search. You must never write a binary search."
@TallSimon @inthehands @vashbear
Yes! Exactly!
Not long ago, I was "handed" AI generated JavaScript to decode and unzip the data returned by a web service.
The code did not work.
So I worked on it a bit, and got it working.
Due to limitations of the vendor tooling, it still did not really work well.
"To heck with it!" I said, and redid it with a simple Unix/Linux command line, using only the standard tools.
…
@TallSimon @inthehands @vashbear
And not only did it work better, it was easy to leverage it from "Do this one call." to "Call all the services for all of these items, format all the responses, and put them in well named files for later use."
Barely a handful of small bash scripts.