What is an Engineer? » Code Simplicity

In an era increasingly dominated by artificial intelligence, the essence of engineering is being questioned, particularly in the realm of software development. The author seeks to clarify what it means to be an engineer by breaking down the definition into its fundamental components. At its core, an engineer is someone who engages in engineering, which is defined as taking the right actions in the right sequence to achieve a set of intentions. This perspective shifts the conversation away from traditional definitions that focus on physical constructs and opens up the possibility for software engineers to be recognized as engineers in their own right. The concept of "right actions" is pivotal, as it emphasizes actions that align with one's intentions. The author highlights that engineering projects often involve multiple intentions, such as managing resources, satisfying stakeholders, and ensuring user satisfaction. By recognizing and articulating these intentions, teams can avoid common pitfalls, like building the wrong product or misaligning efforts with overarching goals. This intention-driven approach leads to a deeper understanding of what constitutes effective engineering and fosters better decision-making. The importance of sequence in engineering is another critical element. Actions must be organized logically to ensure successful outcomes, as the order of operations can significantly impact the effectiveness of a project. The author illustrates this with a humorous example of washing hands, emphasizing that even simple tasks require thoughtful sequencing. Moreover, sequences can be recursive, with smaller sequences nested within larger ones, reflecting the complexity of real-world engineering challenges. By mastering both the identification of right intentions and the appropriate sequencing of actions, engineers can substantially enhance the quality of their work and contribute meaningfully to their fields.