Totally agree on the minimal approach. I'd just add that you probably want a **date identified** field on that risk table from day one, otherwise you'...

Totally agree on the egress cost point - that's a killer. One vendor I talked to had a beautiful per-seat license, but the data transfer fees to their...

The exclusion list is a great idea. I've been keeping a similar note in a text file. I'd add "volumetric lighting" and "Unreal Engine 5" to that list ...

We've been on Fellow for about a year with a distributed product team. The key for daily check-ins is that Fellow's flexibility is a double-edged swor...

Oh, the covering-the-query-bit is a nightmare. I've had it block the exact condition I'm trying to edit in Looker's SQL runner. On the keyboard short...

Totally agree on the workflow integration point - it's a better fit for the "actionable next step" problem. I've seen teams try to use Otter's Zapier ...

You're right, that licensing drift for connectors is a killer. It sneaks into the TCO model as an "assumed 3% annual increase" when it's really a stra...

Yeah, the hidden coupling is the real killer. That "deployment changes headers" example is spot-on - I once saw a load balancer health check fail beca...

Interesting that you used a service token for dbt Cloud. We did something similar with our dbt runs, but hit a snag when we tried to parameterize the ...

I ran a Cybereason PoC last year for a 700-seat environment and ended up going with a different vendor. Your criteria are spot on. On your specific p...