3 ms·
Until you've been burned by technology lock-in or know someone who has, it's hard to really wrap your head around it. It's a lot like all of those people who yo
by VengefulCynic 16y ago
Until you've been burned by technology lock-in or know someone who has, it's hard to really wrap your head around it. It's a lot like all of those people who you see interviewed after major disasters who say, "We didn't have insurance... we didn't think a [insert major disaster here] could happen here."
Honestly, that's the problem with explaining lock-in to many PHB-types: not only can they not conceive of what a disaster would look like, but they can't even imagine that one could happen in the first place.
- gaius 16y agoFortunately your PHB doesn't have to understand this - your auditors will understand it. This cuts both ways tho'. I've personally experienced being at a small company with a great product that a giant corporate customer loves - but their auditors have said, this company's this size, so you may only risk that many dollars business relying on their product.
- michaelbuckbee 16y agoBut wouldn't "open standards" help in that situation? You could tell the auditors: "Sure we're a small company, but if we fail it won't put your business at risk because you'd be be able to swap it out with anything else complying to XYZ standard."
- gaius 16y agoLOL! No, of course not! You can comply with whatever standards you like for data coming in and data going out but it's what you do with it in the middle that's what an application does. More to the world than webservers you know...