I think this is one of those things that’s situation dependent. It sounds to me like your organization has a lot of data that needs to be processed. In that cas

I think this is one of those things that’s situation dependent. It sounds to me like your organization has a lot of data that needs to be processed. In that case it’s extremely important to write your SQL so that it executes efficiently. SQL does a lot under the hood but it won’t automatically switch a left join to an inner join if it figures out that would have no impact on the output. So if you’re in a situation where that’s important, you’ll want your pipeline building employees to be using best practices. I run into a similar problem with my peers (data scientists) when I ask them to provide a SQL query link to their charts / analysis. It’s like pulling teeth but to me it seems obvious that everyone should be doing it as mistakes would be found sooner and others could build off of your work resulting in a positive feedback loop of data understanding. But nope, not everyone seems to care about that.