SEAM #28 - Avoiding a Meltdown, The DevOps Way - Dave Farley+BMC+Devoteam

In SEAM #28 we are joined by legendary Continuous Delivery pioneer, Dave Farley.

Along with Dave, Ross Burton of Fidelity, Neil Cullum of BMC and Matt John of Devoteam will be discussing how DevOps practices can be used to help avoid a meltdown from a people, process and tech perspective.

Agenda:

18:30 - 19:00 - Networking Drinks and Pizza
19:00 - 19:30 - Ross Burton (Fidelity) & Neil Cullum (BMC) -
"Let the Dev, meet the Ops"
19:30 - 20:00 - Matt John (Devoteam) -
How Ops makes Dev work - The key to a successful marriage!
20:00 - 20:30 - Dave Farley -
Taking Back “Software Engineering”
20:30 - 21:00 - Prize Draw (2 * Apple Airpods) & Go to the pub

*Please also register with the venue (SkillsMatter's CodeNode) via
https://skillsmatter.com/meetups/12532-seam-28-avoiding-a-meltdown-the-devops-way-dave-farley-bmc-devoteam

Dave Farley Bio-

Dave Farley is a thought-leader in the field of Continuous Delivery, DevOps and Software Development in general. He is co-author of the Jolt-award winning book 'Continuous Delivery' a regular conference speaker and blogger and one of the authors of the Reactive Manifesto.

He has a wide range of experience leading the development of complex software in teams, both large and small, in the UK and USA. Dave was an early adopter of agile development techniques, employing iterative development, continuous integration and significant levels of automated testing on commercial projects from the early 1990s.

Title: Taking Back “Software Engineering”

Subtitle: Craftsmanship is not enough

Abstract:
Would you fly in a plane designed by a craftsman or would you prefer your aircraft to be designed by engineers? Engineering is the application of iterative, empirical, practical science to real-world problems. Craftsmanship is a wonderful thing, and as a reaction to the terrible abuses of the term Engineering in software development Software Craftsmanship has helped in our learning of what really works.

The term "Software Engineering" has gained a bad reputation. It implies "Big up-front design" and "Mathematically provable models" in place of working code. However, that is down to our interpretation, not a problem with "Engineering" as a discipline.

In recent years we have discovered what really works in software development. Not everyone practices approaches like Continuous Delivery, but it is widely seen as representing the current state-of-the-art in software development. This is because at its root CD is about the application of an iterative, practical, empirical, maybe even science based approach to solving problems in software development. Is this a form of software engineering?

Software isn't bridge-building, it is not car or aircraft development either, but then neither is Chemical Engineering, neither is Electrical Engineering. Engineering is different in different disciplines. Maybe it is time for us to begin thinking about retrieving the term "Software Engineering" maybe it is time to define what our "Engineering" discipline should entail.

Ross and Neil's talk...
Title: "Let the Dev, Meet the Ops"
Bridging Digital Business Automation to Continuous Delivery with modern orchestration methods: ‘Jobs As Code’ and ‘Automation API’.
How Fidelity is transforming agile delivery of applications and infrastructure, reaping the benefits of truly automated continuous delivery and provisioning pipelines whilst avoiding the headache of Operational Meltdown.

Matt's talk...

How Ops makes Dev work - The key to a successful marriage!

Devoteam UK’s Service Transformation lead Matt John looks at how to ensure a successful ‘marriage’ between a Dev and Ops framework. What operational fundamentals need to be in place to build a successful union? How can development run smoother, faster and with minimal manual interactions?

Thanks to our sponsors BMC and hosts Devoteam.
Thanks also to our regular sponsor, E-Synergy ( (https://www.esynergy-solutions.co.uk/), without them we couldn't meet up every month.