11 ms·
The Software Crisis
- Animats 2y agoThe ending: "Things can be better. I'll show you how." It's just an intro for clickbait.
- throwup238 2y agoIt's the first (and only) blog post on that site: https://wryl.tech/log/index.html https://wryl.tech/log/index.html
- darioush 2y agoIf only they had unveiled the single unifying abstraction of everything :(
- unstruktured 2y agoOh that's a solved problem since 1969. It's called "unix". Everything is a file which can be processed as a byte stream. Composition is a breeze- can't be any more general than that! (I kid, mostly :)).
- bitwize 2y agoThat's the worse-is-better grand unified abstraction. The Right Thing, as any Lisp programmer can tell you, is lambda.
- glompers 2y agoRichard Gabriel: https://www.dreamsongs.com/WorseIsBetter.html https://www.dreamsongs.com/WorseIsBetter.html (1991) https://www.dreamsongs.com/WIB.html https://www.dreamsongs.com/WIB.html (2000?)
- kazinator 2y agoAn actual Lisp programmer will tell you that the right thing depends on the situation. The right thing can be a lambda, a string, a symbol, a structure, a class object, a hash table, a vector, a list, a call to a foreign function, a syntactic abstraction, a bitmask, a load-time value, a pattern matcher, ...
- Animats 2y ago- UNIX: everything is a file. - LISP: everything is a lambda. - Tandem: everything is a database. - QNX: everything is a message. - IBM System/38: everything is a capability.
- aleph_minus_one 2y ago> If only they had unveiled the single unifying abstraction of everything :( Here you are: https://en.wikipedia.org/wiki/Category_theory https://en.wikipedia.org/wiki/Category_theory ;-)
- dimitrios1 2y agoThe prime criteria for being clickbait is if it is sensationalized, deceptive, or intentionally misleading. This strikes me as none of those things. It's the last sentence of a blog post.
- Animats 2y agoIt's something where you have to read the introductory material, and then find out the important part is elsewhere. In this case, in a blog post yet to come.
- redleggedfrog 2y agoAd Hominem? Or are you just stating that as a fact and not questioning the veracity of the arguement?
- Swizec 2y agoThe “inscrutable layers unapproachable to beginners” of today are the bare metal low level computing of tomorrow. Sure I learned with DOS and Turbo Pascal and it was wonderful, but if you ask my teachers who learned with machine code and microcontrollers, they worried that computers have become too abstract and kids these days have little chance to learn the true details.
- EternalFury 2y agoIf it's done right, by documenting a mature interface and its inputs/outputs, no one needs to know what atoms make up the slice of bread that gets buttered.
- doug_durham 2y agoIsn't that exactly what the author is complaining about? There is too much complexity to understand all of the layers no matter how well documented.
- ChrisMarshallNY 2y ago> It's catastrophic when they don't." I have found this not to be the case. Very often, an inaccurate mental model is the ideal user state, and it's my job to afford and reinforce it. But that's just me, and my experience. I'm sure there's a ton of folks that have found better ways.
- omnicognate 2y agoPersonally I can't bear software that contorts itself to conform to an incorrect mental model. I find it alien and unusable. I don't want the inaccurate mental model and cannot force myself to accept it, but the contortions and don't-look-behind-the-curtain prevent me from forming an accurate one. That doesn't mean I don't want abstractions. It means I think what constitutes a good abstraction is determined as much by how true it is as by how intuitively appealing it is. An abstraction that corresponds to a naive user's expectations but that doesn't accurately reflect (the essential/relevant aspects of) what is actually happening is not an abstraction, it's a lie. Edit: And the tragedy of it is that users are, by and large, extremely good at figuring out the reality behind the lies that well meaning developers make their software tell. When our software breaks and misbehaves, its internal realities are surfaced and users have to navigate them, and more often than not they do, successfully. Internet forums are full of people reasoning, experimenting and fiddling their way to success with faulty lying software. Apple Community is perhaps the purest example of a huge population of users navigating the broken terrain behind the abstractions they weren't supposed to think about, with absolutely no help whatsoever from the company that built them. We should have more respect for users. If they were as dumb as developers assume they are almost none of the software we write would ever be successfully used.
- ChrisMarshallNY 2y ago> We should have more respect for users Agreed. In my case, I write software for a lot of really non-technical users, and have found great utility in reinforcing inaccurate, but useful, user narratives. So "respect" doesn't just mean assuming users are smart. It's also making house calls. Meet them where they live, and do a really, really good job of it, even if I think it's silly.
- neilv 2y ago> It seems as if this state of comfort is due to a sense of defeat and acceptance, rather than of a true, genuine comfort. A whole lot of, say, Bay Area software developer salaries/compensation have genuine comfort. Defeat and acceptance doesn't come into this, for most organizations: they face little-to-no accountability for security problems or other system defects, so... comfort for the developers.
- kmoser 2y agoAbstractions themselves aren't a problem; they are in fact a necessity if you want to move anywhere beyond simple bit-twiddling. (Heck, even the idea of software itself is an abstraction over hard-wired instructions.) The real problem with abstractions is when they are implemented poorly, or have side-effects, or just plain bugs. In other words, we will always be at the mercy of human-produced software.
- ramesh31 2y ago>The real problem with abstractions is when they are implemented poorly, or have side-effects, or just plain bugs. Which is always, and is why clean maintainable code uses minimal abstractions to accomplish the task. However it seems the default these days has become "pile it on".
- threatofrain 2y agoThe problem isn't minimal abstraction but imperfect abstraction. Imperfect abstractions convince people to dig underneath the surface. Now you've lost the benefit of abstraction because they're thinking of two layers at once. So when people run explain on their SQL query, IMO you've broken the declarative abstraction.
- kmoser 2y agoAsking the SQL engine to explain the query doesn't mean the abstraction is broken or imperfect. It simply means the developer wants to understand how their query is being understood and, hopefully, optimized. This is essential when debugging why queries don't behave optimally, e.g. failure to use an index. Even with the perfect abstraction, people will need to dig beneath the surface. This is because every layer of code is subject to side-effects due to its actual implementation. That's why we have, e.g., multiple sorting algorithms, and documentation for their individual behavior, speed, etc.: so developers can understand the limits and idiosyncrasies of each and pick the correct one for the job. We may make incremental steps towards more bug-free code, but because everything is limited by the details of its actual implementation (whether real or an abstraction), there is no magic bullet that will make a huge leap forward in the realm of software development as a whole.
- UweSchmidt 2y agoIf you look at the resumes of engineering or automotive company leadership, you'll see people going through stages of ever expanding responsibilities of part, component and product design, or management of production facilities of increasing size and importance. The CEO will still emphasize their technical knowledge, non-technical staff will at least try and fake it. In agile software development on the other hand, technical competence usually ends at the lowest tier. A scrum team has folks on it who make software, that's it. Then, lots of scrum masters, business analysts have probably never coded much; the first actual boss in the hierarchy has mostly secretarial and managerial work and will hardly look at code at all. Point is, it's not just that software development is done in ticket-sized portions which does not invite philosophical considerations about the numbers of abstraction layers that one builds and maintains. It's that software developers don't even have a seat at the table(); they get babysat by scrum masters, make compromises during code review, are discouraged from thinking beyond the ticket, and are then of course not usually promoted into leadership roles to which they would bring their technical competence. It appears therefore that any movements to bring awareness to the "software crisis" will be relegated to hobbyists, as the article states at the end: to "Handmade, Permacomputing, and various retro-computing circles". () I partly blame Hollywood and their incessant humiliation of software/IT people, while creating endless leading roles for doctors and lawyers, effortlessly weaving their complicated terminologies into fascinating storylines, which is aparently not possible to do for us? Maybe the scriptwriting AIs can come up with something here soon.
- steveBK123 2y agoI could buy this argument. Had I been a junior during the agile era, I'm not sure I would have developed as fast or as far as I have. The most agile pilled company I worked for just treated juniors & seniors as interchangeable cogs, except seniors should be able to clear more points per sprint. Active discouragement from thinking outside the scope of your ticket, keep your head down and mouth shut.
- heurist 2y agoWhen I was starting out a bit more than a decade ago, I was on an agile/scrum software team in a hardware company. The team was fine but I found the process painful. I ejected as soon as a new director realized he could do algebra with the story points and began plotting stories quarters out. I've never been on a scrum team since and am happier for it. As a manager now, I would push back on scrum in almost every situation (and have).
- wryl 2y agoHi! Author here. I think it's important to address certain aspects of this post that people tend to misunderstand, so I'll just list them here to save myself the effort. * I do not argue against abstractions, but against the unrestricted application of them. * I do not advocate for a reversion to more constrained platforms as a solution. * I do not advocate for users becoming "more technical" in a "suck it up" fashion. The key to understanding the software crisis is the curves of "mastery of a platform" and "growth/release cycles". We have, in the past 40+ years, seen these curves diverge in all but a few sectors. We did not address the crisis when these curves were close in proximity, but the second best time is now. As for folks calling this clickbait, it is the first in my log, and reflects my thoughts on the situation we find ourselves in as developers. The sentiments are mirrored, in various forms, around multiple communities, some of them based in counterculture. I do want to deliver some part of the solution to these problems, so I do intend on following up on "I'll show you how". I am a single entity, so give me time and grace.
- morning-coffee 2y agoIt's hard to get past the hubris wrapped up in the statement "I'll show you how"... as if the tens of thousands of bright engineer's whose shoulders you stand on were incapable and you're the savior... maybe you are! (But just adding the word "try" in that sentence would reduce the perceived arrogance by orders of magnitude.)
- wryl 2y agoWell, that certainly wasn't my intention, but in an environment of "I have a silver bullet and it'll cost you $X", I can understand the sentiment. At the same time, I do want to show that I have confidence in my ideas. Hubris and confidence must be applied in equal parts.
- croemer 2y agoHubris and confidence are two sides of the same coin. Did you maybe mean to say that one should balance hubris with humility to avoid coming across as arrogant?
- GiorgioG 2y agoMany abstractions do not hold over time. That is the basic problem I have with OOP.
- pmarreck 2y agoThe large majority of the work code does can probably be boiled down to a series of transformations done by a hierarchy of pure functions with a fixed number of inputs/dependencies, all of which are easily testable in isolation. It's unconstrained side effects and dependencies, resulting in an increase in complexity, that seem to cause the major issues and have to be managed. The real problem, of course, is the human capacity to comprehend (or not) the entirety of the system or subsystem by modeling it correctly in the brain.
- doug_durham 2y agoI reject this thesis totally. It has never been easier to get things done with software. The APIs provided on many different platforms allow useful applications to be developed by a larger number of people than ever before. I started my career in the era is 8 bit microcomputers. Yes it was great to know the entire stack from processor up through the GUI. But I would never want to go back to those days. Development was too slow and too limited. We are in a golden era of software development.
- psychoslave 2y ago> Very rarely do these models reflect reality. > It's a nice coincidence when they do. > It's catastrophic when they don't. Well, generally, it’s not my experience. Most software out there is not critical. Many bloated crappy webapp might end up badly doing what user is expecting while sucking irrelevantly large amount of resources all day through with erratic bugs showing here and there, yes all true. But this is not as critical as the software that handle your pacemaker or your space rocket. Most software can afford to be crap because most projects are related to human whims for which a lake of quality is at worst a bit of frustration that will not cause a feeling of devastation or pure death penalty. All the more, I guess that most software developers out there are neither working on Sillicon-Valley-like money motivation, nor paying their bill with the kind of software project they love to build on passion. So this means most software that hits market are generated through exogenous miserable remunerations. Who will expect anything else than crap to be the output of such a process?
- wryl 2y agoWhile I sympathize that the stakes don't appear to match up, I am talking about all software, and also taking into account the fact that these frustrations are numerous. It'd be one thing if it was taken in small pieces, small cracks in the stairs, but half of them are missing on average. I really don't like missing stairs. We're very removed from the usage of our software, and experience it in short-form (hopefully) actionable signals that we use to inform our development process. We don't get to appreciate the real pain in this "death by a thousand cuts" unless we can somehow switch bodies with a new user. I see programming as a trade, however, and we do have the power to govern the quality of our software. There are, however, incentives, financial or not, that can get us to look the other way.
- stackskipton 2y agoI don't think most programmers are removed of usage of software. I have to use Google Workspace daily and I'm not sure how Workspace team doesn't have entire GooglePlex hunting for their head. Likewise, I'm shocked that Microsoft Teams is not secluded for their own protection. I've got a laundry list for Azure Team and most of Microsoft employees I know have same list yet it remains so some outside force is driving this. However, I think it's clear why it's this. Business team wants cheaper developers and hope is that if you put enough abstractions out, they can turn over Development to AI or monkeys with typewriters trying to create great works of Shakespeare. I remember reading Log4J exploit and wondered which Log4J developer thought it was a great idea to allow "feature" they added in the first place. Probably someone trying to prevent the monkey from destroying the typewriter. However, it's excellent article and I await the next installment.
- wvenable 2y agoThis article presupposes that this software crisis actually exists or is a significant problem. The crisis is all this these things: Projects running over-budget Projects running over-time Software was very inefficient Software was of low quality Software often did not meet requirements Projects were unmanageable and code difficult to maintain Software was never delivered Now take the word "software" out and how many human endeavours have one or all of these things? And then how much software is actually pretty great? We tend only see the failures and the flaws and success is just a baseline that we completely ignore even as it gets continuously better. When we press the power button on our computer and it gets to a desktop, our computer has already run through hundreds of abstractions. Just at that desktop it is already the most complicated machine we have or will interact with all day. This happens billions of times a day, all across the world, and mostly flawlessly. And that's just one tiny example.
- jdbernard 2y agoThe thing that is unique about software is the lack of physical constraints which serve as a natural forcing function or filter on quality. With a bridge, for example, at some level it must meet a minimum bar of structural integrity, quality of materials, etc. or it will fall over from its own weight. As a cook, there is a bare minimum I have to hit with the quality of my ingredients and skill of preparation in order for the food to be palatable and edible. No such limits exist on software beyond maybe performance and memory constraints. But both of those are in abundance, so we can and do patch over crap endlessly. Every one of us has had that moment where we think or say, "how does this even work?" But until the user hits the wrong edge case they have no idea how rickety the underlying code is. > This happens billions of times a day, all across the world, and mostly flawlessly. No, I'd argue it's much more common for there to be flaws. They're just not obvious. They're random crap like my phone continuing to vibrate after I've answered the call until I get another call or text. Or options disappearing from a web app because something didn't load 100% correctly. Or the joys of flaky Bluetooth pairing. The list is endless. "Have you tried turning it off and on again" is evidence of this. It's normal for software systems to get into such inscrutably subtle bad states that the only fix is to wipe everything and reload from scratch.
- bitwize 2y agoComplaining about too many abstractions in software is like complaining about too many meetings in a Scrum shop. It's true. Everybody knows it. Or rather, it would be true if efficiency of the software/development process were the thing being optimized for. But it's ultimately a short-sighted perspective because you're not thinking of the people involved. In the case of Scrum, Scrum is implemented because it gives managers and stakeholders some semblance of observability and control over the software development process. Granted, Scrum shops are merely cosplaying at implementing a rigorous, controlled methodology, but if you take that semblance away you will have angry, frustrated decision makers who resent the software teams for being opaque and unwilling to commit to budgets or schedules. In the case of abstractions... maybe there are a bunch of junior devs who just can't learn the complexities of SQL and need an ORM layer in order to reckon with the database. (I worked at a software shop where the most senior dev was like this; part of the reason I was brought on board was because I knew how to munge the PL/SQL scripts that formed part of their ETL process.) Maybe one part needs to be completely decoupled from another part in order to allow, for example, easy swapping of storage backends, or the creation of mocks for testing. Maybe some architect or staff SE is just empire-building, but at any rate they're way above your pay grade so the thing will be built their way, with their favorite toolkit of abstractions and advocating for the use of fewer abstractions will get you nowhere. If you're working on a team of John Carmacks, great! You will be able to design and build a refined jewel of a software system that contains just the right amount of abstraction to enable your team of Carmacks to maintain and extend it easily while still running smoothly on a 386. Unfortunately, most software teams are not like that, most customers are not like that, so the systems they build will develop the abstractions needed to adjust to the peculiarities of that team.
- kleiba 2y agoOT: anyone's got an idea why Firefox would not be able to display that page in reader mode (button in the URL bar not showing up)? For some reason, my eyes cannot cope with white text on black backgrounds, so I usually just go to reader mode in cases like this article. But here, this option does not exist, for some reason?
- wryl 2y agoThanks for the feedback regarding this, I've been trying to find a middle-ground between my authoring style (writing raw HTML with low overhead, instead of using a static site generator) and "portable readability". I have a feeling it's just me not annotating the markup correctly, which I am in the process of fixing and porting around!
- marcosdumay 2y agoPersonally, I've found that adding 3 lines of javascript to make a style switcher leads to great results. (You know you can simply load a CSS file in javascript and apply it, in a single command?)
- pauleee 2y agoThey didn't use proper html syntax like <article>, <h2>, etc.; only <div>. With this it's not possible for the browser to know what is the content of the article.
- marcellus23 2y agoIt's possible, just more difficult. E.g., Safari reader mode works fine for this page.
- kwhitefoot 2y agoNo idea. And I won't be reading it either. Someone wanting the world's attention because of a crisis really should not add extra friction.
- williamcotton 2y agoShallow and composable is something we all experience when using UNIX tooling. GUIs are where this all falls apart as they are literal islands that don’t communicate with each other in a composable manner. I’ve been experimenting with some GUI-meets-shell-pipeline ideas with a tool I’ve been working on call guish. https://github.com/williamcotton/guish https://github.com/williamcotton/guish I’m curious to know if anyone knows of any similar tools or approaches to composable GUIs!
- wryl 2y agoThis is really, really cool! Definitely going to share this around, I love tools like this. They bring so much visibility into dark spaces.
- williamcotton 2y agoThanks! I started on it a week ago so it is just barely presentable at this point. I expect there are many glitches and bugs that I am completely unaware of! The parser is off-the-shelf and seems robust. The AST-to-bash aspect is a bit messy. Wrapping arguments with spaces in them with either " or ' is somewhat of an unsolved problem. Like, it's hard to tell if someone wants to embed a bash variable and thus wants " or if they are using something like awk that uses $var itself and thus need '. We'll see how it goes!
- wryl 2y agoIt's still really impressive! Comparisons were thrown around to nushell, which is also a really impressive project. I can see the vision and I hope to follow along! :)
- marcosdumay 2y agoYes, shallow, wide, and composable. That's how our abstractions should be. But the larger problem is not GUIs. GUIs are a problem, but they are necessarily at the top of the abstraction stack, so the problem doesn't compose any further. (What interestingly means they are so much of a problem that they aren't anymore.) The elephant in the room nowadays are distributed systems.
- rednafi 2y agoIt’s absurd to complain about abstraction. Hardware will continue to leapfrog the pace of software innovation and things will keep getting better. Sure layers of abstraction is leaky and has their issues, but I don’t want to write a hipster language in a hipster editor. If you enjoy that, great. Also, it’s easy to look at the past with rose tinted glasses. Modern softwares are bloated mess but still a million times more productive.
- adamrezich 2y ago> Hardware will continue to leapfrog the pace of software innovation and things will keep getting better. This is wishful thinking. Try running Windows 2000 on era-appropriate consumer hardware and tell me just how much better off we truly are now with bloated and unresponsive web apps. > Also, it’s easy to look at the past with rose tinted glasses. Modern softwares are bloated mess but still a million times more productive. What metrics are you using to quantify "a million times more productive"?
- woah 2y agoI hate when people try to promote things by inventing a crisis
- beryilma 2y agoI don't think we have a software crisis. Millions of programmers are able to create more or less useful programs all over the word; everything including your toaster is running software on it succesfully enough; and the community was able to build programs that are accessible to all from a 5 year old kid all the way to your grandparents. Where is the crisis in it? However, we have a project management crisis, which is not only limited to software, where people in charge of planning are distanced from people in charge of the delivery. And we don't seem to be able to bridge the gap. Agile, Scrum, whatever are indicators of this gap where "gurus" take all of us as fools and we are not able to produce anything better ourselves. Commoditization of software development is also contributing to this mess because people of all skill levels can find a way to partake in this activity with results of varying success. This is not good or bad, but just the nature of ease of entry into the field. Not much different than food business where we have both Michelin star restaurants as well as MacDonalds of the world both of which have consumers. But we don't say we have a restaurant crisis.
- nicce 2y ago> I don't think we have a software crisis. Millions of programmers are able to create more or less useful programs all over the word; everything including your toaster is running software on it succesfully enough; and the community was able to build programs that are accessible to all from a 5 year old kid all the way to your grandparents. Where is the crisis in it? About that toaster point; this is the actual, real, concrete example of the software crisis. Your toaster runs bad code. Bad code that is not designed with resiliency or security in mind but is connected to internet. It reduces your toaster's lifetime. In the past, you might have had a toaster which lasted 10 years. Now, because of the bad software and maybe even mandated Wifi or Bluetooth connection, your toaster is garbage after 2 years because the vendor stopped pushing updates. Or maybe there were no updates at all. But because we might not always directly see it, or because the current hyper consumption and never-ending buying of new products, the crisis is not always that visible. We might be even okay that toaster stopped working after 2 years, and did not pay attention or knew why that happened. But maybe it was part of Mirai botnet https://www.cloudflare.com/learning/ddos/glossary/mirai-botnet/ https://www.cloudflare.com/learning/ddos/glossary/mirai-botn... Likely toaster was not part of that, as they use simpler chips, but who knows.
- fungiblecog 2y agoJust watch all the Rich Hickey videos on YouTube and you’ll understand where it’s all gone wrong.
- wryl 2y agoWith a splash of Joe Armstrong!
- peter_d_sherman 2y ago>"We developed methods of building nested layers of abstractions, hiding information at multiple levels. We took the problem of constructing software and morphed it into towering layers." https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/ https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a... https://en.wikipedia.org/wiki/Tower_of_Babel https://en.wikipedia.org/wiki/Tower_of_Babel https://en.wikipedia.org/wiki/Hierarchy https://en.wikipedia.org/wiki/Hierarchy https://en.wikipedia.org/wiki/Abstraction https://en.wikipedia.org/wiki/Abstraction https://en.wikipedia.org/wiki/Abstraction_(computer_science) https://en.wikipedia.org/wiki/Abstraction_(computer_science) (Compare and contrast!)
- brundolf 2y agoThis paints abstraction like an evil, but it's an unavoidable tool for any human-made software to reach certain capabilities Rich Hickey said something along the lines of "A novice juggler may be able to juggle two or three balls, but the best juggler in the world can only juggle maybe nine balls. There isn't an order of magnitude difference in human ability, we hit a ceiling quickly." If we are to surpass those limits, we have no choice but to abstract Of course there may be bad abstractions or too many abstractions in a given case, which is what I think the author is mad at. But that's an important distinction This part is also plainly false: > It is no longer easy to build software, and nothing comes with a manual. Making software has never been easier or better-documented
- dgb23 2y agoIn that talk he mainly proposes simplicity (decomposition) rather than abstraction. We don’t necessarily need indirection to understand a whole, complex thing. In order to deal with complexity, we need to disentangle it, so we can understand each part in isolation. Hiding complexity with indirection, puts distance between the us and thing we have to reason about. Abstraction is good for users (devs or not), so they don’t have to care about the details, but it doesn’t make it easier for us to build it.
- 0x1ceb00da 2y agoThe author mentioned handmade as a step in the right direction but the handmade creator more or less gave up on the project after a couple years and didn't accomplish his goal of delivering a final product.
- et1337 2y agoThe later videos are like cautionary tales… 5 years in, no game in sight, and you’re 30 videos deep into writing a sophisticated global illumination system…
- adamrezich 2y agoGame design and programming are largely orthogonal skills, and procrastinating working on the former in service of the latter is perhaps the most common game development mistake of all time.
- deleted 2y ago[deleted]
- socketcluster 2y ago> It is no longer easy to build software It is very easy if you know the right tools for the right job, but information about these are suppressed so you never hear about them. What the vast majority of people think the tech tooling landscape looks like and what it actually looks like are very different. The tools we know about are mostly horrible. They try to be silver bullets but they're really not good for anything... Yet they're the most popular tools. I think it's about capital influence, as hinted by the article. For example, with the tool I'm using now, I made a video showing how to build a relatively complex marketplace app (5+ pages) in 3 hours with login, access control, schema validation, complex filtered views from scratch using only a browser and without downloading any software (serverless). The whole app is less than 700 lines of HTML markup and 12 lines of JavaScript code. The video got like 10 views.
- bckr 2y agoLink it!
- dualogy 2y agoAlthough not sure, I guess socketcluster might be referring to what is further elaborated on in these earlier posts I just quickly stalked: https://news.ycombinator.com/item?id=40326185 https://news.ycombinator.com/item?id=40326185 https://news.ycombinator.com/item?id=40530828 https://news.ycombinator.com/item?id=40530828
- socketcluster 2y agoHere: https://www.youtube.com/watch?v=A0PJ1KlxDtM https://www.youtube.com/watch?v=A0PJ1KlxDtM
- tavavex 2y ago> with the tool I'm using now Correction: with the tool you created and are not-so-subtly trying to market right now. Complete with an $18/mo subscription fee, no users and (of course) a cryptocurrency that's fueled by promises and hype. No, despite the conspiratorial twist, modern tooling is more flexible and easier to use than ever before. It has flaws, but those flaws are nothing compared to what developers had to go through a couple of decades ago. There's no big collusion to cover up your tool.
- mlhpdx 2y agoThe missing piece in this and similar arguments is the miracle that we have before us. It is unfathomably wonderful that we have the breadth of technology (including software) that we do given where we’ve come from. As with everything we’ve done and will ever do it is messy, flawed and tragic as well but that doesn’t diminish it. If you’re going to advocate we change, it might start with recognition of the value we have and the effort it took to realize it. The flaws can only be resolved insomuch as they solutions don’t dilute the gift.
- mixmastamyk 2y agoThis is discussing some of the same subjects as Brooks' Mythical Man Month and related essays. Our solutions are made up of "pure thought stuff" and so can be organized in almost any possible way. We've found better ways to organize things over the years, and reduce incidental complexity too. We continue to chip away at small problems year after year. But, there's "no silver bullet," to give us a 10x improvement. Believe I agree with the piece that we have too many layers building up lately. Would like to see several of them squashed. :-D
- devwastaken 2y agoExample - "I made an app" is considered more signal than developing the underlying tools and libraries that app needed to exist. Making everything "easy" backfires because those doing the hard work doing realize it's a rigged game.
- jocoda 2y agoThis is one of those articles that you read and realize that that was a waste of time. Concludes that the prime villain of this supposed crisis is abstraction and provides a simple solution - "... solution ... a constraint on the number of layers of abstractions we are allowed to apply. Uh-huh, all hail to the coming of the layer police. Ends - "Things can be better. I'll show you how." - @author - Maybe it would have been better to under promise and over deliver instead? ---- But that got me asking whether there might indeed be a software crisis and yes, I think there is a crises of sorts on the personal level. Maybe for others too. It's not one that is structural as the author proposes. It's that the software landscape is so vast and chaotic. There's so much going on that it's almost impossible to know where to focus. FOMO I suppose, too much to do and not enough time. So many clever people, so much energy, doing all kinds of amazing things. For many different reasons, some good, some not. A lot of it looks, to coin a phrase, like fractal duplication, e.g. yet another JS framework, yet another game engine, yet another bullshit SAAS, just because. Seems inherent redundancy is built in to the systems. Good times, I suppose.
- Guthur 2y agoThe problem is that the abstractions we are forced to create do not drastically change how we can think about the problem domain in question. We're often just hiding some mechanical details when in truth we should be searching for and codifying fundamental ontologies about the given domain. It's hard because at the same time we can't yet be users because the thing does not yet exist, but yet we can't really know what we must build without a user to inform us. We can create some imaginary notions with various creative explorations, but images can often deceive. I do believe the tools most used for software development are fundamentally terrible at modelling these ontologies and are really little more than telling computer to do A then do B and so have never really abstracted much at all.
- geekraver 2y agoIs this going to be followed up with a “functional programming is the bestest” post?
- swader999 2y agoSoftware should strive to be no more complex than the underlying problems it attempts to solve. I don't think it can be simpler than the reality it needs to address.
- djoldman 2y ago@wryl: I can't find a definition of the title term, "Software Crisis," anywhere in the post. Is it "...[the] growing complexity of software..."? It's difficult to reason about something with no definition.
- alxmng 2y agohttps://en.m.wikipedia.org/wiki/Software_crisis https://en.m.wikipedia.org/wiki/Software_crisis
- ziofill 2y agoThis reminds me of Jonathan Blow when he says that software has been free riding on hardware leaps and bounds for decades https://youtu.be/AikEFhCaZwo?si=9klvCUW5qHtOpePh https://youtu.be/AikEFhCaZwo?si=9klvCUW5qHtOpePh
- brabel 2y agoI agree with the statement that there's a software crisis, but completely disagree with the author about what the problem is caused by. The software crisis, if there is one, is caused by complexity. Complexity is the single enemy of a software developer. I would say that reducing complexity is the whole purpose of the software engineering field. I have many small hobby projects where I am the sole developer, and I still struggle with complexity sometimes... I've tried many languages and programming paradigms and still haven't found one that actually "solves" complexity. I am convinced, for now, that the only solution is developer discipline and, guess... good abstractions. Because complexity doesn't necessarily come from abstractions. In fact, it's the exact opposite: the only way we know to make things "look" simpler, so that we can make sense of it, is to abstract away the problem! Do you need to know how the network works to send a HTTP request?? No!!! You barely need to know HTTP, you just call something like "fetch url" or click a link on a browser and you're done. This is not something we do because we are stuck on some local maximum. Whatever you do to "hide" complexity that is not crucial to solving a certain problem, will be called an "abstraction" of the problem, or a "model" if you will. They always have downsides, of course, but those are vastly offset by the benefits. I can write "fetch url" and be done, but if something goes wrong, I may need to actually have a basic understanding of what that's doing: is the URL syntax wrong, the domain down, the network down, the internet down, lack of authorization?? You may need to dig a bit, but 99% of the time you don't: so you still get the benefit of doing in one line what is actually a really complex sequence of actions, all done behind the layers of abstractions the people who came before you created to make your life easier. > Various efforts have been made to address pieces of the software crisis, but they all follow the same pattern of "abstract it away" Of course they do. Abstracting away is the very definition of addressing complexity. I believe what the author is actually trying to say is that some of the abstractions we have come up with are not the best abstractions yet. I would agree with that because as hardware evolves, what the best abstraction is for dealing with it also should evolve, but it hardly does so. That's why we end up with a mismatch between our lower level abstractions (Assembly, C) and the modern hardware we write software for. Most of the time this doesn't matter because most of us are writing software on a much higher level, where differences between hardware are either irrelevant or so far below the layers we're operating on as to be completely out of sight (which is absolutely wonderful... having to write code specific for certain hardware is the last thing you want if all you're doing is writing a web app, as 90% of developers do), but sure, sometimes it does. > We lament the easy access to fundamental features of a machine, like graphics and sound. It is no longer easy to build software, and nothing comes with a manual. I have trouble to take this seriously. Is the author a developer? If so, how can you not know just how wonderful we have it these days?? We can access graphics and sound even from a web app running on a browser!! Any desktop toolkit has easy to use APIs for that... we even have things like game engines that will let you easily access the GPU to render extremely complex 3D visualisations... which most of the time working on most Operating Systems in use without you having to worry about it. Just a couple of decades ago, you would indeed have to buy a Manual for the specific hardware you were targeting to talk to a sound board, but those days are long gone for most of us (people in the embedded software world are the only ones still doing that sort of thing). If you think it's hard to build software today, I can only assume you have not built anything like even 10 years ago. And the thing is: it's easy because the "hard problems" are mostly abstracted away and you don't even need to know they exist! Memory allocation?? No worries, use one of a million language that come with a GC... even if you want the most performant code, just use Rust, still you don't need to worry (but you can if you must!!! Go with Zig if you really want to know where your bytes go). Emit sound? Tell me which toolkit doesn't come with that ready off the box?? Efficient hash table? Every language has one in its standard lib. Hot code reloading so you can quickly iterate?? Well, are you using Lisp? If so, you've had that since the early 80's, otherwise, perhaps try Smalltalk, or even Java (use jdb, which lets you "redefine" each class on the go, or the IntelliJ debugger, just rebuild it while it's on, specially if you also use DCEVM which makes the JVM more capable in this regard) or Dart/Flutter, which has that out of the box. Almost any other problem you may come across , either your language makes it easy for you already or you can use a library for it, which is as easy to install as typing "getme a lib"). Not to mention that if you don't know how to do something, ask AI, it will tell you exactly how to do it, with code samples and a full explanation, in most circumstances (if you haven't tried in the last year or so, try again, AI is getting scary good). Now, back to what the problem actually is: how do we create abstractions that are only as complex as they need to be, and how many "layers" of abstractions are ideal? What programming model is ideal for a certain problem?? Sometimes OOP, sometimes FP, sometimes LP... but how to determine it? How to make software that any competent developer can come and start modifying with the minimum of fuss. These are the real problems we should be solving. > Programming models, user interfaces, and foundational hardware can, and must, be shallow and composable. We must, as a profession, give agency to the users of the tools we produce. This is the part where I almost agree with the author. I don't really see why there should be a limit on how "shallow" our layers of abstractions should be because that seems to me to limit how complex problems you can address... I believe the current limit is the human brain's ability to make sense of things, so perhaps there is a shallow limit, but perhaps in the future we may be able to break that barrier. Finally, about user agency, well, welcome to the FOSS movement :D that's what it is all about!!
- lulzury 2y ago“Modularity based on abstraction is the way things get done” --Barbara Liskov Something as big and complex as the internet, which covers technologies from email to fiber, is held together by layered abstractions. Also, software has gotten incredibly better since the 70s. We've built so much better tooling (and I believe tooling can help close the gap on growing complexity). When I was learning how to program, I had to double check I had every semicolon in the right place before hitting compile. I simply don't have to do that anymore. I can even get an entire API auto-completed using something like copilot on VSCode. Nonetheless, a very thought-provoking article. Thank you for sharing!
- kyleperik 2y agoAlong the same lines is a general theory of mine that many people in this era generally underestimate the cost of coordination, and overestimate the efficiency gain of bulk processing.
- lincpa 2y ago[dead]