Thank you. I'm going to screw up again at some point just hoping to get best practices for preventing it. I should have mentioned I work for a tiny startup that doesn't have someone competent to review the SQL.
I think that even if the other developers are not familiar with SQL specifically, you can show them the query you plan on running.
I׳ve found that the fact that you need to explain something to someone makes you double check everything, and reduces the chances of screwing up.
Even if they׳re not familiar with SQL, they can still easily understand the logic behind the query.
Comments
Thank you. I'm going to screw up again at some point just hoping to get best practices for preventing it. I should have mentioned I work for a tiny startup that doesn't have someone competent to review the SQL.
I think that even if the other developers are not familiar with SQL specifically, you can show them the query you plan on running.
I׳ve found that the fact that you need to explain something to someone makes you double check everything, and reduces the chances of screwing up. Even if they׳re not familiar with SQL, they can still easily understand the logic behind the query.
Yeah, that is a problem. Could you train up one of the cofounders slowly on the basics? I mean, someone needs to fix the database if you are ill...
Mistakes are kind of human nature though. I think a lot of 'best practice' is about trying to spot them before they cause a big problem.