I smoke test my APIs on every deploy — cheap insurance against “it built successfully” quietly meaning absolutely nothing about whether the thing actually works. If you're on Azure Web Apps or Functions, you've got deployment slots: push to a slot, poke it to make sure it&
When requesting an OAuth bearer token for machine-to-machine communication (usually to talk to an API), the lazy path is client credentials with just a client ID and secret. It works. It's also not great, security-wise — a static secret sitting in a config file is basically a Post-it note
Ever wondered if there's an “easy” way to test the signed-JWT-request flow? There is — if you're already handing OKTA or Auth0 a monthly invoice for the privilege. But what do you do when you're prototyping a POC at midnight, or your actual dev environment
The C4 model is a way of visualizing software architecture that doesn't require a whiteboard, three markers, and a passive-aggressive debate about whose box goes where. It's lightweight, it scales, and — unlike 90% of architecture diagrams I've been handed in my career — a human
In a previous post, I showed you how to stand up your own self-hosted UML editor. Congratulations, you now own the equivalent of a blank canvas and a box of crayons. This post is about not drawing like a caveman. Let's start with this painfully honest sequence diagram:
This one's going to be short — mostly because the answer to “how do I do this” is genuinely just a YAML file, not a whole architecture diagram. I get asked a fair amount how I publish my NuGet packages into GitHub Packages, so let's just show
If you've spent any time in software architecture, you already know the drill: someone asks for “just a quick diagram” and three hours later you're wrestling Visio stencils into submission like you're assembling IKEA furniture with instructions written in Elvish. Sequence diagrams, class diagrams,
Extract from a certificate the base64, JWK and private key
