3 ms·
We have spent the last 50 years trying to automate our job away. Many projects that 20 years ago took an entire team a year or more are now weekend projects for
by wongarsu 5y ago
We have spent the last 50 years trying to automate our job away. Many projects that 20 years ago took an entire team a year or more are now weekend projects for a single person, because of how much better our programming languages, libraries, APIs, IDEs, linters, etc have become. But demand turns out to be incredibly elastic. A 50% increase in productivity just means that there's 400% more work, because so many new things have now become cost effective to try.
Of course there is bound to be an end to this, a peak-software if you so will, where productivity increases will stop being offset by demand increases. I might live to see that day, but this AI wave is unlikely to be it. Yes, it brings some new tools that make programming easier, but it stimulates more than enough demand to offset that.
- astrobe_ 5y ago> how much better our programming languages, libraries, APIs, IDEs, linters, etc have become It's just libraries, really. Or libraries are 80% of the gain. So it's less about automation and tools and more about code reuse (sometimes it's even just binary reuse - you surely do that everyday by calling dynamic libraries). The progress you note in the last 20-30 years is just Internet that became widely available. First at work and Unis, and then at home. We switched from sending disks by mail to downloading stuff from FTP servers. Recently WWW Git front-ends gave it another serious boost. That's what happened. > But demand turns out to be incredibly elastic. A 50% increase in productivity just means that there's 400% more work, because so many new things have now become cost effective to try. I would credit Moore's law for that instead. Really, if one can do e.g. affordable, real-time machine vision stuff today, it has more to do with CPUs and GPUs gaining power every year, than software getting better.
- hervature 5y ago> I would credit Moore's law for that instead. Really, if one can do e.g. affordable, real-time machine vision stuff today, it has more to do with CPUs and GPUs gaining power every year, than software getting better. How can you say that seriously when, for the vast majority of people, a computer vision project consists of `import cv2`?
- ramesh31 5y ago>I would credit Moore's law for that instead. Really, if one can do e.g. affordable, real-time machine vision stuff today, it has more to do with CPUs and GPUs gaining power every year, than software getting better. Not really. AlexNet was a watershed moment for computer science, and the kind of things that were possible by 2015 with AI that weren't possible in 2010 far outstrip the gains in hardware advancement during that time.
- dougabug 5y agoTrue. VGG models halved the ImageNet error rate of AlexNet two years after AlexNet, followed by ResNet models a little over a year later which halved the error rate again. Recent NAS generated models are up to 20x more computationally efficient than ResNet models of the same accuracy.
- Clubber 5y ago>We have spent the last 50 years trying to automate our job away. Yes I've heard it for 25 years. It's mostly low hanging fruit and it hasn't been done with auto-coding per-se, but more data drive architecture where a layman can do a basic website. Anything custom or sophisticated requires programming knowledge though, and since they are proprietary systems, it's a lot more expensive.