5 ms·
The problem is you never know when you’ll go from “dev who doesn’t care” to “dev who does”. While I agree that the details of StoreLoad are likely a distractio
by kasey_junk 7y ago
The problem is you never know when you’ll go from “dev who doesn’t care” to “dev who does”.
While I agree that the details of StoreLoad are likely a distraction the big picture concepts of cache coherence presented in this article are table stakes for performant systems.
- strstr 7y agoWhile that might be true in practice, I do think not knowing when you transition between those two indicates a failing by your coworkers/mentors. I encourage people I work with to read many of the books in this book series. I particularly encourage them to read “Hardware and Software Support for Virtualization”, since it’s basically a book on their job.
- steev 7y agoJust to be clear, the book series you are referring to is "Synthesis Lectures on Computer Architecture" published by Morgan-Claypool, right? If you had to rank them in importance for the average engineer, how would you rank them?
- onion2k 7y agoThe problem is you never know when you’ll go from “dev who doesn’t care” to “dev who does”. This is true for literally every hard problem in dev though, and the implication that you need to grasp everything just in case you need it is silly. The problem space in compsci is too big to know everything. We have to choose.
- afiori 7y agoPart of the reason this kind of blogs exist is to give you more information to choose properly.