3 ms·
"All good points. "software engineering" is how we take raw code and turn it into reliable systems." No, that's software development. It comes in many forms. Y
by nickpsecurity 11y ago
"All good points. "software engineering" is how we take raw code and turn it into reliable systems."
No, that's software development. It comes in many forms. Your academic example is a good one of a failed approach.
Software engineering is applying engineering practices to software to produce The Right Thing. Examples of it are Cleanroom, Praxis' Correct-by-Construction, Green Hill's PHASE, and so on. These connect requirements to clear specs (semi-formal or mathematical) to code. The systems are usually abstracted, modular, and layered in a way to allow testing of individual components and how they connect. Both successful and failure states are documented with fail-safe methodology. Design/code reviews, testing, static analysis, automated build processes, and so on are common here. The results are consistent, effective, and with low defects. Much like engineering.
Then, there's software development and programming in general. They're selectively applying some of this stuff but no way looks like engineering. The results are likewise all over the place.
"Open Source projects run by communities with a focus towards testing, documentation, and maintainability are the best thing to happen to software engineering."
All of that was happening in software engineering back in the 1960's-1980's for companies that tried to do the real thing. Just formal, code reviews and testing got incredible reliability gains (see OpenVMS). High assurance systems did much more. An article, about both security & software engineering, described the very best of security in 1970's with specific practices and results they had. Most software development hasn't caught up to that level despite the fact that every aspect of it was exceeded in academia and professional communities focused on quality/security.
What I do agree with is that OSS projects using such methods have gotten them mainstream adoption in many OSS and proprietary projects. The benefits were real. However, the stuff already existed for decades, was even mandated by some standards, and the mainstream is a pale imitation of all that. Improving, for sure, but it's actually them that still have much to learn. If only the will.
"We pretty much need two divisions here: "software engineering (social)" and "software engineering (technical)". "
This I'm less sure about as now we're on an open-ended topic. :) There's definitely social and technical factors. I'd say the technical side is designing, implementing, and verifying any aspect of it. You need to understand the tech to varying degrees to do each. At same time, there's a social component because everyone is working together and one can affect another. seL4 teams, development and formal methods, were an example where constant communication solved issues where one side's abstraction/implementation was causing severe issues on the other. So, it's all technical and social minus maybe project manager or owner(s) making the money off it. ;)