this post was submitted on 13 Dec 2023
316 points (98.8% liked)
Technology
59440 readers
3612 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I get why enterprise likes VMWare but KVM isn’t harder to deal with. I’ve always worked at smaller companies so this isn’t an expert opinion. But I’ve always felt like at the infrastructure level, it ends up being cheaper to hire experts and run the open source solution (assuming it’s mature and at feature parity) than pay licensing and support fees.
An expert in one thing will usually add to your company in other ways too. Talent > “solutions” in the long run.
Let me tell you about a large bank and two data centers operated using VMware and the type of talent the bank is able to hire and retain. A move away from VMware is a 5-year project involving hiring, retraining, design mistakes, budget overruns, and a lot of grey hair. The year was 2012. 7 years later, one DC converted to OpenStack, the project is shelved and the majority of th OpenStack DC gets converted back to VMware due to "OpenStack disaster."
The fundamental problem I have identified over the years I worked adjacent to this project is this. Most folks above the manager position are not technical. They're typically some sort of BA. These kinds of folks do not easily comprehend the technical merits of different solutions. All sorts of errors stem from that. Errors in estimating risk, errors in estimating difficulty, but crucially errors in telling reality from fantasy, or truth from lies. Under this framework, the ability of the organization to hire technical people who know what they're doing is more or less based on luck. This particular org struck luck with some hires and didn't with most. So now we have a group of people who will build this thing, with only a few qualified people among the unqualified. Alright. A difficult design decision has to be made. There are two proposals. One from a qualified person. Another from an unqualified one. They're both presented to a director or a VP for a final decision. The qualified person presents their design, pros, cons, etc. The unqualified one does the same, except they have an ace up their sleeve - confident lies. So they sprinkle those all around their design - everything is amazing, few cons if any, unicorns shitting rainbows and the lot. The decision maker cannot discern the lies from the truth. The unicorn design feels irresistible. It's chosen. Its designer is promoted before its ill effects are ever realized. Now the competent folk don't even get to present alternatives to the VP level. Eventually they're tired of this shit and move to a place that is less corrupted.
This wasn't confined to one project and a single set of people. It's a general problem that transcends orgs and companies.