Re:Redis 2.6 is near
by pork on Friday February 24, 2012 @03:05PM
(#3630765)
Seriously, neither can I, and you're right that it's a culture problem. I am genuinely trying to do my part to overcome that. Towards that, it would be nice to see more in-depth expositions of setups, and above all, an honest description of any issues and problems. I'm trying, antirez, I'm trying... :)
[ Parent
| on HN ]
One tried-and-true solution is to use it on "non-enterprise" projects (small, invisible, failure-tolerant) within your enterprise, then mention that you've used it, then use it on something slightly less obscure and mention it again ... worked for Linux in the '90's.
Re:Redis 2.6 is near
by thibaut_barrere on Friday February 24, 2012 @05:23PM
(#3631380)
What worked for me: I tried new things (ie: ruby, continuous integration, redis...) first on low-risk projects, then used that feedback as a self-proof (look! it works - maybe it can go a bit further?).
The other simple thing to point out is all of the issues with "enterprise" software you guys use. That label doesn't mean software doesn't have bugs. That being said...i agree with the others to use it on smaller projects (to get used to oddities with it, etc.) and to show the "higher ups" ... look..it's fine..we've been using it in X, Y, and Z for months. Also, I think it would become _more_ prevalent once a 10gen / datastax / percona like place pops up for it (so mgmt can put a checkbox next to "support")