My Principles in Ops and DevOps Management

  1. Use of gatekeepers to filter what goes into Production is key. I use process based techniques such as, QA sign-offs and/or product sign-offs, and utilization of a designated Change Advisory Board (CAB); as well as logical access controls, such as, access controlled code repositories and/or environments.
  2. Thoroughly monitor performance, availability and errors. I use tools such as,
    • Dynatrace
    • NewRelic
    • AWS Cloudwatch
    • Pingdom
    • Custom BI
  3. Establish repeatable processes. Runbooks / Playbooks deliver great value here. Documentation is key; diagram where necessary.
  4. Automate where it makes sense. Remove the risk of human error
  5. And finally, when incidents do occur:
    • Stop the bleeding as soon as possible
    • Stop the line (stop CI)
    • Reproduce error in the test environment
    • Find and test rollback
    • Deploy fixes with caution. Monitor afterwards
    • Use reporting techniques like CAPAs to learn and improve as a group

See other core areas of skill

Dev Process Engineering

I analyze the Quality requirements, delivery and MIS communications requirements, and develop custom tailored development processes for organizations.

Software Test Engineering

By applying industry best 'Risk based testing' techniques, I engineer highly efficient and highly effective test strategies, environments, and teams.

Operations Management

With extreme attention to detail, I ensure high availability of Production environments, build effective CI/CD pipelines and deliver software on time.

Got questions?

See what people say about my work.
Let's connect. I'd love to get to know you.