Hacker News Reader

My project has no ORM, and now that other developers are coming on it is hard to work with - the readability of an ORM far surpasses writing your own queries and I can see that the benefits far outweigh the cons.

And what's not to say you can't write your own lightweight ORM to abstract the database if you can't find a tool that suits your goals - and as always it all depends on your use case.

View on HN

Why is it not properly documented or are you not hiring developers with the right skills or providing training?

Instead of fizz buzz maybe testing basic SQL abilities in an interview would be better.

Even with documentation, it is a lot to consume - someone on the project for a longer time can get more done definitely, but bringing on more people will lead to wildly different quality control. I find it do be a scaling problem if anything.

Would not splitting responsibility for the Database to more senior developers work better.

Not sure what you mean by quality control you don't enforce any coding standards / style guides for writing SQL.

It does sound like your employer is cheeping out and not hiring enough experienced developers

Management is an issue unfortunately, we need a larger developer team, he wants more sales. Yeesh.

Reply on news.ycombinator.com