connormcarthur
If you have the resources to avoid putting business logic in the database, in a production app context, I'd avoid it if possible. It's just another thing tying you to that database, and if you ever decide to migrate, it's another hurdle preventing you from doing that.
> Would you believe that growth in January was two times as strong as in August?
I'm not sure I agree with the author's analysis here. "Quick Ratio" is an interesting metric, but a lot of companies would take the ~75k net MRR growth with more churn than ~25k with little churn in the short term. Despite that, it's an interesting measure to add to the toolkit.
I've always visualized MRR changes with the same stacked bar chart (New / Expansion / Churn / Contraction) with a line overlaid to visualize Net New MRR. That gives you an absolute sense of growth which is usually what you want from this kind of overview report.
Understanding Hash Joins in Redshift Query Plan
On Two Years of dbt
I'd imagine that 99% or more of that 400GB/day gets thrown away before ending up in Redshift.
What's new in dbt 0.9.0
From a learning standpoint: Clojure and other functional languages are worth using because they make you approach problems differently, and in doing so you become a better programmer.
Source: used Clojure in production building a real product for ~3 years