[clawrencewenham]

Almost all of the software I've written is as useless outside of the company as air pockets taken out of a loaf of bread.

The big-rectangle diagram of what I do is fetch data from A, apply B(A), and send the result to Z. This is great when A is a proprietary API delivered over long-poll HTTP, B(A) converts it into a vocabulary common to just our products, and Z is Websockets to a mobile app. When we add a new customer who uses A2 all I do is write B2() and the rest stays the same.

Outside of the company, it's useless. There are thousands of products that do the same thing for different flavours of A, B and C. However, we can get our particular product to our target markets a year earlier than someone starting from scratch.

Compulsorily licensed to a competitor, they'd barely be able to install it because it's not packaged like a product. There's an old database that has evolved over more than a decade that's as crusty as an old fishing boat's keel. If a "good compulsory licensing scheme" would compensate the company for packaging it and writing manuals for it, then it's looking at millions of dollars just in the opportunity costs of taking the lead developers off other projects.

[de_watcher]

Wow, I actually have time to maintain that thing so it looks like any other program in some Linux distribution.

That way it's as boring as possible, which is good for the focus on the real function.