Because it's so big, there's a lot capable engineers, but also deadwood. I think Watson has attracted many capable devs. There's definitely too many execs flail

Because it's so big, there's a lot capable engineers, but also deadwood. I think Watson has attracted many capable devs. There's definitely too many execs flailing around with buzzwords. It's a great brand, it has potential. The problem is that a) it's being overhyped and b) yet again IBM doesn't understand that if you want it to be used for truly mind-blowing stuff, you have to make it easy for developers to use (or maybe they do, but suck at making it easy to use, see [1]). Then it generates its own, real hype. For an example of this, I'd say MQ vs MQTT/RabbitMQ, DB2 vs Postgres et al., NoSQL, analytics, Bluemix vs Amazon/GCE/Heroku, Softlayer vs Amazon/Google/Azure. I get that selling to traditional, conservative, and very rich/big firms is a viable strategy - but one that's failing for e.g. Bluemix, Softlayer. --- [1] The Google search results for "Watson API" suck. The documentation sounds like it was written for managers (" Representational State Transfer (REST) Application Programming Interface (API) "). Stop getting me to use Bluemix, Amazon/GCE/Heroku work better. Just look at this mess: https://www.ibm.com/smarterplanet/us/en/ibmwatson/developercloud/doc/getting_started/gs-full-nodejs.shtml https://www.ibm.com/smarterplanet/us/en/ibmwatson/developerc...