Software has more than its fair share of acronyms, which we often choose to say phonetically, like SQL gets said “sequel.” We also have the TTY, and you often have to detach things from it. Depending on the context, best to spell that one out, or just substitute “terminal,” but I’ve definitely been in meetings where someone said something about a process that needs to be detached from the titty.
Google’s “inclusive documentation” guide highlights other… colorful choices… that emerge and proliferate on account of all computer-science experts being the same kind of complete dork. For example, variables names are alternating-caps or dash-separated instead of camel-case and kebab-case. Hierarchies should probably never have been called master versus slave. And there’s some debate for how to describe server-cluster recovery modes, but the answer is not “shoot the other node in the head.”
Software has more than its fair share of acronyms, which we often choose to say phonetically, like SQL gets said “sequel.” We also have the TTY, and you often have to detach things from it. Depending on the context, best to spell that one out, or just substitute “terminal,” but I’ve definitely been in meetings where someone said something about a process that needs to be detached from the titty.
Or the story of the guy talking in the airport about his BOM list.
Christmas break, I got some side-eye discussing a project from Intro to Engineering Design.
Google’s “inclusive documentation” guide highlights other… colorful choices… that emerge and proliferate on account of all computer-science experts being the same kind of complete dork. For example, variables names are alternating-caps or dash-separated instead of camel-case and kebab-case. Hierarchies should probably never have been called master versus slave. And there’s some debate for how to describe server-cluster recovery modes, but the answer is not “shoot the other node in the head.”