I notice this a lot in RFCs within my company. Teams will put out architectures for new systems that contain massive amounts of acronyms and jargon for the syst

I notice this a lot in RFCs within my company. Teams will put out architectures for new systems that contain massive amounts of acronyms and jargon for the system they're building and/or replacing it's insanely frustrating. It doesn't help when the last system was named something completely arbitrary and is being replaced by a new system with an equally arbitrary new code name. ("Flywheel has served us well for years but due to limitations on the XCGA middleware we believe Project Kegerator is the future...")