Write better SQL with a Style Guide | 3 Things to Consider

No developer actually enjoys creating documentation. We want to build things, not be part-time writers. But we also all have our own opinions and egos when it comes to best practices. We’ve all seen it happen at least once (or much more) in our career. A few members on the team get into an extended debate about how something should be done, or be written. I’m as guilty as anybody in this. And, sure, major decisions warrant this type of discussion. But constantly debating like this on minor decisions can become incredibly counterproductive. One of the best pieces of documentation you can create to avoid this is a simple style guide. This will help the team decide, and document, how things should be done. It can then be referenced to answer minor formatting questions without needing to ask others. So today I want to help you with this by sharing 3 of the most important things to include. This will be focused primarily on SQL, but can be applied to any language. Let’s dive in. Thank you for watching! New to data engineering? Check out some of my free Starter Guide PDFs - ▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬ 0:00 - Intro 0:35 - Naming Conventions 1:57 - Casing and Indentation 3:36 - Preferred Approaches ▬▬▬▬▬▬ Useful Links 🔗 ▬▬▬▬▬▬ ► ▬▬▬▬▬▬ Want to learn more? 📚 ▬▬▬▬▬▬ Data Engineering ► Data-Build-Tool (dbt) ► Snowflake ► GitHub ► ▬▬▬▬▬▬ Connect with me 🔄 ▬▬▬▬▬▬ Twitter ► Newsletter ► Website ► [video title] #kahandatasolutions #dataengineering #sql