Lone Star Ruby Conference 2010 Real Software Engineering by Glenn Vanderburg

I would say that this blog post is half right. The half that's not right is glaring. > the pyramids have had 100% up-time with no human maintenance It helps that there is hardly any rain in the desert. Water would foul up the structure in a matter of years. > dependencies are added like seasoning. Hundreds of packages. Thousands of foreign lines of code make their way onto your software routinely True, and I think NPM JavaScript exhibits the worst of this behavior. > Problems are expected and fixed on the fly, somewhat haphazardly: ... push a patch ... code scanning ... dependa-bot ... DevOps True, and I remember when software releases were treated with much more care and quality because it costs a lot to ship a CD or game cartridge rather than a download. > More waterfall-y. That's not a good thing. Having a short feedback cycle from implementation back to design is a big win for software development. Waterfall is the dark ages when we didn't know better. > This is where minimalist software is built. Agreed. > No build process That doesn't make any sense, unless you're writing machine code directly in hexadecimal. > no outside dependencies I agree with minimizing dependencies, but there's no such thing as no dependencies. I dare you to avoid any of these libraries: HTTP (especially HTTP/2 and 3 which are much harder than HTTP/1), TLS/SSL, TCP/IP, hardware drivers, compilers, data codecs like DEFLATE, multimedia codecs like AVC and AAC. > There's no need to be constantly refa

I thought calling programmers "engineers" was very odd until I saw this great talk: Real Software Engineering by Glenn Vanderburg Lone Star Ruby Conference 2010 ▶ this video Software engineering as it's taught in universities simply doesn't work. It doesn't produce software systems of high quality, and it doesn't produce them for low cost. Sometimes, even when practiced rigorously, it doesn't produce systems at all. That's odd, because in every other field, the term "engineering" is reserved for methods that work. What then, does real software engineering look like? How can we consistently deliver high-quality systems to our customers and employers in a timely fashion and for a reasonable cost? In this session, we'll discuss where software engineering went wrong, and build the case that disciplined Agile methods, far from being "anti-engineering" (as they are often described), actually represent the best of engineering principles applied to the task of software development.

This talk describes how the waterfall development model was a caricature that got accidentally turned into reality: ▶ this video "Lone Star Ruby Conference 2010 Real Software Engineering by Glenn Vanderburg"

This talks about the same topic: Lone Star Ruby Conference 2010: "Real Software Engineering" by Glenn Vanderburg: ▶ this video

I always thought calling programmers engineers was very weird until I watched this great talk: Real Software Engineering , Glenn Vanderburg, Lone Star Ruby 2010 ▶ this video which explains what various kinds of engineers actually do. Not at all dry and boring like it might sound! From the YouTube blurb: Software engineering as it's taught in universities simply doesn't work. It doesn't produce software systems of high quality, and it doesn't produce them for low cost. Sometimes, even when practiced rigorously, it doesn't produce systems at all. That's odd, because in every other field, the term "engineering" is reserved for methods that work. What then, does real software engineering look like?

I first came into contact with this article via ▶ this video , which is a pretty decent analysis on how people misinterpreted the original concept.

Real Software Engineering, by Glenn Vandenburg. Not a perfect talk (especially the conclusions IMO), but a very good exploration of how some of the common beliefs in the field of software "engineering" came to be, and how something resembling actual engineering practice might be beneficial and practical. Link: ▶ this video Abstract: "Software engineering as it's taught in universities simply doesn't work. It doesn't produce software systems of high quality, and it doesn't produce them for low cost. Sometimes, even when practiced rigorously, it doesn't produce systems at all. That's odd, because in every other field, the term "engineering" is reserved for methods that work. What then, does real software engineering look like? How can we consistently deliver high-quality systems to our customers and employers in a timely fashion and for a reasonable cost? In this session, we'll discuss where software engineering went wrong, and build the case that disciplined Agile methods, far from being "anti-engineering" (as they are often described), actually represent the best of engineering principles applied to the task of software development."