I tried to explain cryptocurrency to my uncle during the Christmas holiday and I gave him the wrong advice about gas fees. He followed my instructions and he moved a small amount of money and the network took half of it in a single transaction. He looked at the screen and he looked at me and the money was gone forever. I felt the heat in my face and I realized I had spoken with an authority I did not possess. I had made a mistake with a digital asset and there was no customer service desk to visit and there was no manager to call. The loss was absolute and the mistake belonged to me.

I work with wind turbines and I know the weight of physical things. I once ordered a pitch actuator for a GE turbine but the serial number was for a slightly older nacelle. I saw the part on the truck and I knew the mounting bolts would not line up. I called the supplier and they took the part back and they charged me a small fee for the shipping. The world stayed in its orbit and the turbine was fixed two days later. The mistake was corrected because physical goods exist in a world of gravity and logistics and human error is expected.

The Weight of Certainty

Software is not like a pitch actuator and it is not like a truck. Lucia sat in her office and the server room was humming through the wall. She had five hundred employees and many of them worked from home and many of them worked in the office. She looked at the licensing page and she saw the options for Remote Desktop Services. There were User CALs and there were Device CALs. She thought about the computers in the office and she thought about the laptops in the field. She chose the Device CALs and she paid the invoice and the keys arrived in her inbox.

She began the installation and she realized her mistake within the hour. Her users did not stay at one desk and they did not use one machine. A single technician might use a tablet in the field and a desktop in the shop and a laptop at home. Each device required its own license under the rules she had just purchased. If she had bought User CALs she would have been covered by a single license per person. She needed to change her order and she needed to do it before the 120-day grace period on the server expired.

She wrote an email to the support team and she explained the situation. She was honest and she was clear. She told them she had clicked the wrong button and she asked for an exchange. The reply came back and it was polite but it was final. The email said that digital deliveries are not eligible for return. The email said that once the key is sent the value is gone. The vendor kept her money and Lucia kept a set of licenses she could not use. The mistake stayed permanently her problem.

This is the central paradox of the digital economy and it is a trap for the unwary. When you buy a chair and the chair is too tall you send it back. When you buy a server license and the license is for the wrong version you are stuck with a ghost. The vendor has no cost of goods and the vendor has no inventory to manage but the vendor maintains a policy of absolute rigidity. They say the policy exists because a digital key cannot be “unseen” or “unreturned” and they claim the risk of piracy justifies the refusal of a refund.

The functional effect of this policy is that the vendor and the buyer have opposite interests at the moment of purchase. Lucia needed advice and she needed a guide but the vendor only needed the transaction to clear. If Lucia bought the wrong thing the vendor still got paid. If Lucia realized her mistake the vendor kept the money anyway. There is no incentive for the seller to prevent the buyer from making a costly error.

Isambard Kingdom Brunel and the Gauge War

This reminds me of the Great Western Railway in the nineteenth century. Isambard Kingdom Brunel was a brilliant engineer and he built a railroad with a gauge of seven feet. It was wide and it was stable and it allowed the trains to run at high speeds. But the rest of England used a gauge of four feet and eight and a half inches. Brunel was right about the physics but he was wrong about the network. For decades the Great Western Railway was an island of broad gauge in a sea of standard track.

When a train reached the end of the line the passengers had to get out and they had to walk to a different train. The freight had to be unloaded by hand and it had to be reloaded onto different cars. The cost of being wrong stayed with the company for nearly fifty years. They finally changed the tracks in 1892 and they did it over a single weekend with thousands of men and a massive amount of labor. They could not return the broad gauge and they could not exchange the engines. They lived with the mistake until the weight of it became unbearable.

The Calculation of Misery

Modern IT administrators are living through their own version of the gauge war every time they set up a Windows Server. They must choose between Windows Server 2019 and 2022 or the new 2025. They must calculate the number of users and they must count the number of devices. If they are running a medical clinic with three shifts of nurses using the same workstations they need Device CALs. If they are running a law firm where each partner has a phone and a laptop and a home PC they need User CALs.

The pressure is high and the documentation is often thick and the consequences of a wrong click are immediate. Most stores will sell you the key and then they will disappear into the shadows of the internet. They do not care if your terminal server is rejecting connections and they do not care if your procurement department is angry about the wasted budget. They have your money and you have a string of alphanumeric characters that do nothing for your infrastructure.

There is a different way to do business and it involves absorbing the risk on behalf of the customer. Most people find the RDS CAL Store because they are already in a state of panic. Their grace period is at 110 days and the red warnings are flashing on the dashboard. They need five User CALs or they need fifty Device CALs and they need them to work the first time.

By offering PayPal Buyer Protection and a clear return window the vendor aligns their interests with the buyer. They want you to buy the right thing because they do not want to process a refund. They become a partner instead of a predator.

I think about Lucia often when I am working on the turbines. I look at the vast expanse of the plains and I see the machines turning and I know that every part has a purpose. If a bolt is the wrong size we change the bolt. We do not tell the technician to keep the bolt and we do not tell them to buy a new turbine to fit the bolt. We fix the problem and we move on to the next one.

Software licensing is the only place where we accept the idea that a mistake is a life sentence. We have been trained to believe that digital goods are fragile and that once the “seal” is broken the value evaporates. This is a myth created by lawyers and it is sustained by companies that do not want to deal with the complexity of human service. A license key is just a permission slip and a permission slip can be revoked and it can be reissued.

The industry standard of “no returns” is not a technical necessity. It is an administrative choice. It is a choice to prioritize the ease of the seller over the success of the buyer. When we find a place that rejects this standard we are finding a place that treats software like the tool it is supposed to be. We are finding a place that recognizes that an IT administrator is a human being who is trying to keep a system alive under difficult conditions.

Beyond the Mistake

Lucia eventually had to buy the User CALs she needed. She had to explain to her boss why the first invoice was a total loss. She had to sit through a meeting where people who do not understand servers asked her why she was being careless. She was not being careless. She was navigating a system designed to punish any moment of hesitation. She was working in a world where being wrong is a permanent condition.

I told my uncle I would pay him back for the crypto mistake and I did. I sent him the money because I value the relationship more than I value being right. Vendors should do the same. They should value the long-term stability of the IT infrastructure they support. They should realize that a sysadmin who is helped out of a mistake today is a customer who will return for the next ten years.

“The wind keeps blowing and the turbines keep turning and the mistakes we make should be lessons and not anchors.”

We are building a digital world and we should build it with the same common sense we use in the physical one. We should be able to exchange the parts that do not fit. We should be able to admit when we have clicked the wrong button. And we should work with people who understand that the hum of the server room is a sound of progress and not just a sound of money being spent.

The next time I have to explain a complex system I will do it with more care and I will admit what I do not know. And the next time I see a “final sale” tag on a piece of essential infrastructure I will walk away and I will find someone who is willing to stand behind what they sell. Life is too short to carry the weight of a wrong license key and the world is too large to settle for a vendor who profits from your confusion.