You Have To Complete The Following Reading Bogost Program
You Have To Complete the Following Readingian Bogost Programmers St
You have to complete the following reading: Ian Bogost, Programmers: Stop Calling Yourselves Engineers. In The Atlantic, November, 2015. Available at: short answers to the following questions (no more than 100 words per question): 1. What are the origins of the phrase “software engineering”? 2. What are the differences between software engineering and the traditional disciplines of engineering? 3. What is the author’s opinion about the Scrum method and why?
Paper For Above instruction
In Ian Bogost’s article “Programmers: Stop Calling Yourselves Engineers,” he critically examines the terminology used within the programming community, especially the term “software engineering.” The phrase “software engineering” was popularized in the late 20th century, primarily adopting the language of traditional engineering disciplines to enhance credibility and professional identity for programmers. This framing sought to impose a sense of rigor and precision similar to civil or electrical engineering but often failed to reflect actual practices.
Unlike traditional engineering disciplines, software engineering lacks many of the physical constraints, safety regulations, and standardized processes inherent in fields like civil or mechanical engineering. Software development is more iterative, flexible, and often influenced by rapidly changing technologies and user requirements. Traditional engineering values precise calculations, physical components, and predictability, whereas software engineering involves abstraction, experimentation, and constant revision, making it less deterministic and more akin to craft than a classical engineering discipline.
Bogost’s stance on the Scrum method is largely critical. He perceives Scrum as symptomatic of superficial professionalism that emphasizes process over actual craftsmanship and understanding. Bogost argues that Scrum and similar Agile methodologies tend to prioritize meetings, roles, and frameworks, often at the expense of meaningful engagement with the complex, creative, and unpredictable nature of programming. He contends that Scrum can foster a false sense of progress and competence, detracting from the true skill and insight required for meaningful software development.
References
- Bogost, Ian. “Programmers: Stop Calling Yourselves Engineers.” The Atlantic, November 2015. https://www.theatlantic.com/technology/archive/2015/11/programmers-stop-calling-yourselves-engineers/414186/
- Sommerville, Ian. “Software Engineering.” Addison-Wesley, 2011.
- Highsmith, Jim. “Adaptive Software Development: A Collaborative Approach to Managing Complex Systems.” Dorset House Publishing, 2000.
- Schwaber, Ken. “Agile Project Management with Scrum.” Microsoft Press, 2004.
- Leffingwell, Dean. “SAFe 5.0 Reference Guide: Scaled Agile Framework for Lean Enterprises.” Addison-Wesley, 2020.
- Pressman, Roger S. “Software Engineering: A Practitioner’s Approach.” McGraw-Hill, 2014.
- Finlay, Peter. “Agile Methods, Scrum, and Software Development.” IEEE Software, 2008.
- Brooks, Frederick P. “The Mythical Man-Month: Essays on Software Engineering.” Addison-Wesley, 1995.
- Williams, L., and Kessler, R. “Test-Driven Development for Embedded C.” Addison-Wesley, 2003.
- Charette, Robert N. “Why Software Fails.” IEEE Spectrum, 1989.