@mattpocockuk We’re also trying this. But we made a painful mistake(?) of trying to evolve the prototype to production instead of starting from scratch.
How do you move from prototype to production?
@BenjDicken@simeonGriggs RLS on Aurora was a nightmare for us. Query planner refused to use a lot of our indexing because of it. Only the most basic indexes work out of the box and beyond that it’s arcane knowledge.
@kenwheeler So.. socialism. Tax and divide wealth. But we’re all too worried about our own three cars, 7 flat screen tv’s. So we keep going for the bag.
Last quarter I rolled out Microsoft Copilot to 4,000 employees.
$30 per seat per month.
$1.4 million annually.
I called it "digital transformation."
The board loved that phrase.
They approved it in eleven minutes.
No one asked what it would actually do.
Including me.
I told everyone it would "10x productivity."
That's not a real number.
But it sounds like one.
HR asked how we'd measure the 10x.
I said we'd "leverage analytics dashboards."
They stopped asking.
Three months later I checked the usage reports.
47 people had opened it.
12 had used it more than once.
One of them was me.
I used it to summarize an email I could have read in 30 seconds.
It took 45 seconds.
Plus the time it took to fix the hallucinations.
But I called it a "pilot success."
Success means the pilot didn't visibly fail.
The CFO asked about ROI.
I showed him a graph.
The graph went up and to the right.
It measured "AI enablement."
I made that metric up.
He nodded approvingly.
We're "AI-enabled" now.
I don't know what that means.
But it's in our investor deck.
A senior developer asked why we didn't use Claude or ChatGPT.
I said we needed "enterprise-grade security."
He asked what that meant.
I said "compliance."
He asked which compliance.
I said "all of them."
He looked skeptical.
I scheduled him for a "career development conversation."
He stopped asking questions.
Microsoft sent a case study team.
They wanted to feature us as a success story.
I told them we "saved 40,000 hours."
I calculated that number by multiplying employees by a number I made up.
They didn't verify it.
They never do.
Now we're on Microsoft's website.
"Global enterprise achieves 40,000 hours of productivity gains with Copilot."
The CEO shared it on LinkedIn.
He got 3,000 likes.
He's never used Copilot.
None of the executives have.
We have an exemption.
"Strategic focus requires minimal digital distraction."
I wrote that policy.
The licenses renew next month.
I'm requesting an expansion.
5,000 more seats.
We haven't used the first 4,000.
But this time we'll "drive adoption."
Adoption means mandatory training.
Training means a 45-minute webinar no one watches.
But completion will be tracked.
Completion is a metric.
Metrics go in dashboards.
Dashboards go in board presentations.
Board presentations get me promoted.
I'll be SVP by Q3.
I still don't know what Copilot does.
But I know what it's for.
It's for showing we're "investing in AI."
Investment means spending.
Spending means commitment.
Commitment means we're serious about the future.
The future is whatever I say it is.
As long as the graph goes up and to the right.
This domain entity is most complex piece of business logic I've ever had to handle (subscriptions with configurable payment terms, renewal frequencies, benefits, grace periods etc) but re-modeling it from CRUD to a state-machine (actor) makes it 10000x easier to reason about
I’d advise to stay away from RLS unless you have PSQL experts in your team. We used RLS on aurora PSQL for 3 years. The query planner has a lot of trouble choosing the correct indexes. We wasted hours and hours trying to get it to use even the most straight forward indexes.
@RogerAlsing@gregyoung Can’t imagine that ever working out. I think McGregor is worth a lot more and his brand would be seriously damaged by losing to an influencer.
@mjblacker@sabine_s_@dillon_mulroy@teej_dv Despite slow compilation, it’s still super productive.. especially when dealing with large existing code bases. Being able to relatively safely move things around is $$$
@mjblacker@sabine_s_@dillon_mulroy@teej_dv Sure. But it trickles down to tooling as well. Open a couple of bigger files and intellisense starts lagging. Add in a little bit of dotnet watch and intellisense straight up freezes for long periods of time.
Picked up on some amazing community work to make rich diagnostics for #fsharp fsi/fsc reality:
https://t.co/bZIeQthRbV
Want to get it into main (flag is unlisted), so we can start playing with format, additional context, etc.