I just put the finishing touches on my new modern SQL style guide.
🔗 https://starlightinsights.com/starlight-data-framework/style-guide
> Modern, you say?
> Okay, great, I get that. But how do you achieve it?
The key steps are to follow a clear level of detail, split code into CTEs, and avoid macros.
Your feedback would be amazing! It's brand new, so it's still a bit rough around the edges, and I would love to improve it ❤️🎉
Yes, one of the main focuses has been to write code that is both human-readable and easy for large language models to analyze.
> But why is that important?
I just put the finishing touches on my new modern SQL style guide.
🔗 https://starlightinsights.com/starlight-data-framework/style-guide
> Modern, you say?
The Starlight Data Framework is a starting point for great data management. How do you define ownership in your data org? Suggestions & feedback are highly appreciated!
🔗 https://starlightinsights.com/starlight-data-framework/data-contracts
✅ Align business and technical definitions
✅ Start small—focus on source & model contracts first
✅ Assign both primary and backup owners
✅ Adapt and evolve contracts as your organization grows
💡 Your comment matters!
With Data Contracts, you can clearly define expectations, standardize definitions, and, most importantly, establish true ownership over your data.
📌 Key takeaways:
✅ Define ownership for each data component
✅ Document everything—clarity beats assumptions
TODAY, I’m open-sourcing the Starlight Data Warehouse Template—a complete CI/CD and Snowflake developer setup built for enterprise data warehouses.
And yes, it’s free to use—even for business use.
https://www.linkedin.com/feed/update/urn:li:activity:7290257691799695360/