My software licensing job is actually a communications job.
What now? How can that be? Licensing is not the same thing as communicating!
It’s like this: I don’t deploy software myself. I work with people who deploy software. For them to deploy software correctly, they must know what “correctly” looks like.
For that to happen, I must effectively communicate both what “right” looks like and what can happen if not-“right” is done. The consequences can be pretty gnarly, about which I’ll say more in a future post.
To bring this closer to home for most people, I’ll draw on the world of Harry Potter. I think it’s safe to say billions of people in the world are more familiar with all things Potter than they are with any single thing software licensing (and the many possible catastrophes related).
If my job is to protect you from Voldemort and I can’t be with you at all times, I must let you know important facts about Voldemort. Given this objective, which facts are the important facts? Those fact’s that’ll best equip you to keep you away from direct encounter with Voldemort: Continue reading “Where Voldemort meets software licenses”