Transforming Software Engineering: A Call for Rigorous Standards
Written on
Chapter 1: The Unique Nature of Software Engineering
Software engineering stands out among engineering disciplines; it often lacks the physical constraints and immediate consequences associated with other fields. For instance, if a civil engineer makes an error, it could lead to a faulty support beam or a damaged circuit board, forcing them to pause and consider their next steps while ordering replacement parts. In contrast, a software engineer can simply hit backspace to rectify their mistakes. The most significant risk might be temporarily freezing a computer, which is relatively easy to recover from.
Furthermore, creating physical items presents challenges, such as ensuring movement or electrical charge flows correctly. Structures must withstand gravitational forces, which they often resist. Thankfully, engineers have developed predictive modeling techniques over centuries to ascertain a machine's functionality before assembly, allowing them to save valuable resources and time.
Software engineering is undeniably captivating and intellectually demanding, attracting many talented individuals. However, the penalties for subpar solutions are minor; the difference in time lost between a mediocre and an efficient solution may only be a few seconds. This lack of immediate consequence encourages a culture of "move fast and break things," a philosophy that reflects a disconnect from the realities faced in traditional engineering.
Chapter 2: The Evolution of Digital Infrastructure
Our lives have become deeply intertwined with information technology. We rely on digital platforms for everything from ordering food to communicating with friends, obtaining news, and managing our schedules. While these applications and programs have evolved into essential infrastructure, they were originally developed as experiments or 'toys.'
Digital calendars, for example, emerged when physical calendars were still the norm. Initially intended as a futuristic enhancement, they weren't designed to manage our daily lives comprehensively. Similarly, cellphones were introduced when payphones were widely available, serving as a mere convenience rather than an emergency lifeline. The design did not prioritize reliability, resulting in the glitch-prone nature of modern smartphones—rarely does one hear someone refer to their device as 'trustworthy.'
Social media platforms like Twitter, Facebook, and Instagram were initially intended for casual interactions, not as critical sources of information. They lacked the robustness necessary for their current roles in society, leading to issues with moderation and content distribution that weren't considered during their development.
Chapter 3: The Need for Change in Software Development
Today, the internet has become the primary space where people engage and make significant decisions. Just as we would never release an untested prototype of a car, we should not accept the same standards for software that underpins our daily lives. We have established safety regulations for physical products like tools and buildings, knowing they can pose risks.
Software was historically treated like a toy, yet we now expect it to uphold societal structures. To ensure the reliability and safety of software, the industry must adopt the rigorous testing and standards prevalent in other engineering fields. It's time to slow down and recognize the potential consequences of our digital creations.