·5 min read
Why engineering dashboards don't change behavior
Every engineering team buys a dashboard. Almost nobody checks it after the first month. The problem isn't the data — it's that dashboards require you to go look at them.
things we think about while building Gary
Every engineering team buys a dashboard. Almost nobody checks it after the first month. The problem isn't the data — it's that dashboards require you to go look at them.
Most merge conflicts aren't caused by git complexity. They're caused by two engineers editing the same files without knowing about each other. By the time git tells you there's a conflict, both engineers have already done the work.
Teams that adopted AI coding agents aggressively are seeing a new pattern: PR volume spikes, review queues back up, and lead times end up worse than before. The bottleneck moved from writing code to reviewing it.