So why not call it Data Structures for Coders? Calling it Data Structures for Coding Interviews makes it sound like it's an answer guide to arbitrary brain teasers that are only useful for passing some test and have no application outside the job interview setting.

Not saying you are wrong, but it's pretty easy to not give something the optimal name. Sometimes your work is just more useful for some purpose other than the one you intended.

I don't disagree. My main complaint with the content of the article would be that they chose to introduce the cache at virtually the same time as memory in general. I found it very easy to follow for the most part and it gave some good intuition.

I'm just not sure if the title is accurate or (at worst) misleading.