4 ms·
"using a dedicated stack of hardware and software owned by one company" advantage - one throat to choke disadvantage - they've got you by the balls when it co
by neverartful 3y ago
"using a dedicated stack of hardware and software owned by one company"
advantage - one throat to choke
disadvantage - they've got you by the balls when it comes time to pay the licensing and maintenance fees
- Yasuraka 3y agoOne has to wonder if the most optimal throat-choking to ball-holding ratio can be modeled
- bob1029 3y agoI have a really hard time with the game theory around this. Every time I run the numbers, I arrive at: I would much rather be in a situation where I can place blame at the feet of one party, especially if they are under some contract to provide a certain level of service. There are things that I absolutely cannot control and I'd rather push as much of this as possible into one bucket. What I can control is how we actually use the technology relative to the business. If our sole vendor doubles the price on a certain service, then we will explore alternative services (within the same vendor) or ways to use that service less (maybe we send emails instead). I know the vendor is going to try to turn the economic screws. That I can work with. Business as usual. What I don't enjoy are those "unknown unknowns".