4 ms·
I don’t need to have deep insights. Developers almost always have to justify why they pick certain technologies. And given how old MongoDB is not sure how it b
by threeseed 5y ago
I don’t need to have deep insights. Developers almost always have to justify why they pick certain technologies.
And given how old MongoDB is not sure how it benefits anyone’s resume.
- marginalia_nu 5y agoIf you don't understand their motivations, how can you claim to know their motivations?
- rmdashrfstar 5y agoWelcome to HN, where nothing makes sense and sources don’t matter
- halostatue 5y agoThere are thousands of projects where MongoDB was selected precisely because it was a new-shiny No SQL thingy. For some of these things, it may have been the right thing. For most of them, it was a chance to play with new technologies. I have seen multiple commercial projects where MongoDB was chosen by the developers with _no_ oversight by management (I have killed a couple of those projects, too, because MongoDB was always the wrong technology). The original comment about the number of projects where MongoDB was chosen under résumé-driven-development is absolutely correct. That doesn’t make it _bad_; how _else_ is one supposed to get experience with new technologies than to try something new? (Sticking with Mongo after multiple data-loss incidents due to the “architecture” of Mongo, on the other hand…)