2016: never, ever run a script unless you know what it does
2026: let a statistical model run random commands for you
@sol_hsa
[Community Note: Don't!]
@sol_hsa unless you know what it does was true in 2006 and 1996 also. In 1986 if you knew what a script was, you probably knew what it did, but that was still good advice.
@sol_hsa I used to think that the `wget -q -O- <some-random-url> | sudo bash` anti-pattern was dangerous and dumb, but then I've watched how a tech company CTO did vibe shell command execution as root.
@matus_chochlik @sol_hsa
yes, I think piping a random download directly into a shell, maybe even a root shell, was an intermediate step that softened people for such bullshit
@sol_hsa this is what I cannot understand at all - we used to have rules where and how to run computers in critical enviroment. What software was allowed and how we personally had to check and recheck, i.e. in medicine/clinics.
And now we use non-reliable tools, that might have non-checked unreliable A.I. inside even in an environment where lives are at stake. This is a time of madness.
@energisch_
There is no rule so rigid that it can withstand our laziness
@sol_hsa

@energisch_ @sol_hsa to be fair, they all state in der eula, more or less, that it's for entertainment purpose only and not meant for critical systems …

but yeah. who tf reads this shit except the llm that distilles it into tldr instructions or, helpful as always, friendly asks: would you like me to rm -f this for you? so glad to be at your service ;)