News for hackers. Stuff that matters.
Re:New Grad vs. Senior Dev by TheOtherHobbes on Saturday March 28, 2020 @04:51PM (#22714236)
I sometimes wonder if CS should be renamed Computer Pseudo-Science. I blame Knuth and (mostly) Dijkstra for propagating the falsehood that you can estimate the performance of real code on real hardware with a some elegant academic blackboard math which gives you the wrong answer for many practical applications.

It's not that Big O isn't useful - it's that it's taught as a set of "proofs" which somehow make it appear objective and "correct", when in reality performance is at least as dependent on cache architecture, median size-of-n, memory bandwidth, and other implementation details.

Anyone who graduates CS without having been taught this very forcefully - preferably during a practical project - should be refunded at least some of their course fees.

Re:New Grad vs. Senior Dev by herbstein on Saturday March 28, 2020 @05:15PM (#22714389)
But Big O was a lot more directly correlated when the CPU wasn't doing "magic" optimizations on its own. It was still estimations with an invisible constant factor, of course,
Re:New Grad vs. Senior Dev by koreth1 on Sunday March 29, 2020 @02:32AM (#22716875)
This is a key point. The gargantuan performance difference between main memory and the CPU cache (or indeed, the existence of significant CPU caches at all) happened well after big-O was firmly established in the CS curriculum.