3 ms·
I mean, advanced tools will just create people with even less understanding of what's going on. And thus have even less of an idea how to fix something when "To
by SQueeeeeL 6y ago
I mean, advanced tools will just create people with even less understanding of what's going on. And thus have even less of an idea how to fix something when "Torch is being dumb" (no it's not Tom! You just suck, stop ripping templates off stackoverflow and actually read some documentation and understand what functions you're using do!)
99pi has a great episode on this phenomenon related to autopilot in planes https://99percentinvisible.org/episode/children-of-the-magenta-automation-paradox-pt-1/ https://99percentinvisible.org/episode/children-of-the-magen... where over automation makes edge case situations much harder to handle (in the case of planes this is deadly)
- nl 6y agoIt's often (for me anyway) not the understanding, it's the syntax that is a problem. I don't see any problem in automating the generation of the line-noise that is array manipulations. Can I write assembly? No. Do I understand what a compiler is doing? Yes. Does this cause problems for me? Maybe twice in my 20 year career and in both cases I've worked it out. Seems like a good trade off, and I see this as similar.