4 ms·
> Why is he discarding compsci literally in the introduction? Does he really think "big O" is all there is, presumably because those ivory tower compsci people
by YesThatTom2 6y ago
> Why is he discarding compsci literally in the introduction? Does he really think "big O" is all there is, presumably because those ivory tower compsci people have no clue about computers?
Hi! I'm the author. I do have an ivory tower compsci degree. I'm poking fun at myself as much as anyone else.
> There are some good bits of advice in the article, too, though.
Thanks! "Everything Sysadmin" is my 3x/yearly column in ACM Queue. My goal is to bring a bit of operational reality to an organization with a reputation for being ivory tower. Click on the phrase "everything sysadmin" to see the other columns I've written.
> So, when you are using C/C++, "small" for this problem is a billion elements.
I know, right? "Small" has gotten so big that we have to re-think our gut reactions and recalibrate our back-of-the-envelope estimations. Just imagine how big small will be for the next generation of developers?
- mark-r 6y agoMoore's law is dead. Small won't change nearly as fast as it used to.
- thewebcount 6y agoI just want to say that I really enjoyed this article. I was surprised to see all the negativity here on HN about it! Thank you for writing it, as it really got me thinking. I've done some of these things before, but it's easy to lose the forest for the trees when you're deep down in the middle of solving some problem.
- voldacar 6y ago>Just imagine how big small will be for the next generation of developers? about the same, since moores law is dead for cpus, and ram doesnt seem to be getting much faster either