# Why the Fishtown SQL style guide uses so many CTEs

**URL:** <https://discourse.getdbt.com/t/why-the-fishtown-sql-style-guide-uses-so-many-ctes/1091>\
**Category:** Archive\
**Created:** [April 27, 2020, 1:36pm UTC](https://discourse.getdbt.com/t/why-the-fishtown-sql-style-guide-uses-so-many-ctes/1091 "2020-04-27T13:36:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kyle\_r](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/kyle_r/32/378_2.png) [@kyle\_r](https://discourse.getdbt.com/u/kyle_r)\
**Post date:** [April 27, 2020, 11:59pm UTC](https://discourse.getdbt.com/t/why-the-fishtown-sql-style-guide-uses-so-many-ctes/1091/2 "2020-04-27T23:59:16Z")

</div>

Coming from a largely software development background, this was one of the first elements of the dbt style that resonated with me and made the overall framework more approachable. Tristan’s proof that the form (style) did not necessarily come at the sacrifice of function (performance) similarly resonated with me as an evaluator of this tool. Thanks for this/these posts Claire, et al!

---

_[View the full topic](https://discourse.getdbt.com/t/why-the-fishtown-sql-style-guide-uses-so-many-ctes/1091)._