3 ms·

It's pretty common for Rails developers to know very little about databases (sql specifically). It's very frustrating because right out of the gate, Rails pushe

• sverhagen 3y ago
  My comment was based on Java environments, and it's the same. It's unacceptable to build poorly-designed schemas in any environment. But good schema design is something else than what I thought the article might have been referring to, which is building the entire business logic in SQL, using triggers and what not. I've seen enterprises with a database team doing that, for application layer people to come in and built their application on top of this "fait accompli" database. And this means you need two highly-skilled teams: the database and the application team. (Aside from a third, the infrastructure team.)
• treeman79 3y ago
  It’s common for JR developers fresh out of college or code camps. It’s also good reason not to let the ratio of Junior to seniors get too far out of whack. I’ve had several jobs now, where I came in to clean up after they hired a bunch of juniors with no experience. Usually they were quite good at making things pretty. But fundamentals like N+1, foreign key, insane / broken build times, desperation of concerns, etc abounded. It’s sort of nice because you come in and be a hero for fixing everything up. Can really sucks because there are often good reasons things got to be that bad.