Developer wrote a critical app and forgot where it ran - until it stopped running

Who, Me? With the weekend behind us, it's time to once again ask the question "Who, Me?" That's the name of The Register's Monday column in which we share reader-contributed confessions of making a mess with tech.

This week, meet a reader we'll Regomize as "Sam" who in the late 2000s built an application for his colleagues that he described as a "content migration toolset." The app was so good that customers started asking for it and Sam's employer decided to commercialize it.

To make that happen, Sam realized his employer would need a licensing system to check that every instance of the app had been paid for.

So he wrote one.

"Excited by the challenge, I spent a weekend researching asymmetric keys and built a licensing system that periodically checked in with the server, both on startup and at regular intervals," he told Who, Me?

The licensing server worked well. Sam told us fixing its occasional glitches didn't occupy much of his time.

Requests for new features required more intensive activity, and on one occasion Sam couldn't finish coding within office hours.

"Normally, I left my laptop at the office, but to make progress on the new feature I took it home for the weekend," he told Who, Me?

Sam thought he made fine progress over the weekend, but on Monday, his phone lit up - the licensing app was down, and nobody could log into the content migration toolset.

Customers were mad. Bosses were confused. Sam was in the spotlight.

"Instantly, I glanced down at the footwell of my car, where my laptop bag sat," Sam told Who, Me? "And that's when it hit me: the licensing server was still running on my laptop."

It was running there because, as he realized, "I had never transferred it to a production server. For years, it had been quietly running on my laptop, happily doing its job."

Suffice to say that when Sam arrived in the office, his first job was deploying the licensing app onto a proper server!

Have you run the right code in the wrong place? Click here to send us your story of misplaced workloads so we can deploy it in a future edition of Who, Me? ®