You joke, but I once worked on a team where nobody was able to point me to any coherent high-level documentation of what the system actually _did_... they all j

You joke, but I once worked on a team where nobody was able to point me to any coherent high-level documentation of what the system actually _did_... they all just walked around referring to it by some proprietary name as though you were some type of misinformed dunderhead for not understanding them. It took two hours of a manager talking and filling up a wall-sized whiteboard for me to discover that it was just a hideously over-engineered amalgamation of a CDN and document repository. If they'd had a diagram, README, or had even been able to give me the one-sentence overview then I suspect that the project's head count and productivity would have looked much different. This is all to say that if you 1) invent novel terminology for things that already exist, 2) don't document anything, and 3) run your team like a high school clique then you never have to worry about finding yourself out of a job. Thankfully my current gig has loads of video training and an interactive dictionary for proprietary terms in an attempt to combat this.