What every programmer should know about memory
I didn’t graduate with a CS degree, but I’ve spent countless hours reading books, watching lectuers and actually even doing stanford OS class hw in my spare time to learn much more about algorithms, OS, network, and just how computer really works.
And I really love how much information is really freely available on the internet.
Recently a DigiPen masters alumni recommended us to read this paper from a professor that compiled all the information that a programmer needs to know about memory.
I became my daily read on the bus ride to/from work everyday, reading it from front to back. Although from time to time it goes to hardware specific details that is probably not necessary for more any software enginer to know, but the information is just so valuable I believe every programmer should read it just to make sure you understand all the implications of memory, cache, and how you should at least be aware of how you can affect it.
http://blogs.msdn.com/b/architectsrule/archive/2008/03/21/what-every-programmer-should-know-about-memory.aspx
Have fun!
