7 ms·
The fun thing is that, until CS slows down, stuff gets better so fast that we get to reimplement the same thing, but 10x better every 5 years or so. First I wr
by hedora 4y ago
The fun thing is that, until CS slows down, stuff gets better so fast that we get to reimplement the same thing, but 10x better every 5 years or so.
First I wrote single threaded code code with automatic memory management, then single threaded synchronous with manual memory management, then synchronous multi-threaded, then async, and then async lock free.
Now I am writing async lock free, and the compiler is helping me prove it is data-race-free and memory safe.
Each time I rewrite this stuff, someone hands me 6-7 figures. This is awesome.
- kneebonian 4y ago> so fast that we get to reimplement the same thing, but 10x better every 5 years or so. Citation needed. Seems that it just us getting more and more abstracted which can make it easier but not necessarily easier. The hardest part for the next gen of developers is not having Moore's law to save them from crappy coding.
- rr808 4y agoRight, I worked on a async non-blocking project in C++ in the 90s. It was a lot simpler than any modern project, no cloud, no yaml, no containers, no fancy security. Sure it didn't have a pretty web interface but was great software.
- userbinator 4y ago10x worse is how I'd put it. First example that comes to mind: Microsoft Teams.
- shrimp_emoji 4y agoTeams is special. You could've cited Slack or Discord. Teams is an anomaly in horrible software quality that *only* Microsoft can manage to produce (also see OneNote (but DON'T see VS Code -- that's somehow really efficient despite being Electron!)).
- YZF 4y agoMore like the hardware gets faster but the software gets slower or stays the same ;) Lock-free goes way back. Multi-threaded goes way back. Both more than 20 years. SIMD goes way back. GPGPU goes way back. What is newer-ish are large scale distributed systems. But even that isn't so new any more.
- mumblemumble 4y agoFor a lot of this stuff 20 years is basically new in my book. MPI dates back at least 30 years and I still sometimes wonder if the only reason we don't use it anymore is because nobody wants to deal with C. I spend too much time these days watching technology like Spark make things slower rather than faster because nowadays the Java platform (not to mention containerization) is becoming an increasingly efficient way to splat oneself into the memory wall.
- asdfman123 4y agoHow do you make 7 figures writing code and not sitting in meetings all day talking about eye gougingly boring business requirements?
- throwaway71271 4y agowhat exactly is 10x better than 5 years ago? the technology gets better but the outcome gets worse somehow. most of the programs i use (besides the browser) are 20-50 years old (paste, cut, xterm, grep, emacs etc), almost any new thing i try is horribly slow (slack, whatsapp etc, the mac terminal app, even the mail app is slow compared to mutt) open a web page on a computer without adblock and look at what we have built https://www.youtube.com/watch?v=pq7NLMwynYg https://www.youtube.com/watch?v=pq7NLMwynYg (funny video demonstrating the state of the modern web)
- VaxWithSex 4y agoripgrep
- anonzzzies 4y ago> Now I am writing async lock free, and the compiler is helping me prove it is data-race-free and memory safe. I am writing async lock free code as well, but which compiler is helping you? Rust? As far as I know, it's cutting edge research to figure out a type system that fixes this for you. But maybe i'm not up to date. > stuff gets better so fast that we get to reimplement the same thing So you are leaving the API in-tact and just change the implementation with new techniques? Or even better, you just rewrite low-level libraries you are using? Sounds like the ideal job to me.
- mchaver 4y agoUnfortunately users are not seeing 10x better performance with the average application. A bit of the curse of more resources leads to using more resources wastefully.
- yamtaddle 4y agoWhen I look at team sizes for '80s and '90s programs, and how fast those teams worked, and consider what I'd expect to be the team size for a modern program tackling the exact same features and how long I'd expect development to take, it also makes me wonder just how much these supposed productivity improvements—which are promoted as where these benefits are being realized, since they're plainly not showing up in program & system performance for the user—actually, like, exist.
- shrimp_emoji 4y agohttps://en.wikipedia.org/wiki/Braess%27s_paradox https://en.wikipedia.org/wiki/Braess%27s_paradox but with RAM
- ChuckNorris89 4y ago>Each time I rewrite this stuff, someone hands me 6-7 figures. This is awesome. I envy you.