> Should I be writing reminders to myself to always double check everything?
> Should I write down the steps to every process?
Yes, but... this should be in the form of code if feasible or shared documentation (README or wiki content) if not. Organizations cannot (and healthy ones do not) rely on perfect execution from every human at every step.
To support this if you have solely been relying on GUIs (IDEs, web UIs, etc.) I strongly encourage you to learn the command line interfaces (or even APIs) of every tool you interact with (source control, build, ticketing, deployment, ...). There is almost no common dev task in modern environments that can't be automated with a simple shell script once you know these. Check those scripts in so they're available to everyone to use and review, correct, or enhance. A working shell script is the best documentation possible for many processes.
Yes, but... this should be in the form of code if feasible or shared documentation (README or wiki content) if not. Organizations cannot (and healthy ones do not) rely on perfect execution from every human at every step.
To support this if you have solely been relying on GUIs (IDEs, web UIs, etc.) I strongly encourage you to learn the command line interfaces (or even APIs) of every tool you interact with (source control, build, ticketing, deployment, ...). There is almost no common dev task in modern environments that can't be automated with a simple shell script once you know these. Check those scripts in so they're available to everyone to use and review, correct, or enhance. A working shell script is the best documentation possible for many processes.