1. 15
  1. 4

    Interesting numbers, but most of the programmers I know don’t need to know about or ever bothered with issues of CPU cache latency. All these numbers are very uninteresting for people working at a high abstraction level on lightweight business logic, which is a huge part of our industry.

    1. 6

      The rule of thumb I try to live by is to deeply understand both the abstraction layer I live in and the layer immediately below it.

      So if I was a developer cranking out LOB apps, I definitely don’t need to worry about a branch mispredict slowdown or think about cache aware algorithms but I should absolutely know the general time to pull a big file off a disk or to shuttle JSON through the network.

    Stories with similar links:

    1. Numbers Every Programmer Should Know, By Year (interactive) via tobym 9 years ago | 2 points | no comments