Error handling, cont. Errors generally have four causes:
1. Fatal errors (memory, fascist takeover). Can't be managed, best just to log and crash.
2. Dev error. Should be caught in unit tests. See above.
3. Poor API design. Wrap in an adaptor at the point of call.
4. External sources. See above.

It's interesting trying to teach a subject you know really well - you still end up learning things. I recently taught a small class on software design, and it really affected the way I develop. Case in point, I've mostly stopped catching errors in business logic.

I guess we're calling them "fascist units" from now on. #metric

I want to share my experience today with Google support, trying to get Gemini (their AI/plagiarism machine) turned off in my Google workspace account. That account is where I personally do all my work communication—I am an editor, and most of my work contracts explicitly ban any use of Generative AI

We should start calling 45 and his munchkins DEI hires since the only reason they got the job was because of their ethnicity and gender.

Finished getting my certification in "Cybersecurity" yesterday. Unless I'm missing something, that's my first official diploma. The value of this is a little nebulous, but I did not have to pay for it.

What's the role of Services in Vertical Slice Architecture and how do they differ from domain rules?

Keeping the holiday traditions alive as an expat comes with its own challenges. At least the kids are interested in my weird cultural quirks.

Today's architecture insight was how to replace a legacy, stateful messaging service that relies on locks and external storage with one that is active-active and instead shares data needed for sync through a topic broadcast. Won't fit in a single post though.

Following my testing with MinimalAPI, I'm still not fond of static methods. It also lacks support for model binding with XML or even Newtonsoft.Json. In the end I was able to convert the existing app to Vertical slices but the end result isn't that pretty.

My current research topic is .net Minimal APIs. Unlike the old-school controllers, this approach uses static (class) methods or lambdas, reducing the need for heap-allocation. The downside is that dependencies and endpoint parameters are jumbled together, leading to reduced readability.

Having a snow weekend with the kids, making cunning plans to surprise eldest sprog with her own Steam account come bday so we can play co-op Valheim.

Hallo Bluesky. I was never a Twitter user but we'll see if this platform works for my social media "needs".