I think IT reached bottom when we started using numeronyms like L10n (localization) or K8s (Kubernetes).
I agree. That practice is the worst.
"My article is about How to Design Programs (HtDP)..."
Then later the article: "In the HtDP book it mentions...."
This makes life easier for those less familiar with the subject matter.
As a software developer with a forty year career behind me I'm quite familiar with the "SICP" book. But for some reason my brain won't persist the connection between the full title and the SICP acronym when I bump into it. Yet somehow I can recall what each and every assembly language mnemonic means across a fairly broad range of micro and mini computer processors.
> maybe that's a sign that particular thread isn't for you, and that you likely have little of value to add.
Sure I may not have much to add, but the reason to read a thread, article or essay is to become familiar with the subject matter because it sounds interesting. Don't assume your reader is an expert in decoding your special and often made up acronyms.
> TAoCP (er, Knuth's "The Art of Computer Programming")
I also would not have recognized TAoCP as referring to the Knuth book. Not all corners of the tech world commonly refer to tech books by their initials. That doesn't mean they have nothing useful to say about them.
Acronyms and initialisms with no explanation are passive aggressive gatekeeping.
OTOH it's really important to spell them out at a right time, to help people not yet in the know understand them. So thank you!
SICP = Structure and Interpretation of Computer Programs: https://mitp-content-server.mit.edu/books/content/sectbyfn/b...
HtDP = How to Design Programs: https://htdp.org/
Sometimes I think gratuitous use of acronyms (initialisms for the pedants) has been the biggest impediment to learning throughout my career.