Husband to Lindsey, Dad to Max, Declan, and Aubrey, and owner of JasperFx Software (https://jasperfx.net). I take pull requests. Go Chiefs!
I occasionally blog at https://jeremydmiller.com.

@jeremydmiller.bsky.social
Husband to Lindsey, Dad to Max, Declan, and Aubrey, and owner of JasperFx Software (https://jasperfx.net). I take pull requests. Go Chiefs!
I occasionally blog at https://jeremydmiller.com.
Some of it is because of bye weeks, but my son & I's fantasy team hit 215 points last week (~140 is usually good enough to win) and we're going to struggle to hit 100 this week.
Repeat. No project -- or even just a subsystem that gets thrown away immediately -- is a complete failure if you learn something that helps a later effort succeed
And after Willie endorses Talarico, the inevitable backlash from Texas conservatives who are perpetually surprised to find out Willie is.
Words to live by from Bruce Robison:
Listening to a channel of covers today just for fun, and I'll make this one the #SongOfTheDay:
And nothing else has
Wolverine's "transactional middleware" for Marten/Polecat/EF Core et al is also tied into the tenant id detection at both the message handler and HTTP/gRPC boundaries so your application code "just works". We're the only tool that does anything like that.
And Wolverine and the rest of the Critter Stack can even do schema initialization for you across tenant databases. And nobody else can do the IoT friendly broker per tenant thing Wolverine has. Weirdly, nobody else does the 1st class tenant id tracking. No idea why.
Wolverine is really the only tool that has any significant multi-tenancy support to speak of. NServiceBus does a *little*, but you have to piece together a *lot* of the end to end scenarios that Wolverine does out of the box. So, almost everything in that article is unique to Wolverine.
Working at a StarBucks and telling myself I'll head home after the next song and it turned out to be American Pie. I might be here the rest of the day.
As a long time Chiefs fan I'm feeling some déjà vu. I'm a little worried about K9 getting worn down from overuse the same way I was about Priest Holmes 20 years ago and having to care a little bit about awful off field stories about Tyreek
My Mom likes these guys, and I've got a soft spot for this kind of 70's stuff.
The easy stuff is easy, then you get a world of edge cases from Kubernetes behavior or network hiccups or database maintenance doing weird things to PostgreSQL sequences if you're not careful. You want to use something that's hardened through real system usage and continuously curated
One thing I told them afterward about how AI has sped up everything. Last December I was having fun comparing every issue or pull request number to what was happening in history that year (1700s - 2000). Wolverine will flip into the 5000's soon. Yikes.
I got to be on DotNetRocks this week talking the Critter Stack, Event Sourcing, inevitably AI, and a little bit of a get off my rant about today's content creators:
They're so much faster than they used to be!
I'll happily argue that Wolverine has the strongest support for multi-tenancy out of all the .NET messaging tools:
Writing a blog post and making yet another link to a pattern in the EIP book. For my writing career I've referred more to Martin Fowler posts, the EIP book, and the original C2 Wiki more than any other resources
That's already out?
Yet another Wolverine release, some themes:
* Wolverine has a vibrant community
* AOT compliance is a slog
* You can't just vibe code something like Wolverine, it's all vision first, but then constant feedback, adaptation, and curation over time
From yesterday: