3 ms·
I know the least about EE of any engineering discipline, but aren't there standardized ways to analyze circuits? Are there analogous standardized ways to analyz
by snowwrestler 11y ago
I 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.
- snowwrestler 11y agoThank you, very interesting insights that I hadn't thought about. I think you're right that the essential difference is complexity, and I am taking a "from the top" view. It makes me think of the various disciplines within science. In theory they are a single stack--chemistry can't violate quantum mechanics, because chemical interactions are just very complex quantum mechanical interactions. But they're so complex that the mathematical tools of quantum mechanics can't be practically used for chemistry (beyond super simple reactions). For humans to analyze and manage chemical reactions, we had to invent a new set of analytical tools that are specific to the level of abstraction that we call chemistry. And again, on top of that goes biology, which is after all just very complex chemical reactions. But we don't use chemistry equations (or quantum mechanical equations) to analyze genetic disorders. Maybe software is sort of akin to biology. It's just super complex circuit design, which is itself complex applications of basic electromagnetic theory. On the way "up from the bottom," each time the complexity gets to be too much, we have to invent new mental tools to manage the system at a new level of abstraction. Are the mental tools for software as robust as they are for circuit design? I think about the implications of security when it comes to APIs and packages. I might not want to update my package, but what if a major vulnerability is disclosed and patched? Now I have to update it, and because security and features are often pushed to the same production branch, I might get breaking changes with the patch. I know not every API and package does this, but it seems like many do. Old release versions are only supported for so long, typically. And depending on the patch, it might not even be possible to maintain complete compatibility with old APIs. I agree with you that the key is culture. I've felt a significant shift in managing websites over the past year due to security. Instead of days to apply open source community patches, I only have hours, or maybe minutes. The default is shifting from "test security patches before deployment" to "deploy security patches instantly then see what we need to fix," because it's harder to recover from a hack than to adapt to documented breaking changes. I think the implications of security are only just now beginning to percolate into popular consciousness, which will create demand for higher standards with software "engineering." Look at the recent car hacking stories, or the Ars Technica coverage of IoT security, which got picked up by NPR among others. Thanks for good discussion.