BUILDING Elite DevOps

DevOps might be a philosophy in a book, however what we found out throughout the years of practicing this methodology - it's about SDLC management. You still are planning, building, testing, packaging, deploying, operating, monitoring and it doesn't matter if a person, a team, or a few teams do that. The task of connecting these components together into an efficient workflow is there.

Lack of practical experience and understanding of how DevOps practices connect into a project is evident even for the industry-standard stacks & tools. This affects not only TCO, the cost of hiring, the cost of onboarding, but also operational readiness, reliability, security, even lead time for changes.

Tutorials, courses, bootcamps, trainings are aimed at showing you a happy path so you can start with the tool or practice easily, and this is barely applicable in the real world where you rarely start from the ideal synthetic conditions. Real projects, migrations, and even every day operations, are anything but a happy path.

Many say “learn by practicing”, it’s a good phrase, we think it could be improved to “learn through challenges”. And we don’t mean courses, tutorials or bootcamps in a traditional way, but "challenges" where everything is designed for you to be anything but a happy path.

Good way to think about challenges is:

• Instead of "How to build a Docker project", we do "what to do exactly when a build of a Docker project fails in [your CI tool of choice]"

• Instead of "How to monitor an Elastic Kubernetes Service (EKS)", we do "What to monitor in EKS with [your monitoring tool of choice]"

• Instead of "How to save costs in AWS", we do "How to optimize the usage of EC2 background workers"

As you can see, our aim is to emerge you into concrete scenarios instead of high level happy paths.