Does anyone else remember the days when "No one ever got fired for buying IBM" was true? You might pay a little extra, but it was never a total fail to use IBM products. I'm not sure when that changed, but I feel like these days, IBM is closer to Oracle than AWS.
A billion reasons never to buy IBM services
11–20 of 200 posts
Re: A billion reasons never to buy IBM services
#12Does anyone else remember the days when "No one ever got fired for buying IBM" was true? You might pay a little extra, but it was never a total fail to use IBM products. I'm not sure when that changed, but I feel like these days, IBM is closer to Oracle than AWS.
"No one ever got fired for buying IBM" because IBM was the safe, established choice. If you bought IBM and the project ended up failing, nobody would blame the failure on your decision, because buying IBM was what you were expected to do. If you bought from some other vendor and the project ended up failing, however, people would rush to claim that the failure was your fault for not doing the safe thing and buying IBM. In other words, you bought IBM to protect yourself from appearing to have taken a risk, not because you expected them to do a particularly good job.
If TFA is accurate, it would appear that "no one ever got fired for buying IBM" is as true today as it ever was. If the Canadian government had hired the Freshbooks guy to build their new payroll system, and the project had failed, the person who had made that decision would have had a whole lot of explaining to do. That person bought IBM, though, so everyone will just shrug their shoulders and assume the fault for the failure lies elsewhere.
Re: A billion reasons never to buy IBM services
#13Re: A billion reasons never to buy IBM services
#14Earlier quoted context omitted.
IBM has sold off most of their divisions - hardware to Lenovo, storage to Hitachi, etc. They no longer actually produce anything. So 'buying' IBM is no longer a real concept - they're pure consultants now, and consultants never 'sell' a product, just help you implement someone else's. A lovely legal distinction that they seem all too happy to abuse.
> They no longer actually produce anything This is not true. IBM produces a ton of software (spanning a range from terrible to excellent, quality-wise). This is where much of their profit comes from now. They still produce a bunch of hardware, mostly at the higher (and legacy) end.
Re: A billion reasons never to buy IBM services
#15Does anyone else remember the days when "No one ever got fired for buying IBM" was true? You might pay a little extra, but it was never a total fail to use IBM products. I'm not sure when that changed, but I feel like these days, IBM is closer to Oracle than AWS.
IBM has sold off most of their divisions - hardware to Lenovo, storage to Hitachi, etc. They no longer actually produce anything. So 'buying' IBM is no longer a real concept - they're pure consultants now, and consultants never 'sell' a product, just help you implement someone else's. A lovely legal distinction that they seem all too happy to abuse.
Re: A billion reasons never to buy IBM services
#16The article criticizes the quality of some Indian coders. Expect to be downvoted into oblivion.
Re: A billion reasons never to buy IBM services
#17Does anyone else remember the days when "No one ever got fired for buying IBM" was true? You might pay a little extra, but it was never a total fail to use IBM products. I'm not sure when that changed, but I feel like these days, IBM is closer to Oracle than AWS.
I never though of it that way but rather as a CYA move.
Re: A billion reasons never to buy IBM services
#18Seems like a baseless article that is pulling fake facts out of thin air to supplement a couple of real ones like the cost basis and failures of large government projects. It's not uncommon for large government projects to fail with all the bureaucracy and politics that is in play. I am not saying IBM is great, but this article is just not worth it.
I've used two services from IBM: Notes and node DB2 package. Both of them were pretty low quality, the db2 package was so unstable that it constantly segfaulted the entire node process. It's not fixed for years since the issue was reported with reproducible code. Needless to say I wouldn't recommend IBM even to my enemies. Can anyone share a good IBM experience? I'm honestly interested.
Re: A billion reasons never to buy IBM services
#19Does anyone else remember the days when "No one ever got fired for buying IBM" was true? You might pay a little extra, but it was never a total fail to use IBM products. I'm not sure when that changed, but I feel like these days, IBM is closer to Oracle than AWS.
Late 1980's. I was there, working for a skunkworks fragment in a Big Blue shoppe. To express doubt about IBM was to get no bonus. Then they started to haemorrhage cash to the tune of 5B$/quarter.
Really it's that Oracle is closer, these days, to what IBM was 30 years ago.
Re: A billion reasons never to buy IBM services
#20Seems like a baseless article that is pulling fake facts out of thin air to supplement a couple of real ones like the cost basis and failures of large government projects. It's not uncommon for large government projects to fail with all the bureaucracy and politics that is in play. I am not saying IBM is great, but this article is just not worth it.
I've used two services from IBM: Notes and node DB2 package. Both of them were pretty low quality, the db2 package was so unstable that it constantly segfaulted the entire node process. It's not fixed for years since the issue was reported with reproducible code. Needless to say I wouldn't recommend IBM even to my enemies. Can anyone share a good IBM experience? I'm honestly interested.