6 ms·
The idea that we will have some abstraction that will someday (in the foreseeable future) save us from all of this difficult work sounds very far fetched to me,
by onion2k 6y ago
The idea that we will have some abstraction that will someday (in the foreseeable future) save us from all of this difficult work sounds very far fetched to me, and I can’t imagine how that would work.
The problem here is that word "all". It's never going to be easy to do everything. Some part will be hard. That's where the value lies, and that's what your best people focus on. But everything else will be abstracted away. It's already happened. 30 years ago making a GUI was hard, but VB changed that. Then making a web app was hard, but PHP changed that. Then app layout was hard, and Bootstrap changed that. Then ML was hard, and Torch changed that. Every hard problem gets a 90% working solution that's more than good enough for most companies. There'll always be a few companies that pay people to work in the last 10%, so the problem never really disappears, but fewer and fewer people work on it.
The key to keeping growth going in tech is to keep finding new problems, not to keep everyone working on the same old problems.
- wongarsu 6y agoEven with just the advances in better programming languages (and newer versions of old languages) and better IDEs we have achieved tremendous productivity increases in the last 30 years. It's just that so far the amount of work has grown to absorb the added productivity. There are some parallels to induced demand in road construction: when you build a new road to ease traffic, traffic increases to use up that capacity. But that isn't a sign that demand is infinite, it's just that demand is limited by the available resources. If you keep building roads, at some point they will become emptier. Similarly, at some point development productivity will outpace demand, and we will start optimizing our own jobs away.
- chrisco255 6y agoI'm not convinced. I think new abstractions beget new abstractions. There's so much left to explore in software. Imagine being in the first century of the printing press and imagining that the press is going to put all these poor monks out of business or that there's not much left to explore with writing. Speaking of writing, how much has our word processing technology succeeded in making authors obsolete?
- visarga 6y ago> how much has our word processing technology succeeded in making authors obsolete? makes more sense to think about GPT-2 like language models replacing authors, than word processors
- contextfree 6y agopresumably those models will be (are already being) incorporated into word processors?
- lentil_soup 6y agoI don't think word processors are the right analogy. In your example programmers are the monks or the press makers. At some point we're not needed any more (at least at the same scale) since word processors have already been built.
- wongarsu 6y agoPrinters are actually a great analogy. Printing presses became more sophisticated, but the printing business grew even further, guaranteeing lots of jobs in the printing industry. But at some point we reached peak demand, but presses continued requiring fewer and fewer workers. Today there are still people manning the presses of publishing houses and newspapers, but in 200 years of improvement we made the job a much smaller niche.
- wolco 6y agoI worked in the print industry when I was younger. The increase in Posters / bill boards / custom cardboard standing displays actually created so many more print jobs. From phd book binding to custom business print jobs to online demand printing there are so many more things we are printing now. There are more newspapers but they are all owned by larger players which means different types of machines and parts. A better example might have been blacksmiths. Although the amount of people making cars is a larger group.
- sakoht 6y agoDemand for the things we want _today_ will be met. But progress leads to new demands, and they are more complicated. Anthropologists estimate that the work week was at 20 hrs at the end of the Stone Age. We have been inventing new problems in the vacuum created by our successes for, literally, millennia.
- barrkel 6y agoI think it was easier to build an acceptable GUI in 2000 with VB or Delphi than it is today with our web stacks.
- sokoloff 6y agoI also think the standard of “what is acceptable?” was much lower back then.
- barrkel 6y agoI think that's mostly it. Design has a much larger role, and form-oriented development with common controls doesn't cut it. You couldn't imagine an app like Facebook in a forms-style UI, it's almost ludicrous to imagine. Looked at retrospectively, forms were just one step above green screen applications on a terminal, transplanting one set of structural idioms to another, like for like.
- nogabebop23 6y agoIf forms are essentially terminal apps, is FB much different from a teletype news service, with hyper-filtered content and an infinite set of data sources? I see massive sea change in connectivity and immersiveness of today, but not really in what we're trying to achieve.
- rsynnott 6y agoI'm not sure that's true. Here's the UI hall of shame, highlighting the worst of the 90s: http://hallofshame.gp.co.at/shame.htm http://hallofshame.gp.co.at/shame.htm Most of the stuff there would be just... normal now. It's quite unusual for SPAs to have a decent consistent UX. And the slowness would never have been tolerated back in the day.
- contextfree 6y agothe author of that page seems to believe that mouse hover feedback is bad, even when it's a simple highlight?!
- narag 6y agoEvery hard problem gets a 90% working solution that's more than good enough for most companies. I very much agree with your comment, but allow me a little nitpicking. Solutions aren't 90%, more like 50% or 20% or whatever. It may sound absurd to discuss a number there, since it's more like a way of speaking, just wanted to add that for most problems the solution is barely better than the default option. In other words, there's still a lot of room for improvement, huge actually but, as you say, it might come in small pieces.
- rsynnott 6y ago> 0 years ago making a GUI was hard, but VB changed that. Then making a web app was hard, but PHP changed that. Fortunately, the SPA Plague made it very difficult again.
- collyw 6y agoPlus kubernetes / autoscaling on the backend.....