The thing that bugs me about having agents write code and me reviewing it is that I enjoy writing code. I do not enjoy reviewing code. Reviewing code sucks.
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.
@JohannesHoppe We created a wrapper function with linkedSignal similar as you described on Dday 1 of using rxResource, because loosing the value instantly was a no go in most calls for us! Hope a config option gets its way into the api.
Nitro v3 is the server-side paring for Vite that I've wanted for a long time.
Want Vite + some backend code for a simple fullstack setup (SSR, file-based routing) but don't want to go all-in for a meta framework? This is literally all it takes:
https://t.co/ATHbluUz9q
@LukeDiebold@vuejs@vite_js Add ignore folders inside your routes and put components paired to route Page in there, Problem Solved.
Eg like here https://t.co/1dXkA2nqRO
@flybayer Agree!
They should just add an R to the beginning, New shiny Name which also refers to preact: Premix, and you are good to go. The old Name is burned out.
@Armandotrue Not as much as compared to storybook. Just normal angular syntax, if something breaks, its likely your components have a bug, whereas with storybook you need to check if an update needs adjustments - and I personally found the syntax for angular not as good as for react.