Taking Back “Software Engineering”

**Dave Farley: *"Craftsmanship is not enough."* 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 approach 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 continuous delivery 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 a 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. **In this talk, you'll learn:** * How to understand what "software engineering" really means