Yes, I understand the acronyms, but they are being used as jargon, not in a instructive way. If I were to talk about a web framework and say, "we've got our JS

Yes, I understand the acronyms, but they are being used as jargon, not in a instructive way. If I were to talk about a web framework and say, "we've got our JSON files wrong and our package configs are cluttered, and don't get me started on the XML files," it's clear that it is metonymy [1]. Knowing that JSON is JavaScript Object Notation, the package.json is used for Node Package Manager, and that XML is a file format doesn't capture the feeling that a developer might have reading that sentence, and it doesn't instruct. [1] https://en.wikipedia.org/wiki/Metonymy https://en.wikipedia.org/wiki/Metonymy From the article: >>> It was Reinhard in years past, then it was Hable, now it’s ACES RRT. And it’s stop #1 on the train of Why does every game this year look exactly the goddamn same? If the problem the author is facing is a gap between art skills and technical skills, then the post could be less angry and more informative about color theory or rendering technology, maybe bridging the needed skills.