Here's how you can avoid repeating the mistakes of others as a system administrator.

The biggest learning is often not found online, on someone elses' pitfall, but our own. I don't believe any SysAdmin would say they never had configured anything wrongly or less than perfectly. It's ok to admit that, it's crucial to fix it, and it's more important to understand "how I got there", "what did I miss", and "how do I not miss it the next time". That's the real learning.

Have a teachable spirit by learning from research, collaborations and solutions. Also, you have to learn from your mistakes as this will be the best experience for you.

By cultivating a mindset of continuous learning, resilience, and adaptability, we can not only navigate but thrive in the evolving landscape of technology. The future belongs to those who are willing to embrace their potential and grow alongside the advancements in technology

Pro tip 1: Create the automation as simply as possible. If you could avoid excessive conditioning, do it. The number 1 most hated thing that happens is when a small step of a hyper-complex automation workflow fails, and then we scratch our heads and go crazy because to fix it, it's as good as re-design a new flow.

If you locked in your recovery and continuity plans back in January but had six code changes since, is your plan still up to date? Doubt it. This isn’t a one-and-done deal. You need to track every code and infrastructure change to ensure your plan stays relevant. Disaster doesn’t wait for your convenience, so your procedures need to be rock solid. And don’t just set it and forget it—practice, practice, practice. The "just like riding a bike" mantra won’t save you here. It’s not a skill you can rely on once and then hope to remember under pressure. As your services evolve, so do the people supporting them. Keep routine drills to ensure everything is documented correctly and everyone knows how to execute the plan flawlessly.

Making mistakes as a system administrator is normal, but the impact can be significant. Anyone can make a mistake, regardless of their experience, so it's crucial to embrace failure as a learning opportunity. ✔️ Document what went wrong and thoroughly investigate the issue, as this process often uncovers other aspects of the system. ✔️ Encourage your team to document the problems they encounter, their solutions, and the impact of each issue. Maintain a shared document cataloging these incidents, noting their frequency to identify patterns and plan for permanent fixes. ✔️ Most importantly, if you make a mistake in production, do not hide it. Seek support immediately to control and resolve the issue as quickly as possible.