Aaron Muylaert retweeted
For the past two weeks I’ve been working on reducing memory usage in #fsharp compiler service that we use in @JetBrainsRider
The latest measurements look really good! 🎉
And since the improvements are in FCS itself, other tools will get them too
#fsharp 💪
Aaron Muylaert retweeted
I called a recommended electrician and he did not answer.
I called again the next day. He did not answer.
I mentioned this to the man who gave me the number, apologetically, assuming the man had died.
He said, "Oh yeah, he's terrible with the phone."
Then he said, "He's great though."
Terrible with the phone. Great though.
I asked how I am supposed to reach a man who does not answer his phone.
He said, "Just keep calling. He'll pick up eventually."
I called eleven times over six days. I left three messages of increasing formality. The third one was, I now realize, addressed to a dead man.
On day seven he answered and said, "Yeah?"
No apology. No acknowledgment of eleven calls. He answered as though we were mid-conversation.
I have since learned the rule, and the rule is upsetting.
The good ones do not answer.
The ones who answer immediately, who have a scheduling system, who send a confirmation text, who arrive in a branded vehicle within twenty-four hours, are the ones you should be afraid of.
Availability is the warning sign.
A man who can come tomorrow is a man with nothing to do tomorrow.
I said this out loud to an American and he nodded like I had recited scripture.
He said, "My guy took nine days to call me back. Best tile guy in the state."
Nine days. He said it with pride. He was bragging. He was bragging about being ignored.
I asked the electrician why he does not answer.
He said, "I'm in an attic."
That is the whole answer. He is in an attic. He is in an attic every day. The phone is in the truck and the truck is in the driveway and he is in the attic.
He said, "If I answered the phone I'd be a guy who answers phones."
He fixed my problem in thirty minutes and did not charge me for the trip.
I have his number. He will not answer it.
That is how I know it is a good number.
How long did your best guy take to call you back. Post the number of days. I want to see the correlation.
Looking again. Specifically hoping to find someone based in Belgium this time.
Cc @fsharpJobs
My remote (CET) team @ maecos.com is hiring a full stack #fsharp developer (#fsharp, #dotnet, #react, #postgresql, #fable). DM me for more information!
cc @fsharpJobs
Aaron Muylaert retweeted
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.
State machines are always the answer! 🚀
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.
Aaron Muylaert retweeted
Picked up on some amazing community work to make rich diagnostics for #fsharp fsi/fsc reality:
github.com/dotnet/fsharp/pul…
Want to get it into main (flag is unlisted), so we can start playing with format, additional context, etc.
Aaron Muylaert retweeted
F# support is getting better than ever.
F# needs more ❤️
Highlights of updates for #fsharp in Rider 2024.1:
- Generating overrides is now available in object expressions
- A new postfix template that creates instances of record types and object expressions for classes and interfaces.
- You can now see union cases when searching for union usages.
- Sticky lines support for F#, so seeing the context is now easier when working with longer types and functions.
Details: jetbrains.com/rider/whatsnew… #dotnet
Aaron Muylaert retweeted
New tale: talesfrom.dev/blog/fsm-funct… in which we explore functional state machines - we also measure how functional they are!
This is my tiny contribution to the great #fsharp #FsAdvent calendar by @sergey_tihon🔥
#csharp #SoftwareEngineering #SoftwareDevelopers #dotnet #DDDesign
Interesting idea to replace assertions with Verify. I wonder though, don't you quickly get in the situation where 10 verifications fail and the person responsible for the change has no idea what those 10 verifications were supposed to test? #fsharp #FsAdvent
My post for F# Advent, about testing derived state (such as with Event Sourcing) is up:
dev.to/larsfk/testing-a-deri…
#fsharp #FsAdvent
My remote (CET) team @ maecos.com is hiring a full stack #fsharp developer (#fsharp, #dotnet, #react, #postgresql, #fable). DM me for more information!
cc @fsharpJobs
The position is filled. I'm amazed by the amount of talented and experienced people in the #fsharp community. Incredible. Thank you all for retweeting and sharing! ♥️



























