3 ms·
Maybe software "engineering" just isn't there yet. I don't get the feeling that there practices and processes that everyone writing software agrees are the abs
by snowwrestler 11y ago
Maybe software "engineering" just isn't there yet.
I don't get the feeling that there practices and processes that everyone writing software agrees are the absolute right way to do things. It seems more akin to a craft than to an industrialized application of basic science, like a bridge or ship.
What is the equivalent of Newton's Laws, for software? What is the equivalant of logarithmic tables and books of standardized information on materials? What are the equivalent of standard alloys and formulations of concrete?
I think that programmers and software companies will eventually be held accountable for quality. But first, there needs to be some strong consensus around how to measure and test for software quality. That might take a while.
- dllthomas 11y ago"But first, there needs to be some strong consensus around how to measure and test for software quality." Liability for damages seems a start, though as I have said repeatedly I think it should rest first with whoever deployed the software in question.
- maldusiecle 11y agoIt's a particularly vicious kind of law and order conservatism, to invent the punishment before one invents the law.
- mindslight 11y agoWhere are the equivalent reams of standardized information for Electrical Engineering (circuits)? Circuit topologies are like design patterns. Lists of components are like package repositories. Datasheets are API documentation - both are fields where the majority of details you have to deal with were decided by someone else. It's interesting, when viewed through the lens of this discussion, EE seems like an early form of software - using specific materials for their ability to stay out of the way, seeking components that are a mathematical ideal, extremely reconfigurable, complexity is the enemy. Which isn't surprising - it's not like people were blind to the advantages of abstraction before computing. Perhaps EE was the horse running out the barn door with the term "Engineer", but he's long gone now. (Mechanical Engineering is in a similar position - there are many people that you would call engineers, but they're not PEs nor responsible to one. Safety is achieved by product regulation and testing, rather than a trusted creation process)
- snowwrestler 11y agoI know the least about EE of any engineering discipline, but aren't there standardized ways to analyze circuits? Are there analogous standardized ways to analyze a piece of software? My understanding is that electrical engineers come out of school, and often go right to work professionally. Whereas graduates of computer science or software engineering college programs sort of famously are usually bad at building "real software" until they've served an apprenticeship of some kind. I mean, a datasheet describes a physical thing that doesn't change, right? If you install a hardware circuit, it's going to work the same way until entropy takes its toll. Whereas APIs and packages are far more complex, and change constantly. I agree that EE is the obvious precursor to software, but I think they are very different today. Companies that were great at EE--like HP, Sony, Phillips, Toyota--have struggled with software. Electrical engineering at least has a few hundreds years of electricity physics experiments and theory behind it. If we think of the basic science of software, I think of computer science or information theory. Neither is much over 70 years old at this point.
- mindslight 11y ago> aren't there standardized ways to analyze circuits? There are basic quantities (current, voltage, time), and every component has an associated formula that model how they behave. But software is similar in that every instruction (eg opcode, function, or program statement) has equivalent well-defined behavior. > electrical engineers ... often go right to work professionally Sure, but they still start off slowly and work under someone more senior. They certainly don't come out of school with an understanding of what circuit topologies are practically used or a great intuition of which factors actually decide designs. > Whereas APIs and packages ... change constantly Only if you constantly change them out! Chips have revisions too. All of these differences strike me as being about scale of complexity, rather than full on new phenomenon. And it's true, for electrical engineering complexity is bounded by cost, even though there can still be a lot of complexity in a cheap chip (but the manufacturer is incentivized to get this exactly right, too). Whereas with software we're often burning GHz chips to perform the same function that 5MHz micros handled just fine. So I think the root of the disagreement is whether you approach it "from the top" or "from the bottom". My above argument is coming from the bottom - EE battles a lot of similar facets as software, just a lot less complex. If you take software engineering as being fundamentally about managing complexity (and therefore imply that it couldn't really get started until we had horsepower to waste), then I'd call that viewpoint "from the top" in a sense. Which is probably more appropriate, especially as complexity grows and grows. But that doesn't mean that the "bottom" "fundamentalist" viewpoint is useless, either. It's not that engineering principles are inapplicable to software, but that they are ignored as a result of the environment the discipline finds itself in. One way to change that environment to encourage more rigor is to change the culture of the field, which IMHO can be helped by calling it "Engineering" and pushing it more towards so, rather than modeling the culture around eg flaky webcrapps.