Dashboard requests
@AheadComputing used to take 3 months (2,160 hrs).
With Dives, they take about 1.5 hrs (0.002 months). That's a lot less!
AheadComputing is building a high-performance RISC-V CPU from scratch. Until recently, an engineer who needed a dashboard had to spec it, wait for the design enablement team to build it, review it, revise it, and wait again.
Now hardware engineers make their own Dives: interactive data apps they describe to Claude Code, built on their data in MotherDuck. The design enablement team liked the side effect: "We removed ourselves from being the bottleneck."
What else changed with Dives:
🦆 A Claude skill deploys each new Dive to the team's internal production site
🦆 One power engineer updates his Dives during meetings and has an updated dashboard within the hour
🦆 Dives of test run schedules and license usage exposed the bottlenecks that cut CI wait times from 8 hours to 1-2
🦆 Every Dive across every team is linked in one catalog and shared in weekly design reviews
But the big one was this:
"Every meeting now is shifted from trying to find answers to what to do about them."
Could be you: