2.5 I want tech to be either mature enough or beneficial enough that I'm willing to deal with all the bugs AND specifically the very real possibility that the a

2.5 I want tech to be either mature enough or beneficial enough that I'm willing to deal with all the bugs AND specifically the very real possibility that the application may need to be rewritten to replace a bad tech bet. A good example was that around 2011 MongoDB was really taking off. HN routinely had articles about migrating to Mongo and how it was the new hotness. It turns out that MongoDB had a number of problems including dropping data regularly :/ Those of us that had to deal with debugging issues like that and potentially porting away from Mongo, are a bit gun-shy about adopting new databases, especially without the ability to call someone up and chat about what issues they encountered after running the tech on an application supporting a million users.