Beware the beehive
I never did find out what the Beehive was, but it was somewhere and we had to write code as if it were going to run on the Beehive. Or at least take account of the Beehive's data protocols. You see, it was the 80s and a world famous chemical company had been in the process control automation business for decades. So many decades, in fact, that there was a machine colloquially known as the Beehive that dated from the 60s.
Never mind that there were systems that could run whole sections of chemical plants autonomously. There was still the Beehive, and there was Fortran IV, which was the language in vogue when the Beehive went into service. And which therefore was the language in which all work had to be done. Just for good measure, the programming rules said that each statement had to have its own label number whether it was the target of the dreaded GOTO or not. Earlier writers had helpfully left gaps in the numbering to allow statements to be inserted between, but of course those gaps were usually filled up by the time I fetched up there for the worst year of my career.
Did I mention that the developers there were among the least talented I have ever encountered? There were two gurus who weren't going to let new ideas get in the way of their retirement.
Oh well, they want editing, I'll give them editing. Delete 100 statements and replace them with the originals plus whatever I needed to add, all nicely renumbered. Make that 200 when necessary. This all had to be submitted as a "job" rather than done on the fly with an editor, as I was used to by then. That's their problem.
Turn the wheel the way it goes, only more so.