Why developers should support their own features in production
Christine O’Dell at JAX DevOps 2018
Development of a feature doesn’t stop at deployment. Your involvement continues for the lifetime of the product. We caught up with Christine O’Dell of Contino at JAX DevOps 2018 to talk about life after deployment, the downsides of being on-call and what’s the best way to handle these issues.
If you want great power to control the choice of tooling and approaches, then you must accept the great responsibility of ensuring it works – and remains working – in production. That’s why you should remain involved in your product’s life even after deployment.
We caught up with Christine O’Dell, consultant at Contino, to talk about life after deployment, the downsides of being on-call and what’s the best way to handle these issues. If you’re wondering who runs the DevOps show and why people come against each other, don’t miss this interview.
Christine O’Dell has been developing software with Microsoft technologies for over 12 years. She currently works at Contino helping our clients to understand, adopt, and sustain good practices for building and operating software systems. She has led teams delivering highly available Web APIs, distributed systems and cloud based services. She has also led teams developing internal build and deployment tooling using the unconventional mix of .Net codebases onto AWS infrastructure. Chris promotes practices we know as Continuous Delivery, including TDD, version control, and Continuous Integration.
Speaking of DevOps, you might want to check out this interview series:
- Part 1: Collaboration or survival of the fittest: Who runs the DevOps world?
- Part 2: DevOps without automation is like peanut butter without jelly
- Part 3: DevOps dream team or superstar DevOps engineer? Tips for aspiring DevOps engineers
- Part 4: Collaboration or survival of the fittest: Who runs the DevOps world?