9 ms·
The Software Industry Is Still the Problem
- randomdata 4y agoThe headline contradicts the conclusion. The software industry offers the exact professionally licensed engineers who are subject to the liabilities spoken of. In reality, is the professional engineering bodies who have not given reason for buyers to want to pay extra for those people. I'm not sure this article improves on that situation, only offering some fuzzy notion that bad things could happen to a business organization, much the same as what will happen if budgets are stretched paying for PEs.
- chrisseaton 4y ago> The software industry offers the exact professionally licensed engineers who are subject to the liabilities spoken of. I thought there wasn't any longer any exam for people to take in software engineering to become professionally licensed in the US?
- randomdata 4y agoCould be. It is a thing where I am from. The software industry doesn't even begin to end at US borders, that is for certain.
- pca006132 4y agoidk, maybe they should try to get politicians aware of the situation and setup regulations for this?
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- mikewarot 4y ago>The time is way overdue for IT engineers to be subject to professional liability, like almost every other engineering profession. Before you tell me that is impossible, please study how the very same thing happened with electricity, planes, cranes, trains, ships, automobiles, lifts, food processing, buildings, and, for that matter, driving a car. How will that solve the problem? Even if we were able to agree on a profession, that people could read and sign on to, would it help? Everything is build on sand. There are zero operating systems that can stand for a year without patching in the face of contact with the internet. Blaming system administrators, programmers, or users isn't going to help fix the fundamental design flaw at the root of our software. We need operating systems that are provably secure upon which to build the rest. Then we can apply the principle of least privilege, and a series of security policies to build upon that. In the mean while, there is one fundamental tool which is under utilized, the data diode.[1] With such a device, it would be possible to monitor a system from the outside world (via the internet, etc.). A polling loop sends data out in a continuous manner (with forward error correction), and a matching server receives the data, checks for errors, an then makes it available to the outside world. You can also use data diodes to allow submission of information from the world, without the danger of exfiltration. Such a system might have helped prevent the OPM breach of 2015 if the database were only allowed to be added, and never queried via network.[2] 1 - https://en.wikipedia.org/wiki/Unidirectional_network https://en.wikipedia.org/wiki/Unidirectional_network 2 - https://en.wikipedia.org/wiki/Office_of_Personnel_Management_data_breach https://en.wikipedia.org/wiki/Office_of_Personnel_Management...
- randomdata 4y ago> There are zero operating systems that can stand for a year without patching in the face of contact with the internet. Similarly, there are also zero buildings, bridges, aircraft, etc. that can realistically withstand attacks of humans despite being built by engineers who have taken on the liability. A sufficiently powerful bomb will win every time. It seems a bit strange to want to hold software to a higher standard here.
- mikewarot 4y ago>A sufficiently powerful bomb will win every time. It seems a bit strange to want to hold software to a higher standard here. A brick fortification built in the 1800s will always offer some defense from small arms fire. You can't cause that fort to attack all other nearby forts. The side effects of the fort are locally limited. A computer that allows unauthorized infiltration of command (not just denial of service) can be used as an offensive weapon by anyone (or any bot) anywhere. [Edit]It's like building your fort out of crates of explosives, instead of bricks.[/Edit] The side effects of a computer are not locally limited. I think it is only rational to require a standard appropriate with such a radically different set of side-effects.
- lr4444lr 4y agoEvery one of these complaints always misses the salient failure of the analogy: do you expect your bridge or your gas line or your house's electrical layout (once it's installed) to be changed every month or quarter to handle new load, produce different results, or even change its feature set? No - these things are planned for and built to do exactly and only the thing they were first designed for. Heck, you can even throw certain software into that mix like medical device firmware. The software industry is doing exactly what people want out of it: becoming highly flexible to individual business and consumer needs in sophisticated customized interactions. Those of us who write it are trying as hard as we can to impose sensible and reusable structure on things, but the public wants constant innovation. Not the same "heat my house when I plus this in" demand they had 50 years ago that would have given us the stability to focus on standards, safety, and efficiency. We're doing the best we can.
- vishnugupta 4y agoThis is my pet peeve too. They also completely ignore the fact that humans have been building physical structures for ~10,000 years where as software industry is less than 100 year old. Give it time to mature.
- brightball 4y agoYou are 100% correct and this needs to be repeated often. There are very few things that can act as an analogy for software development. At the same time, there’s also no other industry that operates at a fraction of the speed of this one.
- cm277 4y agoHmmm, I think TFA misses the fact that software engineering, isn't really engineering any more. We don't develop code that gets deployed and stays in place (well, maybe in embedded systems, but even those are getting IoT'ed). Modern software is a service: it gets updated all the time, it's "hired to do a job" rather than perform a specific function. The latter is finite, controllable and could potentially be certified as an engineering product. The former relies on professional codes (and yes liability as well) to make sure that the service is acceptable. All that is to say that the proper metaphor isn't licensing as for civil engineering or telco networks but akin to licensing for professional services, like medicine, accounting or law. Which means different tiers of service, different expectations and yes much different compensation/service fees. But to get there we have to stop talking about 'engineering' as the correct framework. We're closer to lawyers or nurses...
- WJW 4y agoI'm a bit on two feet about this article: - On one hand, professional liability would indeed be a good thing for overall reliability of our software systems. A "code" for offering software products to citizens would be a good thing. The GDPR is a good step in the right direction for privacy concerns, but there are many other types of concerns that could be covered. - On the other hand, most of the "real" problems in infrastructure software come from adversarial action. Most software systems run more or less fine by themselves, from a professional liability standpoint. Adversarial action is not usually covered by "professional liability". For example, nobody blames the architects of the Azovstal plant that the steel furnaces couldn't stand up to sustained artillery bombardment. - Despite all the talk about how critical software systems are these days, 99% of systems out there is the equivalent of a garden shed and nobody would care if it falls over. Certainly the shed in my own garden would not survive a proper hurricane, but that is OK because a. we don't really get hurricanes here and b. the cost to completely rebuild it would be much lower than bringing it up to hurricane standards. Even Maersk, which is surely not a small target, managed to survive a full blown ransomware hit just fine. (By which I mean, they took a fairly large hit financially but nobody died and no ships sank. By and large all vessels even reached their destination on time) Their IT had to work a lot of overtime for sure, but "the system" is not as vulnerable as people like to claim. So what to do? I would not mind some form of legally mandated checklist to follow that would be mandatory for any company offering services on the internet, but at the same time I don't think it would be very effective in countering the worst threats and I also don't think it would be proportionate for most companies.
- drewcoo 4y agoThe shed's a strawman. How do we handle hurricane damage and other "acts of god?" Not in court, but with insurers. Do insurers currently insure properties with sheds? Yes. Do they insure shabby sheds against hurricanes? Maybe - it's up to them and I'm sure they can figure out if the odds would pay off for them. If your shed exploded into millions of shards of glass when struck by high wind that would be a different story. Or if it spread toxic chemicals all over your neighborhood. Or if it caught fire easily and the fire could spread to other buildings. Who would have thought sheds would make such wonderful metaphors?
- shaftoe444 4y ago"The pretence that corporations are necessary for the better government of the trade, is without any foundation. The real and effectual discipline which is exercised over a workman, is not that of his corporation, but that of his customers. It is the fear of losing their employment which restrains his frauds and corrects his negligence. An exclusive corporation necessarily weakens the force of this discipline. A particular set of workmen must then be employed, let them behave well or ill. It is upon this account that, in many large incorporated towns, no tolerable workmen are to be found, even in some of the most necessary trades. If you would have your work tolerably executed, it must be done in the suburbs, where the workmen, having no exclusive privilege, have nothing but their character to depend upon, and you must then smuggle it into the town as well as you can." Adam Smith, The Wealth of Nations
- dboreham 4y agoThis was good advice in 1700's Kirkcaldy. Doesn't work so well in a globalized marketplace and with products where by the time a defect has manifested, the vendor is long gone.
- agentultra 4y agoCan't agree more. I've been saying for years that we should have some professionalism added to the industry. It doesn't mean that everyone who writes code must be licensed. But to determine if software is fit for purpose you must be. Liability is important and software doesn't have to threaten life and limb to benefit from it. Many engineering professions also protect property and business interests (along with life and limb). What I hope such a system would provide is a means to prevent companies from cutting corners for the sake of profits and give engineers the right to say what is fit for purpose. Too many breaches that have cost economies too much money happen because IT is incentivized to release now and fix it later. Then hundreds of thousands of peoples' financial details are leaked or their pensions disappear. And the current system of liabilities don't protect the end users or dissuade the software industry from continuing on this destructive course. We also don't account for externalities well. Consider how many years PoW crypto mining has been going on, growing, and forcing new coal plants to open to keep up with demand. People in rich countries don't care because it's not happening in their backyard and it is promising to make some of them rich. That happened because we have no social safeguards against bad technology harming the environment/society/etc. You can write a software service that exists to use up as much energy as possible and you will never face any consequences for the damage caused. We barely slap people on the wrist for organized crime let alone corporate crime, negligence, etc. We're not talking about your high school web project here. We don't have to prevent people from learning and building things on their own. I just think we need to prevent companies from rolling the dice with our future and let the folks who know what they're doing run the show.
- chrisseaton 4y agoI recently got professionally qualified as a software engineer with a capital E. I'm still the same regular programmer I ever was! Not sure a piece of paper really solves anything.
- dimgl 4y agoI think it does. I think the barrier for entry is way too low now.
- 4y ago
- civilized 4y agoThe author makes a decent case that some sort of licensing should exist for some types of software development at some point in the future. But the devil is in the details, and the merit of the licensing process needs to be proven. A lot of regulators are valuable but we've also got a lot running around with red tape and power trips that they didn't earn. We're extracting thousands of dollars from low-income minorities for hairstylist licenses that benefit no one. We've got engineering boards punishing people for publicly (and correctly) disputing the math of red light timing. There's too much abuse. Regulation isn't just one way. Regulators need to be held accountable too.
- hibikir 4y agoIt's especially interesting that the author has open source experience, and decides to put a company that went through a ransomware attack as a way of discussing liability. Imagine for a second that the ransomware attack comes via an attack vector because, say, there's a security bug in Spring, giant Java library/ecosystem, that almost everyone pays zero for. Then imagine that this is in a world where the engineer is liable. How does this play out? First, you could claim that the bug is in OSS Spring, and that they can't waive liability. In that circumstance, I'd be surprised if OSS continued existing: You get very little for your contribution in comparison to the liability risk. It's the same for corporate sponsored OSS: Imagine telling your company's counsel that you want to open source a library that is unrelated to the core of your business. Never. So this either has cataclysmic consequences to OSS, or we get to say that anyone making OSS's legal disclaimers are legally binding. So what happens instead? Anyone building applications for a company is responsible for all the bugs in the libraries they chose. OSS will still be mostly poisoned by this. Imagine the fun of taking liability, as some kind of signing engineer, for a half a million lines. And those lines are almost sure to have some vulnerabilities: It's just that we don't know of them yet, and you need patching forever, just like you do today. And along with the patch, we'll have great discussions about who brought in the patch that introduced the vulnerability. Note that this is especially fun in a world where security is covered by this. It's one thing to assume that ones code to control a car will not accelerate without bounds, risking deaths to the passenger. Then your design is narrow, and can have a semblance of good testing. Testing that your code cannot be used as part of a security vulnerability is testing a far wider field of possible inputs. Either way we slice this, all I see is the world building a whole lot less software, because the dangers of writing it make all kinds of products dangerous. We either move to a world where a lot of code is shared and owned by a few companies that take all the liability, and hit major trouble whenever they have a vulnerability, because suddenly they are to blame for possibly millions of breaches, or a world where we share very little code, we evaluate it more thoroughly, and we hope nobody pays attention. I bet my libraries to handle certificates would be worse than the ones experts built today, but I could hope nobody examines them. But yes, as others say, the world could do this right now: We can hire a firm to build something and take the liability for us. It's just that, in general, we don't, because they don't give us anything more secure, or better: mostly more expensive. Instead we might just buy insurance, and hope we don't have too much of a counter-party risk. If we cut security vulnerabilities out of the equation, maybe there is a good defense that the world the author describes might be different, but not worse than the one we live in today. But with security? Tough.
- coldcode 4y agoPeople assume software is just like engineering a bridge, but it isn't. Software changes all the time, due to market needs, due to attacks from the outside or inside, due to legal changes, due to executives who want to be promoted, due to technological changes, due to etc, etc. Bridges do not change, as gravity and wind and temperature and chemistry and physics are in the real world while our software exists in a world of our making, generally built in myriads of layers, often from multiple vendors, and have to interoperate with myriads more other worlds that are also continuously changing over networks which we may not have any control of. Since I started in the early 80's every generation thinks they can standardize things, license programming, make things from perfect reusable parts that work perfectly, and generally turn programming into recipes. Every generation fails. In reality software is a mess because none of those things are possible because complexity is inherent in what we do, and what is expected of us, and there has never been any way to satisfy everything we are asked to do with some magical silver bullshit, err, bullet. Even if you wanted software "Professional Engineers" to be a thing, how would you even do that, with 100's of programming languages, operating systems, software environments and industries all with different needs, and in an industry that changes every single day. Bridges have been built for thousands of years, software has changed radically and continuously since I started in 1981. As soon as you defined some standard to test against, it would be obsolete.
- hotpotamus 4y agoI could complain about software endlessly and I came here to do it, but the comments discussing the analogy breakdown between software and bridge engineering made me wonder - is bridge engineering really so staid and rote? I've seen some beautiful bridges built in the last few decades and it makes me wonder if they get to play around with design as well.
- Verdex 4y agoThe appearance of bridges might change but I suspect that the underlying structural components are much better specified than what we have with software. While I don't know the specifics for bridges, I have seen the specifics for the joist industry (those metal rails with Ws inside them that you see when you look up at the ceiling in a Walmart). There is some design work that an engineer needs to do for any given job. However, they pick the type of joist, material, and wield (etc) based on a book that publishes weight tolerances. And those numbers come from someone taking a joist out someplace and dumping weights on it until it collapses. We just can't do the same thing with software. It's not even clear what kind of weight we would be dumping on software. Human comprehensibility? How do you measure that?
- lapcat 4y agoThe author's analogy is bad. On the software side, he's talking mainly about security. On the other side, he's talking mainly about build quality. But those two things are not really the same. No homebuilder pays liability if a criminal breaks into your house and steals your stuff. That's security and has nothing to do with build quality. If someone steals your car, does the auto manufacturer pay liability? No. Computer security is definitely a problem. But this argument by analogy simply doesn't work. Moreover, non-computer security is a problem too. (School shootings, anyone?) Anyway, talking about toilets and whether they work isn't helpful at all in this case.
- pylua 4y agoIs there a way to make this work in an agile framework ? It is more than just the Engineers this would effect.
- DeathArrow 4y agoSince every other blue collar profession is regulated and only certified individuals can practice it, we will probably get the same at some point in time.
- alaricus 4y agoWhy is it mechanical engineers have standard sizes for all nuts and bolts but software engineers can't pull off the same feat?
- bokchoi 4y agoI'd say some things have been standardized quite well - 8 bit bytes, Unicode, http. It's the application layer that isn't standardized.
- BlargMcLarg 4y agoBecause we're still stumbling on what is and isn't a "bad practice" while companies continue to gaslight the developer population and a few consultants and spokesmen have endless discussions on what should and shouldn't happen. Ergo, there's no incentive to fix it, and every incentive to keep it broken.
- throwaway787544 4y agoStandardization of threads started between private companies around the year 1800, and continued on mixed in with a bunch of other "competing" private company standards. Sick of the lack of a unified standard, William Sellers submitted a paper in 1864 proposing one standard based on an already popular form. Eventually the USG adopted this as a requirement in government contracts, was adopted as United States Standard thread, and later Unified Thread Standard. The standard is maintained by the American Society of Mechanical Engineers and American National Standards Institute. https://en.m.wikipedia.org/wiki/Screw_thread#History_of_standardization https://en.m.wikipedia.org/wiki/Screw_thread#History_of_stan... Get the government to require a standard for all their software and anyone who wants a government contract will have to conform.
- dredmorbius 4y agoFurther parts of that story: - As noted at Wikipedia, wartime mechanisation and the requirements for standard parts to be provided for the new high technology of motorised transport, armour, and aircraft, drove further standardisation. - The noted socialist and collectivist,[1] Herbert Hoover, provided the final push toward standardisation of weights, measures, and engineering components, as Secretary of Commerce. It turns out that military needs and government legal authority and purchasing power can do much to promote standardisation which the free market cannot. A subsequent case emerged during the Vietnam War during which the US Navy, a/k/a the transport and logistics arm of the US military forces, faced a critical problem in delivering supplies and materiel to very underdeveloped South Vietnamese ports. Though there'd been multiple attempts to standardise shipping around a single container size, this proved to be the ultimate nudge which established the TFU, or twenty-foot unit standard. (Now largely seen in its doubled form, the 40-foot shipping container.) ________________________________ Notes: 1. Sarcasm, gentle reader.
- throwaway787544 4y agoJesus Christ, it's like he's read my mind. He's hit the nail with a laser beam. Software continues to be incompetent because there are no incentives to make it competent. We need to hold people liable or they will keep acting like "craftspeople" while building the Sears Tower.
- _9rq6 4y agoThat's why SLAs exist?
- RcouF1uZ4gsC 4y agoIf we regulated software like engineering, it would destroy open source. Before contributing you would need to upload your engineering certification credentials. Good luck getting certified if you are under 18 or do not have a college degree. Also, because of liability issues, employers may prevent you from contributing to open source.
- edgedetector 4y agoTraditional engineering can be done by unlicensed persons. It's just that the final design must be signed off by a licensed engineer. In the same way, open source software can be contributed to by unlicensed software engineers, but if the system will be used in a production product, it must be signed off by a licensed software engineer.
- musicale 4y ago> if the system will be used in a production product, it must be signed off by a licensed software engineer. Now I think you're talking about something that large companies could get behind: a massive barrier to market entry and competition that simultaneously neutralizes the threat of open source software while allowing them to sell it.
- Aerroon 4y ago>It's just that the final design must be signed off by a licensed engineer. This is a great way to establish a new system to elicit corruption like you get with building permits etc. After all, you don't want your design to be stuck for 9 months waiting for approval, do you?
- rossdavidh 4y agoOn the one hand, the problem he discusses is entirely real, and he does not exaggerate the scale of the issue. It is much like medicine in the time of the "four humours". The state of medicine then was a real problem, but if you were to have instituted licensing and professionalisation requirements at that point, it would largely freeze into place a bad situation. The other industries with licensing, have established a good, safe way of doing things. Software has no good, safe way of doing things to establish as code, and teach to new practitioners. I do not exaggerate, either. On the other hand, what he suggests as a solution, would require that innovation be slowed by at least one, probably two orders of magnitude. Any nation which did _not_ do this, would quickly sprint ahead of those who did, and they would quickly be able to overwhelm the capabilities of the nations who had professional licensing requirements.
- petermcneeley 4y agoDo you ever wonder how much medicine has been slowed down?
- rossdavidh 4y agoI do. But I think there are benefits to having the FDA (and etc.) provide checks on fraud, wishful thinking, etc. I'm pretty sure that, on balance, it's worth it. If it had been instituted back in the "four humours" times, it would not have been.
- petermcneeley 4y agoMost of medicine seems about 30 years behind. Imagine what one could do with all that progress; how many lives could be saved/improved. I disagree with your calculus.
- petermcneeley 4y agoDont we want it go go the other way? Dont we want to deregulate quite a few industries? Software is eating the world for a reason. It is unregulated and unrestricted scientific and technological progress. Why would you want to neuter that?
- edgedetector 4y agoWhat industry do you wish to deregulate? Also, software is not unrestricted "progress." It is unrestricted "change," which is not always a good thing.
- spaced-out 4y ago>The good news is the ransomware attack on Colonial Pipeline in May 2021 probably marks the beginning of the end. Comforting as that might sound, it tells us very little about how that ending will turn out. I wonder what level of liability would be reasonable when considering the increasing sophistication of these types of hacks. Going back to the bridge analogy, we would hold the licensed engineer responsible if the bridge they built collapsed because of a thunderstorm, but not if the bridge collapsed because a terrorist or rival nation state bombed it. Which of those situations is more analogous to getting hit with ransomeware or some other type of hack? Say a piece of software from a small company is compromised, should the liability be different if the attacker is some script kiddie versus if it's some hacking group that likely has ties to a foreign intelligence service? Is it reasonable to expect every software company to be able to fend off even the most well-financed attack?
- spiffytech 4y agoI highly recommend this interview series with engineers from other fields who moved into software: https://www.hillelwayne.com/post/are-we-really-engineers/ https://www.hillelwayne.com/post/are-we-really-engineers/
- dgb23 4y ago> The time is way overdue for IT engineers to be subject to professional liability, like almost every other engineering profession. Before you tell me that is impossible, please study how the very same thing happened with electricity, planes, cranes, trains, ships, automobiles, lifts, food processing, buildings, and, for that matter, driving a car. But the people responsible for the Colonial Pipeline are not Software Engineers. SWEs are just workers. Why don't we start to hold the people accountable who extract wealth and give orders? Power and responsibility should go hand in hand. SWEs _want_ to engineer, make things more performant and secure. They _want_ to say No to unnecessary features. This takes time, trust, money. What about the owners? The board? The executives? They make the decisions, want fast growth, more features, less expenses, software to be a commodity and engineers be interchangeable. Managers and sales people, who buy and sell software packages with fancy names on them to get a promotion, don't do the soul sucking work of integrating with a buzzword driven hodgepodge. Shouldn't they be held accountable first? With that out of the way... The example in the article is the Colonial Pipeline ransomware attack. A cyber _attack_. Are bridges, toilets and buildings generally built to withstand arbitrary hostile attacks? But Lack of understanding of how decisions in the IT industry are made, ridiculous examples and bad analogies aside: I still think there is a good point hidden in there somewhere. Namely that good engineering takes time, investment, auditing, standard processes and a strong technological foundation. But we are not there yet. Nobody is laying the foundation to get us there. It's just iterations upon iterations and layers upon layers, features upon features. Before we can even start to think about licensing SWEs, we need to start thinking _very_ long term. Much of the SWE effort is funneled into short term monetary gains, while fundamental technologies like OS's common file formats, browsers, firmware and all that stuff is rarely reconsidered and just patched over continuously. The foundations are _inherently_ insecure and the mindset is wrong. Familiarity and productivity often take precedence over simplicity and robustness. Everyone thinks they are entitled to telemetry and other user data and most software is closed source. How do you reason about black boxes? How do you trust them? Also who will do the licensing? The people who tend to push for these things while shitting on other software practitioners don't inspire much confidence IMO. I have so many questions...
- musicale 4y ago> But the people responsible for the Colonial Pipeline are not Software Engineers Precisely. It's the company with it's "disclaimer of all warranties express or implied" that would/should be liable. I'm not sure how this works for free/open source software however. Presumably liability passes to whoever is charging for the system or service.
- toyg 4y ago> If any science fiction author, famous or obscure, had submitted a story where the plot was "modern IT is a bunch of crap that organized crime exploits for extortion," it would have gotten nowhere Has Kamp ever read any SciFi published after the '70s? That's a pretty common trope in cyberpunk and subsequent works. Heck, it's a staple of Mr. Robot, hardly a niche production.
- flappyeagle 4y agoAuthor misses the point entirely. Almost nothing in the real world is engineered to prospect against motivated malicious actors. Even security devices like locks and fences are trivially defeated with the right know how and tools.
- musicale 4y ago> "If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." If architecture, construction, and civil engineering firms could implement automatically binding license agreements that absolved them of all liability and responsibility, we'd probably see similar results.
- musicale 4y ago> The time is way overdue for IT engineers to be subject to professional liability, like almost every other engineering profession. Sounds like a good idea, right? > Poul-Henning Kamp spent more than a decade as one of the primary developers of the FreeBSD operating system How does professional liability work when FreeBSD security flaws result in power plants shutting down or gas lines exploding?
- mbrodersen 4y agoMost software doesn’t kill people or cause any other type of financial/physical damage if it falls over. So regulating all software is a bad idea. However I 100% believe that all software that is critical to saving lives/avoiding damage should be formally proven correct using proof assistants. The people who are qualified to do this deserve to be licensed Software Engineers. People who can’t do this should not be called Software Engineers and should not be legally allowed to work on safety critical software.