What every programmer should know about memory (2007) [pdf] | Hacker News
What every programmer should know about memory, Part 1 | Hacker News
What Every Programmer Should Know About Memory [pdf] (freebsd.org) 2 points by sebg | hide | past | favorite | discuss
Every programmer should know this stuff. You may not be directly manipulating memory in python, but you should know enough about memory (and other scarce resources) to know when you need to optimize your application.
Does every programmer really need to know the physics behind dynamic ram? What every programmer should know is the latency of the various memory types (cache, RAM, virtual) and their respective sizes.
This should probably have a (2007) in the title, FYI. “What every programmer should know about memory” is a modern classic and at first I thought this was a contemporary article about the paper.
The good news, even for those who cannot get into this presentation at JavaOne, is that there is a video and associated review of a version of 97 Things Every Programmer Should Know as given at Jazoon ...
Learn 10 essential math concepts that every programmer should understand - whether you’re building apps, designing games, working in AI, or preparing for technical interviews. This video covers the ...
You average Rails/Node/etc. programmer doesn't need to know half of what's covered during the 3 weeks of an undergraduate architecture course that's devoted to the memory system. How many programmers in 2012 are ever even going to need to cache-optimize their code? 25%? 10%? The content is fascinating, but the title is pretty wrong.