Bite me? It's 'byte', and that acronym is Binary Interface Transfer Code Handler

Beware the forgotten bit of test text lurking in the application

Who, Me? Surprise! It's Monday again! The weekend has evaporated once more, so pour a coffee, steal one of the expensive executive biscuits and tuck in for another tale of reader woe in The Register's Who, Me? feature.

Today's tale is a hybrid: part On Call and part Who, Me?. It is, however, 100 per cent "there but for the grace of God go I" for many a developer, this writer included.

"Paul" told us of his days working on a project that was running on an IBM System/36. A hefty beast compared to today's hardware, the machine succeeded IBM's System/34 and was usually programmed in IBM's legendary Report Program Generator (RPG) language. Launched in 1983, the machine lasted over 10 years before being succeeded by the AS/400.

The project, he explained, "was an automated process that would pop up screens and ask user[s] for input in order to continue." The process itself was already in place; Paul was just tweaking it for the customer's specific needs.

The help definitions were also there, "but I was trying to modify it just a little in order to add the bit of code I needed."

Sharks with frikkin lasers.

Dude, where's my laser?


Paul didn't need everything, just certain pieces. He created some extra test code for his validation library, declared the project complete and shunted it into production.

For the uninitiated, accessing help on the System/36 required the user to hit the F1 function key. Users were trained that if they were stuck, pressing the F1 key would show some text to tell them what to do next. Simple stuff.

Paul was at another client when the inevitable phone call came in.

"Paul, my computer just told me to Bite Me. I am not sure what I need to do."

"Bite you? What are you talking about?"

"I was running the new process, and it popped up the screen to enter the value, and I didn't know what I needed to enter, so I press the F1 key to get help, and I got a message that said 'Bite me Bitch!' I don't know what I am supposed to do."

There was a pause as Paul doubtless experienced the bowel-emptying sensation all too many developers have felt when a forgotten bit of test code comes back to, er, bite them.

After gathering his wits, he instructed the confused user to hold fire until he could "look at it," apologised to the client he was working at and raced over to the site.

It took half an hour to reach the unfortunate user, who had left the message shining brightly on the screen and was flummoxed as to what she had done to merit such ire. "I started looking at it," recalled Paul, "and it was 'Oops, my very bad'."

Paul's mistake was a simple one. He hadn't wanted to copy over all the old code and had inserted the "Bite me Bitch!" into the old template for the help text so he knew help was working in the old part. "Then when you get to the new part, my new help would pop up like it was supposed to."

His plan was that he would simply put the newly created code into production, where the old Help still lurked. So everything would work as it always had.

Alas, he confessed: "I had named my template for my test help the same as what was in production. I had inadvertently copied the template over to production when I installed it, and shame on me, didn't test the old Help function when I was done."

"I did test the new," he added. "It worked fine."

His bacon was, however, saved by a tape backup he'd taken before the "bite me" file had been inflicted on the customer's System/36.

We're sad to report that Paul did not come up with an excuse involving a tortured "Byte Imperative Transfer Exception Move Execution in the Bit Integer Throttle Channel Handle" backronym, but instead opted for the simple truth and confessed his misdeed. The user, he recalled, "wasn't too mad [and] we both laughed because the computer told her to bite me."

"I did have a conversation with her boss about using the word Bitch," he remembered, "but it was more, I shouldn't use that language."

We've all seen the odd bit of embarrassing debug code rear its ugly head in front of a user, right? No? Just us then? What excuse did you come up to justify the suddenly potty-mouthed behaviour of an otherwise innocent application? Confess all with an email to Who, Me? ®

Similar topics

Broader topics

Other stories you might like

  • An international incident or just some finger trouble at the console?
    All routers are equal, but some are more equal than others

    Who, Me? Welcome to an edition of Who, Me? where some configuration confusion left an entire nation cast adrift.

    Today's story is set in the early 2000s and comes from a reader Regomized as "Mikael" who was gainfully employed at a European ISP. The company had customers in multiple countries and Mikael's team was responsible for the international backbone.

    "Us senior network engineers were widely regarded as consummate professionals," he told us, before adding, "at least amongst ourselves."

    Continue reading
  • A discounting disaster averted at the expense of one's own employment
    I know what this process needs: Microsoft Access!

    Who, Me? A tale of discounts and process improvement via the magic of Excel, Access and a fair bit of electronic duct tape we imagine. Welcome to Who, Me?

    "James" is the Regomized reader of record today, and continues the theme of running the risk of doing a job just that little bit too well with an ancedote from the end of the last century involving his first job out of university, at a certain telecommunications giant.

    The job involved a process of calculating the discount received by big customers (the ones with multiple branches). "For the life of me I can't remember what the main DB was called," he told us, "but it was the old style green writing on a black screen that took forever to download the necessary data."

    Continue reading
  • In IT, no good deed ever goes unpunished
    When being helpful can mean being shown the door

    Who, Me? Going above and beyond in IT can sometimes lead to also going directly out of the door, as one Register reader found when discovering that sometimes efficiencies can be less than rewarding.

    A reader Regomised as "Will" told of us his days working at a now-defunct company that produced large telephone switches. In those days whenever a major software revision occurred, customers were expected to send in their configurations and Will's group would merge them into the latest and greatest. A new load would then be returned to the customers.

    It was not a fun process, not least because of constant hardware and software failures during the merge process. "When I first started, there was a constant grumble about how unreliable the machine used for the merging was," Will told us.

    Continue reading
  • An early crack at network management with an unfortunate logfile
    It's a backronym, right?

    Who, Me? Come with us on a journey back to the glory days of Visual Basic 6, misplaced enthusiasm and an unfortunate naming incident. Welcome to Who, Me?

    Today's tale comes from a reader Regomised as "Stephen", who was working in the IT department of a Royal Air Force base. "My duties were many," he told us, "from running daily backups of an ancient engineering system using (I kid you not) reel-to-reel tapes to swapping out misbehaving printers."

    This being the early 2000s, his boss loaded up our hero with more tasks. He could change printers and tapes, so Visual Basic (and its bedfellow, Access) should present no problem.

    Continue reading

Biting the hand that feeds IT © 1998–2022