Perhaps the experts have decided that, for this specific instance, the thing we need to do is ad-hoc and throwaway, and is simply not worth paying the extra cost to make it tasteful.
Bash is one of the most complicated languages in common use and is horribly error-prone.
It's almost never useful alone, but as an interface to call other CLI tools.
I don't think this is a particularly useful comparison.
I cannot judge without more context. Depending on the one liner, the problem at hand, and overall situation that can be justified. A CLI is straightforward to create.
A bash oneliner can be a chain of 5+ programs, each buffering the stdin/out, what if the CLI is doing the same operation via streams instead? Just a random example but that can easily be worth it
Wait... Did you just fictional strawman a fictional strawman?
Because I don't think I've ever heard anyone say an expert gets brainwashed by AI into forgetting everything they ever knew. Maybe losing some skills that require regular exercise. Or get lazy about implementations when spawning dozens of super useful agents. But come on. Don't build your strawman out of a fictional strawman.
I'm sorry but "extensive documentation, scalable, high test coverage, perfect code style" seems to me to be the opposite of throwaway.
It sounds like the kind of thing people will think surely must be very important and in use, because why go through all those hoops instead of doing a quick hack?
But I guess we can just throw AI at the maintenance burden anyways..
I agree, so you should ask yourself "why would the expert do this?"
I decided to go for the charitable interpretation of "the alternatives are close enough in functionality that writing by hand is not worth it", instead of the uncharitable interpretation of "these examples are completely made up".
Ok, if you think the expert has forgotten that a problem can be solved by a bash one-liner and instead think they need a whole extensive CLI with documentation, our viewpoints are too far apart for fruitful discussion.
The bash one-liner might be hyperbolic but with the advent of AI everything is artificially longer, stuffier, more complex and convoluted for no reason other than because the AI allows this increase in volume with little to no extra effort.
It used to be the proverbial one-liner with zero documentation because that was the best ratio of effort to results. Now the effort is on the AI and the results look more impressive. Today that will still impress a lot of people, bosses, colleagues. Very soon everyone will see through it and anything overly stuffy will have the opposite effect of looking low-effort.
Or maybe they just didn't have the time (left it to the last minute and ran out of it), and went with the first thing that AI proposed which was said CLI with documentation.