π΄πβοΈπ» 75 Year of Learning to Engineer Software - Silvio Meira - ICSE 2026 keynote
π€ AI Summary
- ποΈ Software engineering historically functions as a reactive discipline where practitioners learn mostly through post-failure reflection [03:06].
- π₯ The fieldβs true origin lies in practical commerce, such as the 1951 LEO bakery computer, rather than academic labs [03:43].
- 𧩠Architecture and abstraction outlast specific code, as seen in the enduring relevance of TCP/IP and Unix principles [09:01].
- π Discipline in software engineering often involves removing features and maintaining simplicity rather than constant addition [07:40].
- π£ The Amazon API mandate demonstrates that governance and interface constraints are fundamental engineering tools [11:08].
- π Digital systems are interventions that construct new realities in a phygital space merging physical, digital, and social dimensions [17:09].
- π οΈ The Adaptive Interventionist Method (AIM) provides a recursive framework for learning before and during the build process [15:14].
- βοΈ Ethics must be a core design parameter (SBA: Society, Politics, Advancement) rather than a final compliance checklist [22:18].
- π€ AI-native engineering shifts the focus from writing code to designing, specifying, and taking responsibility for interventions [37:12].
- π Software engineers must adopt the formal responsibility and rigor of civil engineers as their work has irreversible societal impacts [34:08].
π€ Evaluation
- βοΈ The speaker emphasizes a shift from coding to high-level intervention design, a perspective echoed by the Association for Computing Machinery (ACM) in their reports on the future of computing education.
- π While the speaker posits that code-writing is becoming obsolete for many, the IEEE Computer Societyβs Software Engineering Body of Knowledge (SWEBOK) continues to emphasize foundational technical implementation as a prerequisite for rigorous engineering.
- π‘ Further exploration into the legal liability frameworks for software engineers would clarify the speakerβs comparison to civil engineering professional standards.
β Frequently Asked Questions (FAQ)
π§ Q: What is the primary goal of the Adaptive Interventionist Method?
π°οΈ A: AIM seeks to shift software development from a cycle of failing and then learning to a process of learning before and during an intervention through recursive inquiry and ethical modeling.
π’ Q: Why is the LEO computer significant to software history?
π A: Built by a bakery in 1951, it moved software into the real world, pioneering essential concepts like job scheduling, subroutines, and acceptance testing for commercial use.
βοΈ Q: What does the SBA framework represent in software design?
π³οΈ A: It stands for Society, Politics, and Advancement, requiring designers to evaluate who is affected, what power structures are encoded, and if the project creates genuine progress.
π Book Recommendations
βοΈ Similar
- π Software Engineering A Practitioners Approach by Roger Pressman and Bruce Maxim from McGraw Hill Education provides a comprehensive foundation on the disciplineβs evolution and methodology.
- π The Mythical Man Month by Frederick Brooks Jr. from Addison-Wesley Professional remains the definitive source on the human and organizational challenges of complex software systems.
π Contrasting
- π Clean Code A Handbook of Agile Software Craftsmanship by Robert Martin from Pearson Education focuses on the granular importance of implementation and code quality which the speaker suggests is becoming secondary.
- π The Lean Startup by Eric Ries from Crown Publishing Group advocates for rapid market-driven experimentation that the speaker critiques as often lacking scientific and ethical rigor.
π¨ Creatively Related
- π The Laws of Simplicity by John Maeda from MIT Press explores how to balance simplicity and complexity in design and technology.
- π Seeing Like a State by James Scott from Yale University Press examines how large-scale social engineering interventions can fail when they ignore local context and complexity.