I would then assume those scripts weren't written properly to begin with.
But yes, shell scripts should be used (normally) to automate some simple tasks (file copying, backups...) or as an wrapper to exec some other program. I've written several shell scripts to automate things on my personal machines.
However shell script can be complex program while at the same time being (somewhat) easy to maintain:
- functions, use functions, alot
-
- comment every function and describe what it expects in stdin or as an arguments
-
- also comment what it outputs or sets
This way at least I don't break my scripts, when I need to modify a function or some way extend my scripts. Keeping the UNIX philosophy inside shell scripts: let one function do one thing well.
And of course: YMMV. People have wastly different coding standards when it comes to personal little(?) projects.
Dude... This is Rickrolling on the nightmare level.
Those who don't remember: NSFW to google that.