17 ms·
Why are we so bad at software engineering?
- davidw 7y ago> Many common practices in software engineering come from environments where failures can be retried and new features are lucrative. And failure truly is cheap. If any online service provided by the top 10 public companies by market capitalization were completely offline for two hours, it would be forgotten within a week. This premise is driven home in mantras like “Move fast and break things” and “launch and iterate.” Good article. We're not really that bad at it, we just optimize differently than building airplanes or elevators, for most things. No one cares if the site I built for the local bookseller goes down at 3 am for an hour or two. Or even for a few minutes during business hours.
- exabrial 7y agoSoftware Engineering is new. The romans were working on solving civil and mechanical engineering problems hundreds of years ago and we've had a lot of time to study their failures. Unfortunately, our industry is dominated by an obsession over "use the latest, cuz is the greatest" mindset, where if you're not using the hottest new language or sexy framework, you're already behind somehow. I can imagine maybe it was this way when the romans were trying to figure out how to build roads. "Oh hey, did you hear how Steve built his road? Yeah, they compacted gravel an inch out of time underneath the bed. Something about water drainage. Oh and they're waaaaaay more productive. Yeah, productive. Lets do use that framework for building our roads!"
- hyperpallium 7y agoNot just new, but always new: > There need be no real danger of it ever becoming a drudge, for any processes that are quite mechanical may be turned over to the machine itself. https://en.m.wikiquote.org/wiki/Alan_Turing https://en.m.wikiquote.org/wiki/Alan_Turing
- ScottFree 7y ago> Software Engineering is new. I believe one of the examples for extreme reliability used in the XKCD cartoon included in the article is air travel, which is about as old as computers. I was told once that the reason air travel is so reliable is because they have mechanical backup systems for when the electronics inevitably fail. Is that true? How reliable are electronics as a whole?
- esmi 7y ago> How reliable are electronics as a whole? Given sufficient time, budget and management will very reliable system can be made. The probes have software too, so there’s that... https://en.m.wikipedia.org/wiki/Voyager_program https://en.m.wikipedia.org/wiki/Voyager_program
- JackRabbitSlim 7y agoIf an aircraft's engine dies mid flight pure physics of falling generates speed and the plane at speed generates lift so you slowly descend in a (semi) controlled manner. In a flight sim you just plummet to the ground unless someone thought far enough ahead to your virtual engine dying and implemented ambient aerodynamics to make sure a gliding mechanic would work.
- HeyLaughingBoy 7y agoNo, it's not true. Air travel is as reliable as it is because it's considered to be a system Airplanes, their design, manufacture and maintenance. Airports, communication systems, procedures for entering, transiting and exiting an airspace, fault reporting, accident investigation and much more. All of those things are part of the "system." What a lot of people fail to do when making comparisons with software is to look at the act of coding in isolation from everything that surrounds it. That leads to a very skewed perspective.
- Supermancho 7y agoObligatory (and still relevant): https://vimeo.com/9270320 https://vimeo.com/9270320
- ScottFree 7y agoI have his book and refer to it often.
- gfs78 7y agoWhy are we so bad at software engineering? Because most software comes without any liability.
- nomel 7y agoProcrastination is usually desired, for timely completion, and almost always rewarded, for the same.
- topkai22 7y agoI completely agree. At the some point, businesses need to to have reason to say "no, what you want is feasible, and we won't risk the consequences of failure." For safety critical applications, technical decision makers need to have reason to say "no, we can't do this, and we won't because my career and possibly freedom are at stake if we do." Right now a huge portion of the risk of software failure to software builders is reputational. This can be sufficient, as pointed out in many cases in the article, but as we see in these examples is often not.
- nottorp 7y agoI wonder if you'd like to pay for developing software that comes with full liability :)
- poulsbohemian 7y agoWe're bad for several reasons: -- Outside FAANG type companies, most businesses are not willing to actually put in the investment it takes to do engineer software. They want a "solution" as cheap and fast as they can get it. I'm not even passing judgment here, as in some cases that approach is entirely justified. -- Software is a world of eternal September, where the industry memory is only about five years long. Lots of us move on to other fields or roles and the memory is forgotten, and here comes another generation to reinvent the wheel all over again. -- Education: Computer science is not software engineering. Code schools are teaching programming more than software engineering. Thus, software engineering is something learned through doing rather than something studied as a discipline.
- taylodl 7y agoI'm curious, what evidence do we have that the FAANG type companies are significantly better at software engineering than anyone else?
- poulsbohemian 7y agoWhen we look at the entirety of companies around the world, it's reasonable to think that there are non-FAANG companies that could be just as skilled. That stated, my own casual observations: 1) The FAANGs that I've seen have significantly more robust practices than the non-FAANGs. Everything from office conditions to build / test / release systems. The reason for this is: 2) Incentives. When your business is completely focused around software technology, you are incentivized to build out systems and processes that other places would not, because it is core to your business. Anecdata from many years in and out of various kinds of companies, as both an employee and/or road-warrior consultant.
- Supermancho 7y agoI still see bugs and rollbacks in FAANG releases. I conclude that the incentive isnt enough. The practices are inadequate.
- soganess 7y agoTime. Airplanes reuse and refine, reuse and refine the same system, more so with elevators. Software is often greenfield. Realistically, software projects get budgeted for half/third of the time they actually need to be anywhere near complete. Then following the "delays" that should have originally been budgeted in, you might be over or under that more realistic estimation, but the software is worse for it. Why? Because the engineers were stressed/crunched/whatever into performing worse under the false pretense that "we're almost there," when that is not the case. If companies put a greater emphasis on correctness and budgeted time/money/testers/etc for it, things would be better. This low grade output is what the industry wants and that is what it is getting. People in charge of scheduling may say they care about correctness, they never really do, they care about fast and the appearance of some facsimile of function ("it looks like it works"). Imagine if you went to your higher up and said that the 6 month greenfield voting app, would actually take 1.5 years and require more resources just to ensure correctness. You would just get taken off the project. "It's just a voting app, one screen and server." But that misses the point, because it's a voting app, it needs to be hardened, just like an airplane. So you learn to shut up and either produce worse output, or work overtime to make something halfway decent. Either way it basically goes unnoticed until something blows up.
- Frost1x 7y agoIt doesn't help that developers pretend this crap isn't going on either. Verbalize and acknowledge it but everyone's so worried that unrealistic requests and budgets are somehow actually realistic and they're just underperforming compared to their peers. So many actually suffering from imposter syndrome and worried that they're suffering from the Dunning-Krueger effect. Every group I've worked with seems to start in a defensive state projecting confidence but I casually admit to my struggles with everyone on the team and folks start to open up. By the end, you have a team of developers who can help set more realistic expectations. The less developers communicate amongst themselves honestly, the more they can be exploited by unrealistic expectations for development. It's a much nicer environment when everyone knows and admits they're slinging garbage code because of resource constraints than everyone pretending they're not.
- taeric 7y ago
- fhood 7y agoI don't think that lack of incentive is the primary reason that software is so unreliable. It might be part of the reason, maybe even a significant part, but not more than that. I suspect that software is just ridiculously hard. The complexity ceiling for programming is insanely high, and there is very little tolerance for oversights. If I'm designing a drill for instance, I don't have to consider every possible use the drill will be put to. I can just overbuild the crap out of it, and cover 95% of my bases. Can you think of an analogous man made thing that is as inherently complex and fragile as a major distributed system? And importantly it never really stops. As soon as a reliable solution to a problem has been discovered we immediately use it to build a billion complex new systems on top of it. And testing is hard. And programmers rarely get to truly specialize. We spend a great deal of time learning on the go because it would be nearly impossible to truly be an expert in a field where the tools and goals change so rapidly. I'm sure I could come up with more if I kept thinking about it.
- jakevoytko 7y agoAuthor here! This is a good point. Earlier drafts of my post did include "the unbelievable depth and complexity of the modern technical stack" as a factor. I deferred it until a future post because I think that we accept that we don't fully understand the systems and stack because of our incentives. Imagine if the stakes were much higher: if our software was hooked up to pacemakers that stopped pumping blood when the software was down. This isn't so crazy: people who design airliners go on the test flights. We would band together as an industry to produce guidelines and recommendations around safe ways to run sites. We'd quit rather than work on a doomed project for a paycheck. Any work would require something equivalent to expert certification and design validation at every layer of the stack. We'd do everything in our power to avoid creating these emergent systems. But the situation is reversed - in many circumstances, the cost of failure couldn't be lower. We tolerate the fact that we don't understand the emergent systems that we create because it doesn't matter enough for us to care. But I don't want to make it sound like I'm dismissing you're point. You're right and it's super important. I think there's a better angle that I can use to explore this. It might be "Why do so many websites get hacked and lose our personal data?", but I feel like that doesn't fully capture it. I have to think about it. But this seems less relevant to the election case, which is what I wanted to address - that these projects fail because "launch and iterate" has become so ingrained in our process that it's difficult to recognize when it doesn't apply.
- miles7 7y agoOne thing I didn't see mentioned about creating software is that the tools and the systems often have serious problems to begin with, even before you start writing a program. Some well known examples are: - major programming languages such as C don't do enough to help with memory safety issues - lack of explicit types in python function arguments can lead to surprising bugs which recur again and again - operating systems and platforms, such as different web browsers, adhere to widely different conventions about how dependencies on other libraries and code is managed
- Supermancho 7y ago> the tools and the systems often have serious problems And running a train over a floating bridge has serious problems, but it is done. These software "problems" are trivial compared to algorithmic complexity when analyzing 10billion events a day in countless ways realtime.
- deleted 7y ago[deleted]
- sparker72678 7y agoWe just stricter type systems.
- _bxg1 7y agoSlightly off-topic, but here's what I would've done: just build a website. No real client-side code; lean on the HTML platform for everything it can be used for. HTML is the simplest, most stable, and most battle-tested client-side framework ever created, and it's stateless and runs on all devices without even an installation step. Toss some CSS on there to make it look pretty; CSS is stateless too so it won't introduce any real bugs. It doesn't have to look perfect; you're not marketing it to anyone. You're just collecting input from users who don't have a choice of product. For the back-end use something dead-simple like PHP or NodeJS. The business logic can't be that complicated; I assume it's really a very simple CRUD app. Just accept form submissions, authenticate, validate, drop it in the database. Done. Spin up a couple of hand-managed VMs on DigitalOcean or the like for hosting both the databases (probably just one database?) and the web servers. It's not a small user load, but it's much smaller than the typical internet company, and it only needs to run for a few hours. You don't need automated scaling and restarting while you sleep. Sit a task force at their desks during the event to repair any outages as they happen. Use the right tool for the job. Your stack should be exactly as complicated as the task demands, and no more.
- zweep 7y agoSoftware is built like crap because when it fails it doesn't kill anyone. Except the software that does kill people when it fails, and that's engineered properly -- not perfectly, but in line with other things like airliners and elevators.
- lhoff 7y agoA former Professor of mine published a paper on a very related topic. He interviewed 54 software developer at the International Conference on Software Engineering. I found it a very nice read. https://arxiv.org/pdf/1911.09971.pdf https://arxiv.org/pdf/1911.09971.pdf
- lioeters 7y agoIndeed, a fascinating study, thank you for the link. Breaking down the summary: Conclusion: More software engineering research should concern itself with: - emergence phenomena - how engineering trade offs are made - the assumptions underlying research works - creating certain taxonomies. Such work would also allow software engineering to become more evidence-based.
- vidanay 7y agoBecause software engineering is recursive and has an unlimited stack.
- proc0 7y agoExcept airplanes and elevators need software and therefore software engineers so this should really be about web and app development.
- deleted 7y ago[deleted]
- scarejunba 7y agoWe're not. We're great at it.
- chasing 7y agoThe Iowa caucus app didn't fail because "we" are bad at software engineering. It failed because someone did a shitty job of understanding the problem space, deciding on an appropriate solution, and finding proper resources to make sure that solution was well-implemented.
- tryitnow 7y agoI think properly implementing a solution appropriate to the problem space is the literal definition of engineering. So "we" aren't bad at software engineering but someone definitely is.
- flukus 7y agoThe someone in question were inexperienced devs fresh from a bootcamp. This is a recipe for failure in every industry from making coffee to making spacecraft. Perhaps software is somewhat unique that we don't appreciate experience.
- chasing 7y agoI'm saying the fundamental problem was not the software implementation but the non-engineering decision-making surrounding it.
- HeyLaughingBoy 7y agoWhat the poster is saying is that the project management aspects are a part of engineering a product. It's an opinion I happen to agree with.
- camgunz 7y agoIt's a lot more nuanced than that. Upfront I'll say I know the people at Shadow and worked right next to them at HFA. They're super competent (they worked on some of the more critical things) and some of the best people I know. Just so you know where I'm coming from. I haven't talked to them about any of this. Political software is very wild west. There are dynamics that are just impossible to anticipate, like every Saturday this vendor's response time drops to nothing because they do weekly backups, or we're coordinating all the votes through this person but they've never used a smartphone before. There are some fundamental truths here: - these systems and processes are underfunded, ad-hoc, and run by people who are compromised in significant ways (haven't slept more than 3 hours in 2 weeks, no experience with technology, responsible for literally 30 things, downright incompetent but bodies were needed, drug/drinking problems). - we're now in an age where these systems have to be secure against state-level actors, and we are woefully unprepared for that in every way you can think of. - very little in our political system can hold up to scrutiny. Caucuses in particular are and always have been junk, but even elections are... maybe impossible to verify. And even if we could perfectly record every vote, externalities (weather, voter suppression, malfunctions) and people's bad memories ensure there will always be a gap between the will of the people and the results of an election. They (and everything else about this process) are fundamentally imperfect. At HFA we dealt with this by planning for it from the beginning, and when you're the presidential campaign you can do a lot to combat these fundamentals (run drills, hire super competent people for pennies who will work for you out of patriotism, run red teams, strongarm and replace vendors, etc). We still made mistakes that haunt me. It's just how it goes. Nowhere else in politics is like that. So you do your best: don't put your app on the app store, subject to anyone downloading it and review by Apple/Google, use MFA even though it will undoubtedly confound 80% of your volunteers. Hope the internet holds up in rural areas or gyms with satellite trucks and crowded APs/towers. Hope no one learns the numbers of your backup hotline. Hope people know the rules of the caucus and count perfectly so the results aren't tainted and called into question ad nauseum on national news media. Hope no one thinks you're part of a conspiracy to cheat their favorite candidate and doxxes you. Make your app as simple as possible. Accept your client's insistence on secrecy in the name of security even though you know training and testing are essential. Hope there's no quirk in the vendor's API that will reject results on caucus night. This whole thing is like a Rorschach test. Are you a person who thinks tech has no place in elections? That's what you see here. Are you a Sanders supporter who thinks there's a conspiracy (not for no reason) against him? Do you think Democrats are fundamentally incompetent? Do you lament the state of software robustness? Etc etc. I would implore people who are falling into into this stuff to recognize these mental reflexes. Very few people know anything about how any of this works (I certainly didn't) or the details of what happened in Iowa, and if you don't, well probably shouldn't extrapolate from this situation then.
- rednerrus 7y agoWe don't have standards in software engineering. We don't reuse components effectively. It's difficult disassemble software and reengineer components.
- marta_morena 7y agoThis article doesn't make any sense. It already fails at the premise. Airplanes and elevators have nothing in common with code written by normal software companies. They optimize for a compromise between short-term gain and long-term gain. In essence, a startup can mathematically proof its software and go bankrupt before they even reach a prototype stage. Or they can shell out utter crap quickly, get some early feedback, funding and beta testers and slowly figure out what to improve first for the biggest bang. Same goes for giants, like Google. They technically have the resources to prove SOME projects and they DO. For instance, Amazon proves their hardware virtualization software and other core pieces, where bugs would undermine the safety of the entire cloud. I am getting a bit sick of "Why is software engineering so bad compared to XYZ". All the people asking are either not in this field or are junior engineers who just don't yet understand why things are the way they are and why writing bug-free, mathematically proven software is infeasible, unnecessary, impractical, undesired, etc. Consider another analogy. When building a house, how expensive is it to decide that you actually want to have a ceiling with 5 meters high in the second floor, because the buyer of that floor wants higher ceilings? Simple: Tear down the building and start over... In software? Usually it comes down to adding an IF-statement or some such. Software follows completely different economic principles and serves completely different needs. There is at least one dimension though where this problem currently shines through: Self-Driving Cars. I think auto-pilots in self-driving cars SHOULD follow the same rigor as airplane auto-pilots and they are most certainly not doing that, which will and already has resulted in lost lives.
- jakevoytko 7y ago"They optimize for a compromise between short-term gain and long-term gain" Hey! Author here. This is the exact point that I make in my essay. I don't compare it to any other fields, and certainly don't mention airplanes or elevators. I explain how this compromise is deliberately reached for people who aren't familiar with the dynamics of software projects. I recommend that you read the post! It sounds like we agree on a lot.
- TrackerFF 7y agoMy take on this problem is that other (engineering) fields operate with much, much longer time frames - not to mention that they also have vastly more experience and best practices to rest on. Software is young, things move very fast, and new practices can emerge quickly (and older get canned). Imagine if aerospace company was to design, test, and build a new airplane in only 6 months. It would probably end up as a disaster. In the realm of software, it is very likely that you need to come up with something new, very fast - you don't always get the luxury to step back and lay the proper groundwork - you're doing it on the go.
- karatestomp 7y agoOur tooling's pretty shitty, generally, isn't well-standardized or anywhere close to it across the industry, is changing rapidly (largely not to any real purpose, though sure, sometimes improvements slip in) and we're all expected to become semi-competent (nowhere near enough time or brain space for full competence) on an absurdly large set of these tools—not just using them, but using several different ones for similar purposes but with different interfaces and quirks (boy do they have quirks), how to set them up, how to fix them when they break, and so on. Oh and you can make a name (and pile of money) for yourself if you manage to promote some mediocre beta-quality-at-best tool and trick enough other people into using it, and if people call you out on it they're the assholes. Every thought experiment that immediately comes to mind, in which other professions of various sorts had to deal with some similar situation on an ongoing and apparently never-ending basis, read as absurdist comedy. Yet here we are. [EDIT] ok here's a fun one: imagine if framers had to use a different hammer depending on the brand of wood at the job site. Like, hammer weight is different and you even hold it differently. For some you can use air nailers, others you can't, some of them only work with air nailers that have a second person working the trigger while one holds them, all the different air nailers need different compressors, some of those take different voltage, shit like that. Imagine it's like that for all their tools and that these differences manifest in all sorts of ways based on the combinations of materials & tools. We wouldn't say "gee why are house-builders so bad at building houses, and LOL they can never even tell us about how long it'll take", we'd say "holy shit how do any houses get built, it's practically a miracle, we should fix it so it's not so hard—for no good reason—to build houses"
- forinti 7y ago1) We hardly ever try (most projects aren't given adequate time to model and prototype) 2) There's not enough specialisation (most software shops will tackle any project and IT people tend to specialise in technologies, not business areas).
- chadcmulligan 7y agoThe Boeing Company invested nearly $10 billion in developing the new 777 The Voting software cost $60K I believe, that includes distribution. That about sums it up for me, if you want reliable software it costs a lot of money.
- alexbanks 7y agoMoney, time and planning. Agile is, for the most part, the absence of planning. "Figuring it out quickly and changing it if we need to." But, by design, most "physical" engineering tasks require tremendous planning, and include (from what I understand) very little "Just figure it out as we go." The reason for a lack of planning, is because tremendous planning increases time to ship, which effectively costs money.
- chadcmulligan 7y agoYes, planning, lots of code reviews, lots of testing. Building your software so it can be tested. Its all doable but no one wants to spend the money - and if its not critical its good enough. I've read with the space shuttle every line of code was reviewed in a meeting - its described here https://history.nasa.gov/computers/Ch4-5.html https://history.nasa.gov/computers/Ch4-5.html
- tootie 7y agoAgile is not the absence of planning. It's about adapting to change. When it comes to business software this makes sense because the end result is typically unknown. Aircraft avionics have a pretty well-defined end goal. The other big difference is really quality control. Most software doesn't invest heavily in quality because a failure isn't that costly. It's the same calculation that goes into producing absolutely everything. The cost of a quality failure in an airplane is humongous. I use apps that crash at least once a day, but I just restart them and keep going.
- alexbanks 7y agoYeah I guess I just very much do not agree with your stance on Agile, but that's okay. YMMV.
- ken 7y agoFashion. We're not bad at software engineering. We're bad at correctly labeling what is "software engineering" and what is not. "Software engineer" today is just a job title. It makes us sound cool, but it has about as much to do with engineering as "Scrum master" has to do with rugby. In lots of places, you don't need to have an engineering degree or be a certified engineer to claim the title. Teams that actually practice Software Engineering, like the famous Lockheed shuttle group, are as good at it as we are at any other branch of engineering. It's wildly misleading to use the same word for an app written by a few programmers in a couple of months (like the Iowa Caucus app) and the Space Shuttle control software (maintained by hundreds of people, with an average of 1 bug per release), and everything in between. It'd be like letting anyone call themselves Doctor.
- xnx 7y agoAgreed. An insult to real engineers. As misleading as calling programmers Software Doctors.
- wruza 7y agoWhat does SWE actually do? I mean, I have some ideas how e.g. building or bridge engineers work and how they plan their projects. Standards, blueprints, legal safety requirements, physics, calculations, approval, etc. But what is software engineering in short? Upd: is there AutoCAD for software?
- tracker1 7y agoMost software and for that matter, most software developers don't need that level of detail. It's the difference between building a nice doghouse and a skyscraper. The problem is too few know the difference, fewer still know how to hire properly, and many seem to think that one developer is interchangeable with any other. Of course tethering to education requirements doesn't mean much. I think a formal guild where you build your representative value by the endorsement and status of others, and if you fail, not only are you brought down, but those that endorsed you will lose cred as well. Setting up such a system would be difficult and take time, and I'm unsure if it would ever reach critical mass. Also, unlike doctors and other fields, I don't think you should have to be formally licensed to work in software. Most initial developers are, were, and continue to be cross trained from other fields.
- harry8 7y agoYou can't discuss software in this context without discussing IBM global services, oracle, computer associates, accenture etc etc. Shut them all down, watch the average quality of software improve dramatically, immediately. Next have someone qualified on every single board of directors and have each board create an appropriate sub committee. The same way you have a qualified accountant and audit sub-comittee. Have someone with proper CS & IT credentials and an IT oversight comittee. (Sure mostly the initial massive win is warding of the vampires mentioned in the previous paragraph but there is huge, huge value beyond that.) Having ignorant people making the resource allocation decision is idiotic in the extreme and leads to overpriced, rubbish quality outcomes. Like deciding to use some garbage vote countinga app that doesn't and can't work - who did that? Can we just say they are utterly ignorant of the field they made important decisions concerning or do we need to get their name and demonstrate it. Why are we so bad at software engineering? We are not! We just aren't. We do amazing things. We can do it reliably. We can do it economically. Software is f*&king awesome. Why is there so much corruption in the decision making process leading to garbage quality overpriced, risky and idiotic software? Now that is a better question to ask. Why is the idea of actually regulating foolhardy risk-taking startups (self-driving, privacy invading, turn-key facist state surveiling etc) so controversial? Because we can't even make good decisions about CRUD development at a policy level in a fortune 500 company - forget a policy decsion at a government level, you know it's going to be awful and redolent with regulatory capture. We just need to grow up and stop blaming the geeks for the utter manure shoveled at us by ignorant jocks on golf courses determined to exclude anyone with actual understanding, insight and knowledge. And the manure shoveled by the actual geeks with a massive risk appetite and zero care for externalities beyond their startup making cash. Really. That's it. That's all. Software is FINE. Decision making about software is SO bad, so awful, so hideous we try not to think about it lest it rots our minds with despair.
- jussij 7y ago> Decision making about software is SO bad, so awful, so hideous we try not to think about it lest it rots our minds with despair. And to add the icing to your cake, more often than not there are no consequences for those making these bad decisions.
- CM30 7y agoNot about the article specifically, but as far as the XKCD comic goes, I'm not sure it necessarily tells people what they think it does. The electronic voting system concept is arguably the only concept software engineers would universally say is a bad idea/worry about. And that's more because of the practicalities involved in that particular idea rather than something about software enginering as a whole. What's necessary for a secure and trustworthy voting system puts it at odds with any attempt to provide such via a machine/app/program/website. Ask the same people about say, reliable hashing/encryption libraries or what not, and their attitudes would probably mirror those of the aircraft designer or building engineer. There are probably also examples of things in aircraft design or construction that would have people in those fields freak out too.
- jiofih 7y agoWhy would that be? There are far more dangerous software jobs, and also examples of successful digital systems like in Brazil.
- pkaye 7y agoI'd say the complexity has increased, the requirements are not well defined and the schedules are tight.
- slifin 7y agohttps://www.microsoft.com/en-us/research/publication/the-influence-of-organizational-structure-on-software-quality-an-empirical-case-study/ https://www.microsoft.com/en-us/research/publication/the-inf... The biggest predictor of bugs is "Organizational Structure", the main problems sound like they're not in the computer(s)
- JackRabbitSlim 7y agoThe real world has a base set of stable frameworks on which everyone can rely, such as physics. Software must implement not only a thing but the entire universe in which that thing operates. Everyone claiming tooling or funding or this or that is missing the forest for the detail of trees in the client spec.
- feral 7y agoContarian opinion: We are great at software engineering, and our field is the best at engineering generally. Engineering isn't about how reliable or high quality the system is. Engineering is about balancing the costs and the benefits. It can be great engineering to make a running shoe that wears out after 2 races, if it wins marathons. People who think software engineering is bad, are actually bad engineers, who think engineering is all about quality or reliablity, rather than about optimizing tradeoffs. Software engineering is doing an amazing job at producing products that balance cost and benefit, which is why software is eating the world. Engineers from traditional disciplines would struggle here, because it's a lot easier to follow super expensive tried and true process, than to situationally make tradeoffs like we do.
- Avshalom 7y agofacebook did ~$70B in revenue with ~$24B in profit, which implies that it spent about ~$40B to keep itself running, for a year. The Big Dig cost ~20B over the course of a decade. The Apollo Program clocks in at ~25B The Large Hadron Collider at a svelte 10B. Software isn't cheap it's just that no one pays attention to the costs.
- feral 7y agoFacebook is an outlier monopoly, having successfully privatized a massive commons, so I'm not sure their ability to spend 40B a year proves much of anything. (If those figures are even the right lens.) As a counterpoint, Wikipedia's operating costs are ~40M a year, 1000 times less, and I know which one I'd rather keep!
- askafriend 7y ago> having successfully privatized a massive commons They created the commons. It didn't exist before and several companies tried to do what they did. They all failed. MySpace had a huge head start. Didn't matter. Everyone shit on the Instagram acquisition for $1B when it was first reported and years afterwards (in fact Zuck made the decision without even consulting the board and right before a risky IPO where the public was sure to take it as a negative signal). He saw the value and invested in it. Today Instagram is a $100B entity that does more revenue than YouTube. Credit where credit is due. That’s not to say there aren’t issues. There obviously are and they’re well documented.
- fallous 7y agoIf I rephrase the title to "Why are the results of software engineering so bad?" it makes it easier for me to point out the most obvious problems, in my experience at least. The alternative to nearly all software solutions is "bunch of people do that thing" or "hire costly expert." Software is usually a combination of transitory, relatively quick to implement, mostly opaque, and very inexpensive in up-front costs in comparison to the alternative, which both reduces the perceived risks as well as makes it unusually attractive as a means to achieve some goal. That combination also lowers the bar for what qualifies as "a goal," providing a much larger universe of possible actions available for those who are establishing the goals. With the lowered bar of what constitutes a goal, given that the overall costs are perceived to be so very low, the decision maker feels unburdened enough to choose goals without vetting the decision and its consequences against the standards that would be applied to "hire a bunch of people to do that." You've taken what used to be a decision that carried with it all the forethought and examination that one would usually apply to purchasing an automobile or home and replaced it with a decision that has no more consequential cost than to decide whether one wants fries or carrot sticks with a sandwich. As with the choice of fries, it's not the single instance of such a choice that lays you out on a cardiac surgeon's table but instead the repeated accumulation of what seemed to be inconsequential decisions to get fries. If you asked someone if eating fries with every meal could set someone up for a heart attack they'd most likely say "of course, that's obvious." But our patient did not encounter the situation in which they had to make the decision as to what side they will have with every forthcoming meal, and all the forethought answering such a question would entail. They only made one little decision whose importance was as fleeting as a single meal. Until it wasn't. This effect on decision-making, with regards to software, almost always spreads to the entire organization (and often beyond, to infect customers and the general public as well). The CEO, the VPs, the Directors, the Managers, not to mention the programmers themselves, all make decisions and set goals that meet the lowered standard (or at least a standard lower than what should or used to be the standard). When you lower the standards for decisions and goals, you get results commensurate with those standards.
- tracker1 7y agoThere are a few issues... First, the people writing the checks aren't concerned about the material quality or the craft discipline output. It's also not so different from manufacturing... you can have a hand crafted oak cabinet with dovetail joins and meticulous material selection, or you can have a flat pack cabinet from Ikea. Both have value, and quality is considered a measure of value that meets or exceeds expectations. Building an aircraft has many layers of bureaucracy behind it, and the cost that goes with it. In the end, software is practiced as a craft more than an engineering discipline. And that's okay. It's usually when politics and management decisions override the needs of the software/product that things tend to go sideways. There are also more than a handful of software developers that don't really care about the quality or maintainability of the software. Let alone learning and using the methods for interfacing with said software. Just the past couple days, I was looking for a React + Material UI template to work from. Many looked great, but actually following the code was a byzantine mess. Mirrored trees of files are my biggest pet peeve in front end projects. Let alone not even using the methods available for use and extension. That's just a recent example. I've seen others, where a given set of methods is copy/pasted across dozens of case statements... Worse still is when you see a schema design that makes no sense and/or variables that are lost and meaningless, that everything around it loses all context. Such as the passwords having the variable w23 and the value is stored in the "Phone2" table under "extra1" columns. Managers give lip service to "quality" and "testing" but when push comes to shove you skip testing to ship on time, and have to deal with bugs several years into an initial 9-month project timeline.
- keithnz 7y agoWe aren't bad at software engineering. The Author does a good job of analyzing the situation. It highlights mostly what we care about is delivering a stream of value knowing that we can correct things when they go wrong. We care that it is mostly right. We 100% embrace the "soft" of software Thing we struggle more with is "Must work correctly on first REAL use". So we now have the PITA world of other engineering disciplines where adapting is often not an option once "deployed", though even there those disciplines look for ways to get "soft". Having spent a lot of my career doing Embedded Systems/Industrial Control Systems the approach to getting things correct is very different from developing web/backend/mobile software. Lots of rules are introduced, design approaches are limited to certain ways of doing things and many techniques are avoided. Functionality is carefully considered on how difficult it is to build correctly. Testing is more convoluted. Robustness and Performance are far more pressing concerns. But again, in this environment it is often desired to be more "soft" and various things are done to try and achieve that. It can be handled much like other engineering and often is managed as part of a multi disciplinary effort of mechanical/electronic/software engineering and treated as a "system" Getting some mobile app developers to make something that is supposed to be "robust" on first deployment is mainly a problem in not recognizing what skills and experience are needed to be employed to get what you want.
- OrgNet 7y ago> We aren't bad at software engineering. I have never seen perfect software, have you? They always end up with bugs that make you vulnerable...
- keithnz 7y agoI'm not sure I've ever seen anything engineered that is perfect, have you? what even is "perfect"? seems like an unrealistic standard and not the goal at all of any engineered system (civil, mechanical, electronic), I don't think that a good definition of "bad" is everything less than "perfect". I have seen software the fulfills the necessary criteria, especially in the world of control of machines, eg, engine control, industrial control systems, etc. Many things get built that work within their "engineering" criteria. I have one particular software application on a microcontroller that performs various functions and control, I've only ever deployed 1 version on thousands and thousands of devices, it has worked for a decade so far. It went through rigorous review and testing before being released.
- blackflame 7y agoBecause there are a lot of bad actors with plenty of time on their hands and resources to backup their endeavors.
- bookAlot 7y agoIt's that face. Is why.
- thaumaturgy 7y agoI appreciate posts like this one for the commentary they generate, but it's still disheartening to see the obvious (to me, anyway) stuff getting missed each time. The overall post was okay, but the lead-in was too topical to be relevant more than a few months from now, and also wasn't really about software quality at all. What happened in Iowa was a lot of bureaucratic cock-up -- they got the wrong people (because favors or political or personal connections) to do entirely the wrong thing, and didn't bother to consult any of the people who could have helped them make better decisions. It's not substantially different from someone buying the shittiest available used car from a private party and the wheels falling off on the highway, and then trying to use that as an indictment of automotive build quality. But. Clearly software suffers from far more issues than other technical disciplines, and that is 100% because there are no common standards and, thus, no certification process or professional licensing. When software developers and managers compare big software projects to big civil engineering projects, they keep missing the obvious educational and certification process required to become a civil engineer. Galloping Gerties and John Hancock Towers still happen occasionally, but then they become case studies for every prospective new engineer. Contrast this to software, where we all slang out code until we're bored and then self-educate by reading other people's war stories online. The average man or woman that can build a porch for your house is subject to more licensing requirements than the developer that builds voting software. Let that sink in for a minute. Programmers are quick to screech at the thought of being subjected to any kind of licensing or certification process, and yet we all have the horror stories of being forced to build and deploy utter garbage by upper management. Professional licensing would really help us here. We'd have a defense that would go, "I can't do that, it would make my license get reviewed." I don't think this will ever happen though. The majority of programmers don't want it and nobody knows how to do it. They'd rather write and share navel-gazing articles from time to time, wondering about what could possibly be so very different in software from every other engineering discipline. 'Tis a mystery.
- kthakore 7y ago100% percent. Software that will be used in a mission critical way should require specialists and certifications. I wonder what your thoughts are on an apprenticeship program that includes course work and practicals in organizations?
- worik 7y ago"Software engineers" are not. Engineers. "Software engineering" is not. Engineering. Delusions of grandeur is the problem.
- grumple 7y agoThe app used for the caucus was built for $60k. That's enough to pay what, 3 developers for 2 months? Not much time for testing. I don't know how complex the app is, but that's doing things on the cheap and they paid the price in the end.
- DantesKite 7y agoOne of the more profound insights from Stephen Wolfram’s “A New Kind of Science” is that small rules can lead to extraordinary complexity. Wolfram famously gives Rule 30 as an example, where you cannot know what each line of squares will look like before you do the computation, but he goes on to cover many other phenomena, like prime numbers and tag systems.[1] One conclusion is that complexity stemming from simple rules is relatively common in our Universe and that historically, humans have done a good job of solving the narrow pool of problems where you can know the end solution with a simple calculation (say predicting the location of a ball as you toss it up in the air). The implication is that there’s a whole “universe” of problems where we cannot know the end solution until we’ve done the work necessary to compute it. And in that sense, it wouldn’t be surprising if software engineering was a bit like Rule 30: an endless array of patterns we can’t predict until we’ve actually created the code or computed what it can do. It’s not so much that we’re bad at software engineering. It’s just that emergent complexity is part of our reality (assuming Stephen Wolfram’s insights apply to software engineering. Maybe they don’t. But it sure feels like it). I think the ancients knew this well. The Tower of Babel story is pretty old. Details the problems humans run into when they try to scale and work with many different elements: Something nobody could predict and possibly, catastrophe. [1]http://mathworld.wolfram.com/TagSystem.html http://mathworld.wolfram.com/TagSystem.html
- cs101 7y agoWould Conway's Game of Life be a good example of small rules that lead to complexity?
- gaogao 7y agoBoth Game of Life and Rule 30 are cellular automata so yes!
- kragen 7y agoWolfram likes to take credit for other people's ideas, but I don't think even he would claim that the idea that “small rules can lead to extraordinary complexity” was original to him. For example, what he calls a “tag system” is often called a “Post tag system” because of Emil Post’s pioneering work investigating it in the 1920s through the 1940s. http://bactra.org/weblog/915.html http://bactra.org/weblog/915.html
- darkerside 7y agoOur society has produced software teams that produce highly reliable software (space shuttle, banking technology, and embedded systems) that don't leave room for a great deal of speed it innovation. Let's call them Type 1 teams. We've also produced "move fast and break stuff" software organizations, who have realized moving fast and failing is a better financial outcome than safely arriving at a suboptimal destination (Facebook, Twitter, tons of startups). Let's call them Type 2 teams. Neither Type 1 nor Type 2 teams are Bad or Evil. They are simply suited to different applications. What happened here is, an organization that was unable to distinguish between these types of teams hired a Type 2 team for a Type 1 job. Generalized example, usual caveats apply.
- ravoori 7y agoThe majority of software teams fall outside of this classification.
- darkerside 7y agoAgreed. It's really more of a gradient. Regardless, the problem is not where a team lies on the gradient, but where a team lies in relation to the fundamental needs of the problem to be solved.
- 29athrowaway 7y agoBecause people can be irrational and dogmatic, and follow incoherent people for no reason.
- EastSmith 7y agoAsk any locksmith about any door security. "I am not putting my breakfast behind a locked door, he will say. I always carry it with my backpack and my backpack is always on my back."
- bufordtwain 7y agoThat cartoon points out that airplane engineers create good, reliable things, and software engineers don't. But airplanes are reliable in part because of the software that they run. So to me the question boils down to "How come we create good software in one case and terrible software in another?". Well, if you give a programmer incorrect/incomplete requirements, not enough time, don't do enough testing, and generally cut corners, the software is probably not going to work very well. And while it's true that some programmers are better than others, poor quality work should never make it past the testing phase.
- asdfasgasdgasdg 7y agoThose aren't the only reasons. Some more: 1. Software is easy to fix. Compared to other construction disciplines, software is the cheapest to fix. 2. The consequences of failure are typically minimal. Most software is not mission critical. Failure means minor inconvenience for a lot of people. Moreover, since your competitors are no more reliable than you are, you don't even stand to lose customers by having an occasional failure. (This is the one the article discusses.) 3. Software has more degrees of freedom. Unlike physical building disciplines where the types of materials are limited and generally well known, and where the number of physical dimensions is at most three, software takes place in an extremely complex and multidimensional operation space. Moreover, we have no evolved intuition about how things behave in that space. 4. Comparatively minor errors result in comparatively major failures. If you forget one rivet on a building, the engineering tolerances will make it such that the building will not fail as a result. But it is not really possible to make a server resilient to null pointer exceptions. It either works or it doesn't. Software fails partially much less often than physical things.
- 3PS 7y agoOne of my favorite quotes from my old data structures professor in college was this: "software is non-linear." If you're laying down the bricks for a house, there really aren't any cheap tricks or shortcuts. Building two houses takes twice as many bricks as building a single house, and so on. We could say that brick usage scales linearly with house construction. This is a bit of a bummer for bricklaying enthusiasts, but on the other hand, a single brick out of place is probably not going to bring your roof crashing down. Software is different. Often, the distinction between processing 100 files and 1,000 files is minimal at best. This ability to scale effortlessly is often the best thing about software, but the same non-linearity is also the price we pay for power. A single subtle programming error can cause millions of dollars' worth of damage and bring massive systems to a grinding halt. Overall, I think this is what makes software interesting and exciting to work with, but I can understand how it can pose a steep challenge once things like reliability and security become major concerns. The way I see it, much of research and development into better programming languages and tools has been to see how we can systematically mitigate these kinds of propagating errors and make our systems more robust to mistakes.
- ocschwar 7y agoAre we? I mean, we're constantly driving every software organization to take on more and more complexity in their projects all the way to the point that they reach their cognitive limits. Yes, a lot of the progress we've made is just an illusion driven by Moore's law and lots of bloatware that it enabled, but a lot of it is genuine and needs to be taken into account.
- kmstout 7y agoThis discussion reminds me of a talk given by Glenn Vanderburg (https://www.youtube.com/watch?v=RhdlBHHimeM https://www.youtube.com/watch?v=RhdlBHHimeM), wherein he explores the question of whether "software engineering" is or can really be engineering. Around the 27 minute mark, he quotes Billy Vaughn Koen, a nuclear engineer, as follows: "The Engineering Method is the use of heuristics to cause the best change in a poorly understood or uncertain situation within the available resources." That's hardly the end of the debate, and I'm still undecided, but it seemed worth lobbing in before hitting the rack.
- asciimike 7y agoSeveral more humorous articles on the subject: 1. https://www.stilldrinking.org/programming-sucks https://www.stilldrinking.org/programming-sucks 2. https://mickens.seas.harvard.edu/wisdom-james-mickens https://mickens.seas.harvard.edu/wisdom-james-mickens (I love The Slow Winter, but To Wash it All Away is probably more relevant here)
- im_down_w_otp 7y ago1. The economic incentives are aligned to ensure most software isn't very good because it doesn't "need" to be. 2. The tools that help make software really, really good are really, really baroque and remain that way because the people who invent them are subtly incentivized to be the high-priest of an esoteric technology church rather than making them for the masses. Which ensures that making really, really good software doesn't get cheaper with time and also ensures that you'll only reach for these tools if _you absolutely have to_ because of #1. 3. Software Programmers/Engineers see their jobs, and appear to derive most of their joy, from doing the actual coding. Not in using rigorous design tools ahead of time which are unmoored from their implementation, nor in doing the testing & verification of the implementation after the fact. 3a. Software Designers/Architects have made a bad name for themselves by spending more time pontificating at whiteboards than writing down verifiable specs & models. 3b. Software Testers/QA folks are treated as lower-class than Programmers/Engineers, and don't get paid nearly well enough, so they're setup to follow rote scripts and procedures rather than empowered to deploy sophisticated testing methods like property-based testing or mutation testing. 4. All those factors appear to have created a feedback loop which has become self-reinforcing.
- nec4b 7y agoAirplanes and elevators both use software. It is obvious that software engineering can be as reliable as any other engineering discipline. World is full of imperfect physical pieces of engineering from roads to night cabinets, therefore it really is a silly position to take, that software is somehow worse than anything else.
- crimsonalucard 7y agoHow do these articles exist without mentioning formal methods? You realize there exists systems and techniques that can prove your program to be 100 percent correct? Whatever the pitfalls articles about code quality and the quality of software in general are pure ignorance if this aspect of software isn't mentioned.
- justlexi93 7y agoWe're "bad at software engineering" because we're bad at whole-systems design, and we're bad at whole-systems design because the market does not incentivize it.
- fctorial 7y agoObligatory xkcd: https://xkcd.com/2030/ https://xkcd.com/2030/
- fctorial 7y agoWow!
- deanCommie 7y agoI'm confused why this is even a puzzle. There is a bubble. Companies with half a product, no distinguishing technology, and no path to profitability are getting valuations of billions. Therefore the big guys - the FANGS - become worth trillions, and can afford to hire the best of the best and pay them millions (over the last 5 years, with stock, yeah, that's what sr engineers make in Seattle/Silicon valley) So, you've got the best software engineers in the world making adtech. Which means the only ones the Iowa Democrats can find for a 60k budget aren't inept, but they're certainly not in the top tier. See also: The Obamacare online rollout. What will fix it? A market correction. One, as a well paid sr engineer, I am not looking forward to. But it will make a bunch of actually competent software devs available for smaller market projects, and suddenly the quality of government software will increase dramatically as lower-paid-but-outstanding-benefits government jobs seem way more cushier all of a sudden.
- vlovich123 7y agoAll this shit applies at the FANGS too so I don't think any market correction will magically solve the problem.
- JDiculous 7y agoBecause it's not actually taught anywhere. There are no widely adopted standards. Web development is literally a patchwork of random libraries and npm modules stitched together. Computer science programs don't teach students how to build good software, they teach computer science. CS professors wouldn't even be qualified to teach good software engineering practices if they had to. Code is also difficult. It's one thing writing your own code and understanding it, but understanding someone else's code is very difficult since you have no idea what was going on in their head when they wrote it. Of course there are practices you can follow to make things simpler, but it's never going to be as easy as say reading plain English.
- grecy 7y ago> Because it's not actually taught anywhere Oh, I don't know. I have a bachelor of Software Engineering that is accredited by the Australian Institute of Engineers. The vast majority of my degree was on the discipline of SE, so rigorous testing standards, theory of large scale system design, hard real time systems, Improving your personal software process. For our final year project 16 of us worked for a very large company to design and build them a piece of software. It was awesome.
- commandlinefan 7y ago> Because it's not actually taught anywhere. Hell, even here on HN not having had any formal education of any kind is seen as some sort of badge of honor.
- watwut 7y agoBecause we dont know how to manage software projects at all. The technology is not a problem, we dont need new credentials for CS&IT people. Organization and management is and we need better education about that for everybody - especially for CS&IT people.
- maehwasu 7y agoNow ask the airplane engineers about the F-35. Voting apps are basically political money laundering schemes. Using them to make comments about software vs other industries suggests either stupidity, laziness, or malice.
- nonseobeliever 7y agoI think that people capable of writing software are more intelligent and more perfectionist. It's not that software is really bad, but people writing it have very high expectations from themselves. They want to improve more and more, get to some perfection level and mastery that few other disciplines expect. See 'not invented here' syndrome.
- scoutt 7y ago> Why are we so bad at software engineering? "Why are we so bad at apps and websites software engineering?" might be a more appropriated title. My hard drives never stopped spinning. I am sure there is some amount of software engineering on them. Last night I finally finished The Witcher 3. It never hanged up and was a joy to see and play. Please, when referring to software engineering, stop assuming is just shitty phone apps and rushed webapps. That's just a small tiny fraction.
- wiz21c 7y agoObligatory post : http://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036.html http://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036... (Dijkstra on software engineering)
- Juliate 7y agoBecause this is a baby industry/technology, compared to other engineering practices?
- LandR 7y agoBut we have established engineering industries best practices to learn from, but it seems like we aren't.
- Juliate 7y agoLike, building bridges? (even there, we still struggle with, not technological issues, but budgeting/governance/contracting/management). How many generations of people have passed since computers are around? Not enough that we can pragmatically reflect upon it. See, we can say we collectively have some understanding of what the invention of the printing press, and its consequences on societies, cultures, and history. As well as, before it, writing. I think we still can't say much the same about computers. We barely see (and not everyone yet) how much it impacted and enabled to impact our societies, public & private discourse, political endeavours and regimes.
- jonathanstrange 7y agoThere is one major difference between the disciplines. Engineers are legally responsible for their creation and sign with their names. Software 'engineers' do not do that, if something goes wrong nobody feels responsible and usually nobody has signed some document that testifies legal responsibility.
- eordano 7y agoI use to explain it this way: nowadays, bits and bytes are everywhere, most everybody you know has a notion of what a `megabyte` is. But this is a shockingly recent idea. My grandma was 20 when a guy named Claude Shannon in 1949 invented/popularized the concept of a "bit" and described what information is, the way Newton described matter and how to model physics with mathematics. Really, "information" was a just vague concept until Shannon and this was just 70 years ago!!1 It's only natural that a lack of generations of craftsmanship in this industry makes it pretty low quality/hard to master. On the other hand, imagination is the limiting reagent, since (arguably) the bottleneck is good ideas, specially with all these decades of Moore's law.
- jacquesm 7y agoMissing here and in the comments so far: because we categorically refuse to learn lessons from the past and to improve on what is already there, instead we keep on re-inventing the wheel in interesting and novel ways which then come with their own sets of problems which usually only show up after a couple of years. By then of course it is too late. This has been going on as long as I've been active with computers. I think a part of the driving force behind this was the speed with which computers became faster. There simply wasn't time enough to absorb the lessons before the 'old' stuff looked small and obsolete in view of our new powers. But if you look at old and mature software systems (Common LISP, Erlang, D and others of that vintage) you'll find that the degree of thought that went into them and making them bullet-proof is still very much absent of that which drives a large portion of the software industry today. We're probably destined to go through this sort of cycle at least a couple of more times, if not forever.
- sjwright 7y agoI think there's one true fundamental reason: software is a lot more difficult than we assume. We underestimate the degree to which even the most mundane program is the task of creating an entire universe and ecosystem from scraps. Even the most helpful programming languages and libraries don't get you as much as you think. Just look at the world software engineers play in. In a world of 7 billion people, nearly all of us use one of a tiny number of compilers on computers running one of just three or four kernels, atop one of two processor instruction sets. Yet look at the plethora of programming languages. The fundamental building blocks of our industry are apparently so terrible that many of our brethren devote years trying to replace them.
- lincpa 7y ago[The Pure Function Pipeline Data Flow v3.0 with Warehouse/Workshop Model](https://github.com/linpengcheng/PurefunctionPipelineDataflow https://github.com/linpengcheng/PurefunctionPipelineDataflow) The idea of simplicity and unity is an important guiding ideology of scientific research. It can be found from the knowledge of various disciplines: the more universally applicable a unified theory, the simpler it is, and the more basic it is, the greater it is. [The Pure Function Pipeline Data Flow v3.0 with Warehouse/Workshop Model] systematically simulates integrated circuit systems and large industrial production lines. It perfectly achieves simplicity and unity. It must be the ultimate programming methodology. In the computer field, for the first time, it was realized that the unification of hardware engineering and software engineering on the logical model. It has been extended from `Lisp language-level code and data unification` to `system engineering-level software and hardware unification`. It brings large industrial production theory and methods to software engineering. It incorporates IT industry into modern standardized large industrial production systems, This is an epoch-making innovative theory and method. 1. The replaceability, insertability, observability, and readability of the pipeline are very strong. 2. The observability, standard, fairness of the dataflow are very strong. Data standards (data interfaces, data specifications) are better than code interfaces. and non-IT practitioners can understand. 3. The warehouse/workshop model is widely adaptable, simple, and reliable, and the workshops are isolated from each other. There are only five basic components: 1. Pipeline (pure function) 2. Branch 3. Reflow (feedback, whirlpool, recursion) 4. Shunt (concurrent, parallel) 5. Confluence.
- wewake 7y agoFood for thought: Should we establish a system that gives people license to code? Doctors need to get a license too because their practice involves human lives at stake. I don't see how software doesn't put human lives at stake. Honestly, the number of lives at stake is increasing with each new self-driving car hitting the road.
- commandlinefan 7y agoI’m continually shocked that there’s still no “bar exam” for programmers. It wouldn’t even need to be something that you need in order to write a program, just some actual meaningful certification that hiring authorities could put some credibility behind.
- vparikh 7y agoSoftware as a wide spread phenomenon has been around since what late 1970s (I am talking about business and individuals using it). Compare it to building industry, accounting, law and any of the hard sciences. They have been around for thousands of years. It is kind of crazy that we insist on perfection withe less than 50 years of practice. Heck we can't even decide on one language yet - and the one that are standard (I am talking about you JavaScript) - people keep re-inventing them (Coffee Script, TypeScript, etc.)!!!
- dave_j 7y agoTypically Time and Consequences of Failure: 1) People typically die when things go wrong and are heavily regulated. Most software that works in this space are tested in accordance to those industry standards. Your desktop browser doesn't need to be engineered to those standards. 2) Other engineering disciplines have in certain cases had 100s if not 1000s of years progress. We've had less than 60 years.