Having DevOps as a separate function within an organisation has its caveats. Consider a traditional problem, a driving force behind the DevOps movement: Developers do not know where their code is running, or how it gets there. System administrators do not know how the code they are running works.
Terraform is a great tool for building infrastructure in the cloud. Ansible is a beautifully simple agentless (and serverless) configuration management tool. A common use case is to build servers with Terraform, and have Ansible configure them. Unfortunately Terraform lacks a provisioning plugin for Ansible - but fear not, they can be used together fairly trivially by using the local-exec provisioner of Terraform.
Whenever I need to run Docker containers manually, I end up looking up the basic syntax. Every. Single. Time. And I do this for a living. Here are my most Googled Docker run arguments, aka. My Docker Run Cheatsheet.
Generally the commands you run in a shell are either built-in commands, or external programs. Unless it is a command that’s built into your shell itself (such as ‘echo’, which just outputs whatever input you give it), the shell uses an environment variable called PATH to know which directories to look for an executable file.
In large organisations using the public cloud to store code, it's unfortunately not uncommon to accidentally make something public that should be private. Whether that's due to negligence or ignorance, a leak can have dramatic consequences.