Tutorials

A video is a wall. You cannot skim it, search it, or tell from the thumbnail whether it is worth your afternoon. A companion post gives the episode a front door.

The recording is maybe a quarter of the work. The thing that holds the other three quarters together is one document per episode, built before I ever hit record.

The gap between what a roadmap says and what people think it says is where a lot of trouble starts. A roadmap is a statement of intent, not a contract.

Not a rigid form to fill in, but a shape I trust: a metadata block, a distribution block, and then the three parts of the writing that actually matter.

The difference between a deck sales uses in every deal and one that never gets opened is not design. It is whether you talked to sales before you built anything.

I used to have The Deck. You know the one. Sixty slides, everything the product could possibly do, updated in a panic the night before every meeting.

The sysadmin version of Model Context Protocol, without the hype: what it is, how it differs from an API call, and why the paranoid sysadmin instinct is exactly right here.

I wrote this deployment guide for CIQ, walking through how to get RLC Pro up and running on Google Cloud Marketplace from start to a live VM.

I wrote this deployment guide for CIQ covering how to get RLC Pro running on Microsoft Azure, from the Marketplace listing to a production-ready Enterprise Linux environment.

I wrote the launch post announcing the CIQ portal going live at portal.ciq.com, covering what it is, who it’s for, and how to go from registration to your first download in under a minute.

I wrote this guide for CIQ covering how to convert a running RHEL system to RLC Pro, without rebuilding servers or re-certifying your application stack.

As a long-time SysAdmin, one of the core tasks I’ve always had to tackle is managing users and groups on Linux systems. Whether you’re running a personal server or managing an entire fleet of Linux…