6 ms·
What every programmer should know about memory shouldn't be 114 pages long.
by louthy 8y ago
What every programmer should know about memory shouldn't be 114 pages long.
- twtw 8y agoIf you are objecting to "every," then sure, not every programmer needs to know anything about memory. You can program without knowing that there is such a thing. But it's a fun title, and an excellent resource.
- oarabbus_ 8y agoNo, he's right. It's more than simply semantics. A better title would be "an extremely overwhelming of programmers don't need to know THIS much about memory"
- netmonk 8y agoThis is what people says when they have a dataset of 100 entries(<100mb) on their developpment laptop. How funny they look when production guys show them how their lame piece of code doesn't scale up with billion of entries in the production platform...But they dont care cause they are developpers, (or so called). Until the production guy rewrite their code and have them fired for incompetence (true story).
- Chlorus 8y ago> How funny they look when production guys show them how their lame piece of code doesn't scale up with billion of entries in the production platform...But they dont care cause they are developpers, (or so called) Why did the production guy even need them in the first place? Why were they hired? > (true story). And that production guy's name was Albert Einstein.
- abraae 8y agoOr perhaps some more positive phrasings: - If you know this much about memory, you'll know more than 99% of programmers. - What 99% of programmers don't know about memory.
- dewhelmed 8y agoThe second one reads like a Buzzfeed article... > What 99% of programmers don't know about memory... number 17 will shock you!
- milquetoastaf 8y agoThis attitude is why today's software is resource hungry garbage
- saagarjha 8y ago"A bit more than what most programmers need to know about memory, but would be nice if they read anyways"?
- asaddhamani 8y agoA _lot_ more. I don't see how most programmers would benefit from reading 100+ pages of low-level details about memory.
- mhh__ 8y agoBecause knowing your craft is important? Besides, if you don't find this interesting why become a programmer in the first place
- Chlorus 8y agoThere's a lot to learn about this craft, and people have to prioritize - knowing algorithms & data structures is more immediately useful compared to, say, knowing what scratchpad memory is. If I spent my time learning every detail about every system underpinning every abstraction, I would literally be 70 years old by the time I started writing code. > Besides, if you don't find this interesting why become a programmer in the first place Who is saying it's not interesting? We're arguing that it's not fundamentally vital knowledge to know the difference in RAS & CAS latency for SDRAM for most programmers.
- drainyard 8y agoBut learning algorithms and data structures literally requires you to know about memory on a pretty low level. As I'm sure you know, a lot of algorithms and data structures that are theoretically equal can be vastly different in practice in no small part because of how they use memory.