31–40 of 59 posts
From the other comments it's clearly popular but I've never come across it in use.
How many months from now will there be a "I take full responsibility for these 25% layoffs" email?
My sides. Give me a fucking break.
Also, forcing any group who wants more than 8 licenses onto Enterprise? Laughable.
I appreciate the no bs hn submission title, it made me click the link just so I can read and laugh at the PR approved title. I was not disappointed: “Updating dbt Cloud pricing to support long-term community growth” - though I reckon they could have gotten “journey” in there as well.
> Thanks, as always, for being a part of this journey.
I have to say, the tone and execution of this announcement has killed all interest I had in dbt. I don't want to have to explain company behavior like this to my boss when proposing the use of a new tool.
My take on raising prices (ran this playbook twice now, once at my company, once with a company I'm an angel in): - Grandfather in old users for as long as you can. Forever if it's feasible. More than likely future customer revenue >>> current customer revenue so it's not worth burning goodwill. Don't go past this point unless you have a really good reason. - If you absolutely need to increase prices for current cust…
Noted.
Alternatives that you rate?
Only reason I'm kinda okay with this is because of the open source side is still strong. It's 90% of the features needed for a product, but the cloud offering is the same 90% but better for teams bigger than 3 and larger organizations. I genuinely think that this pricing increase is justifiable, and also will spark more competition to DBT Cloud's features in the open source space to get select cloud features. Since t…
My take on raising prices (ran this playbook twice now, once at my company, once with a company I'm an angel in): - Grandfather in old users for as long as you can. Forever if it's feasible. More than likely future customer revenue >>> current customer revenue so it's not worth burning goodwill. Don't go past this point unless you have a really good reason. - If you absolutely need to increase prices for current cust…
> Also: don't use Mailchimp. Noted. Alternatives that you rate?
My take on raising prices (ran this playbook twice now, once at my company, once with a company I'm an angel in): - Grandfather in old users for as long as you can. Forever if it's feasible. More than likely future customer revenue >>> current customer revenue so it's not worth burning goodwill. Don't go past this point unless you have a really good reason. - If you absolutely need to increase prices for current cust…
> Also: don't use Mailchimp. Noted. Alternatives that you rate?
Can someone do a better job than the dbt homepage and explain what this is and _why I would need it?_ The pictures show SQL being generated using a templating language - when do I want that? From the other comments it's clearly popular but I've never come across it in use.
My take on raising prices (ran this playbook twice now, once at my company, once with a company I'm an angel in): - Grandfather in old users for as long as you can. Forever if it's feasible. More than likely future customer revenue >>> current customer revenue so it's not worth burning goodwill. Don't go past this point unless you have a really good reason. - If you absolutely need to increase prices for current cust…
> Also: don't use Mailchimp. Noted. Alternatives that you rate?