Your work responsibilities boil down to 2 things, either add value to customers or save cost for the business.
Value to the business is always more important than the latest technical fad. If a feature is done (production
ready) but not deployed to production it is an opportunity loss for the business.

Adopt a painless continuous delivery culture, add more business value [Slides]

Below are the slides of my talk titled "Adopt a painless continuous delivery culture, add more business value" given today at DevOpsDays Portland 2017:

The Slides #

Slides on slideshare

The Video #

The video of the talk is below:

The Abstract #

A continuous delivery of new features definitely adds value to the business, it should be effortless to the tech team too. 5 years back our sys-admin team was in Istanbul and the dev team was in Dubai. Even then changes were shipped periodically but the process was cumbersome. A stable delivery pipeline with tests, continuous integration and small atomic deployments with github flow gives us a leading-edge. The culture of logging and monitoring ingrained in our team helps us move fast. Now, we ask a chatbot to deploy our microservices several times a day to production. In this session, I will unveil details on how you can get started with a smooth continuous delivery pipeline one step at a time.

Conclusion #

The first day of DevOps Days PDX 2017 was pretty impressive. Looking forward to day 2!

Geshan Manandhar Geshan Manandhar
2 MIN READ

Comments

Related Blogs

From 0 to working Serverless URL for a Containerized app with Google Cloud Run [Slides and Video]

Serverless Containers are possible and getting a running URL with Google cloud run is super easy.

Logging best practices to get the most out of application level logging -- Slides

Logs from the application level are the only way your application talks back to you. Having proper logs with commendable search capabilities is like having a torch in a dark room.

Moving from A and B to 150 microservices, the journey, and learnings [Slides and Video]

We were frustrated too, but in 4-5 years of time, we replaced A (front-end) and B (back-office) system with ~150 microservices.

Stay Connected

Follow me on LinkedIn for new posts, engineering insights, and tech takes — straight from the trenches.

Follow on LinkedIn  →