Writing

I was recently setting up a new Windows machine for work - a desktop machine that actually has enough storage for me to run local SQL experimentation. I diligently followed the steps to create a bootable Windows 11 Enterprise USB, got the disks properly formatted, installed the OS, and tried to start customizing everything to my liking only to hit a brick wall.

If there would be some absurd world where I would be able to choose two pieces of the common vocabulary that should just vanish, it would be “just” and “works for me.” We, folks in tech, got way too comfortable throwing these around.

If product management was ever perfected and applied evenly to every single company and industry, we’d likely swim in products that solve all our problems. Unfortunately, good product management is unevenly distributed and often takes on patterns and practices that are very far from optimal.

I host media content related to this blog in an Azure Blob Storage account that is exposed publicly via a CDN. Here is how I manage the caching configuration.

I am ashamed to admit that for all the nerding out I am doing around Halo I did not know that there is a Halo Museum up until a few weeks ago.

I am a big believer in good documentation being an essential part of the product. Good docs are hard to come by for several reasons, not the least being the fact that writing good docs is hard.

I decided to host a static site on Azure App Service. I also decided that it would be nice if I could restrict who could access the site.

If you are building software on Azure, you’ve likely stumbled across the concept of managed identity. In layman’s terms, a managed identity is an automatically provisioned and managed identity resource that can be used to access other resources in Azure.

How to write API documentation that nobody can use, read, or use as reference.

Azure Active Directory (AAD) has a nifty feature that helps administrators keep tabs on the state of their tenant.