Why the software community banned this coding construct

A brief history of the GOTO statement, Edsger Dijkstra's famous critique, and why it is considered a code smell today.

#Programming #SoftwareDevelopment #ComputerScience #Coding #TechHistory #Fortran #COBOL #ALGOL #CProgramming #Cpp #GoLang #GOTOStatement #ControlFlow #ProgrammingHistory #CodeSmell #Dijkstra In this video, we go over a brief history of the infamous go to statement, the unconditional jump construct present in earlier programming languages like : Fortran, Algol, Cobol and later on relatively younger languages like c, c++ and go. We talk about the famous go to statement considered harmful paper by the computer scientist **Edsger W. Dijkstra,** and how it may have contributed in the reduction in appeal and popularity of the go to statement among developers in the software industry as a whole. We discuss the reasons why the use of the go to statement is now treated as a code smell and whether this approach / mentality is warranted in the production of reliable and bug free software. Thoughts? Clean coding course: v2.scrimba.com/introduction-to-clean-code-c025?via=DevToolsM… Join us on x: x.com/DevToolReady