3 ms·

>Especially the "lazy" is very uncalled for in my opinion - there's just too much to learn, and too little time. How is that a valid justification for reinvent

>Especially the "lazy" is very uncalled for in my opinion - there's just too much to learn, and too little time. How is that a valid justification for reinventing the wheel, and poorly at that? In the end they're having to come around and learn SQL anyway, judging by all the Mongo hate and "why we switched to Postgres" posts I see here, so they gained nothing by avoiding it. >or even know where you're making the wrong choices. They could try actually listening to older developers for once and trusting established solutions like PostgreSQL instead of chasing after everything new and shinny that catches their eye.

Vinnl 10y ago
> How is that a valid justification for reinventing the wheel, and poorly at that? I'm not talking about the people reinventing the wheel, I'm talking about the people using the reinvented wheels and not realising that it's a reinvented wheel. > try actually listening to older developers This is harder than you make it sound. On the internet, it's hard to know who to listen to, and in real life, it can be hard to find older developers working on something relevant to you, and even then their skill levels differ. And then they should even want to bother with holding your hand while you're setting up your first database, making sure you don't botch up the performance by not doing things that come natural for someone who's been working with PostgreSQL for years and years.