hm. Well I tend to work with smaller companies that have less people overall. So we need a lot of automation to enable the devs to be more productive. We have fully automated cicd pipeline where everything in the pipeline can be run locally. Most of the scripts support the pipeline allowing quick and easy reproduction of anything that might not work in gitlab. We have scripts to authenticate, validate, build, deploy, unit test, integration test, performance test, lint, e2e test, vuln scan, terraform, teardown, updating tickets, generating release notes... It's a very transparent system to the developers. And it works pretty well, which is why they don't need to have all the scripts memorized. They just don't need to run them much. But when the pipeline fails in a way they don't understand, access to all this allows them to self-serve finding out why. I know that plenty of places just make the devs do a lot of this manually. And since they are doing it often, it's easy to remember and a required part of the job. But humans make mistakes, or cut corners and such which leads to bugs getting out into production. With working automation the devs don't have to do these things manually very often which means they don't need to memorize all of them, and less opportunity for bugs to slip through that could have been caught. The fact that they don't have our scripts memorized is actually a sign of success for the automation. I have always been of the opinion that the more we can automate the mundane tasks away, the better. The people I have worked with prefer spending their time designing and coding, not memorizing mundane processes. Even with all our automation, our devs are always hoping for more.