Skip to content

Dispatches

Namiko

In Remembrance

Namiko Akoi Miller
April 01, 1932–September 01, 1993

Reflection

Few things are as still as a South Georgia library in the dead of summer. The air inside is thick with the scent of old paper and the hum of a laboring compressor, while the dust drifts through shafts of light.

Namiko Akoi Miller was the steward of that stillness. As the librarian of Seminole County Public Library, she was a quiet mercy in a landscape that didn’t always know how to hold a gentle thing. To a child fleeing the white-hot sun or a restless home, she offered up worlds bound in glue and buckram. She would press her stamp to the page; a small ritual of safe passage.

The quiet didn't just end; it tore. I was a junior in high school when the town’s fragile veneer of safety was once again peeled back, exposing the old shadows underneath. We learned then what we’ve known ever since: you don't ever truly outrun the way violence hollows out a small place.

This song isn't about her murder. It's about the grace of a woman in a house of stories, and the way that grace continues to haunt the pine curtains and the red clay, long after the sanctuary was breached.

Lyrics

NAMIKO

A freight train’s echo, water tower in the air
Dust on the hardbacks, sunlight on the stairs
She knew every title and she knew every face
Keeping the peace in a small-town place

     Faded ink on the due dates, a pocket full of prayers
     A quiet kind of calling, an empty wooden chair

     And it ain’t the books that haunt that room at night
     It’s the lamp still burning in the borrowed light
     Where the stories always ended the way you hoped they would
     A chapter closed in Seminole like no one thought it could

Kids came in laughing, sun-drenched, summer-sweet
A note in the margins, a squeak in the seat
She’d say “Take your time,” ‘cause time was on our side
Now the doors lock early and the town stays inside

     Repeat Pre-chorus

     Repeat Chorus

There were ghosts in the aisles long before she was gone
Seeking shade from the heat of a red Georgia dawn.
She’d stamp the cards gently, she’d ask how you’ve been
A shelter from the weather and the trouble you're in

I won’t sing of shadow, I won’t sing of blood
I’ll sing her name like a hymn in the flood
I’ll sing the way she handed hope across a desk
The simple, honest kindness that we easily attest

No, it ain’t the books that haunt that room at night
It’s the love she left there in the borrowed light
Let the pages hold her, let the pine wind tell
Somebody keep the quiet, somebody keep it well

Writer: J. Ryan Johnson (BMI)
Copyright: © 2026 J. Ryan Johnson. All rights reserved.
Phone: +1 (407) 902-5419
Email: hello [at] tenthirtyam [dot] org

Audio Disclaimer

Lyrics: Original | Audio: AI-Generated

I am a songwriter and a musician, but I am not the voice meant to inhabit these verses.

I've used AI to bridge the gap for the concept demos, crafted to serve as blueprints that capture the genre, tone, and weary soul I hear for each song.

They exist as an invitation, offered in the hope that these lyrics will eventually reach the hands of an artist and storyteller who can bring them fully into the light.

Until then, they remain as they were born: quiet reflections on the grit and grace found just north of the county line.

Busy != Important

I am not naturally good at time management. I can make a list, rearrange the list, rewrite the list in a better app, and still end the day with the uncomfortable feeling that I mostly attended to noise. The inbox moved. The calendar happened. A dozen small things got handled. The important work, the thing I knew mattered before the day started, somehow survived untouched.

That is the trap. Busy feels defensible. Busy gives you evidence. Busy lets you point at a full calendar and say, "See, I did things."

But a full calendar is not the same as a useful day.

Randy Pausch, the Carnegie Mellon professor best known for The Last Lecture, gave a famous talk on time management that included his adaptation of the Eisenhower/Covey Matrix. The model is simple: sort work by two questions.

  • Is it important?
  • Is it urgent?

That gives you four buckets.

%%{init: {"theme": "base", "themeVariables": {"background": "transparent", "primaryTextColor": "var(--md-default-fg-color)", "secondaryTextColor": "var(--md-default-fg-color)", "tertiaryTextColor": "var(--md-default-fg-color)", "fontFamily": "Clarity City, sans-serif", "lineColor": "var(--md-default-fg-color--lighter)", "quadrant1Fill": "rgba(239, 68, 68, 0.18)", "quadrant1TextFill": "var(--md-default-fg-color)", "quadrant2Fill": "rgba(34, 197, 94, 0.18)", "quadrant2TextFill": "var(--md-default-fg-color)", "quadrant3Fill": "rgba(245, 158, 11, 0.18)", "quadrant3TextFill": "var(--md-default-fg-color)", "quadrant4Fill": "rgba(100, 116, 139, 0.18)", "quadrant4TextFill": "var(--md-default-fg-color)", "quadrantPointFill": "var(--md-accent-fg-color)", "quadrantPointTextFill": "var(--md-default-fg-color)", "quadrantXAxisTextFill": "var(--md-default-fg-color)", "quadrantYAxisTextFill": "var(--md-default-fg-color)", "quadrantInternalBorderStrokeFill": "var(--md-default-fg-color--lightest)", "quadrantExternalBorderStrokeFill": "var(--md-default-fg-color--lighter)", "quadrantTitleFill": "var(--md-default-fg-color)"}}}%%
quadrantChart
    title The Eisenhower/Covey Time Management Matrix
    x-axis Not Urgent --> Urgent
    y-axis Not Important --> Important
    quadrant-1 Do It Now
    quadrant-2 Schedule It
    quadrant-3 Delegate It
    quadrant-4 Do Not Do It
    "Crisis deadline": [0.86, 0.86]
    "Family emergency": [0.76, 0.78]
    "Weekly plan": [0.22, 0.86]
    "Exercise": [0.18, 0.72]
    "Skill practice": [0.34, 0.66]
    "FYI meeting": [0.74, 0.34]
    "Low-value ping": [0.84, 0.22]
    "Feed refresh loop": [0.18, 0.12]

Task: A Practical Guide to Cross-Platform Build Automation

Task

make is still one of the most useful tools in a developer's toolbox, but a lot of modern repositories need something more portable, more readable, and easier to share between local development and CI. Task is a fast, cross-platform task runner that keeps the good part of a Makefile, one command for common project workflows, while replacing the rough edges with a YAML-based Taskfile.yml, built-in dependency orchestration, variables, templating, caching, and first-class behavior on Windows, macOS, and Linux.

Field Dispatch: The First ESX Host Drifts from Custom Certificates After VMware Cloud Foundation 9 Instance Bring-Up

Effected Versions

  • VMware Cloud Foundation 9.1.x.x
  • VMware Cloud Foundation 9.0.x.x

If you're using securitySpec to deploy VMware Cloud Foundation 9.x with external CA-signed ESX certificates, the bring-up can look successful while still leaving you with one surprise:

Post Deployment Configuration Drift

The first ESX host will be deployed with a VMCA-signed certificate instead of the external CA-signed certificate provided.

I ran into this while testing external CA-signed certificates through both the API and Ansible. The JSON payload was accepted, the instance bring-up completed, the ESX hosts retained their external CA-signed certificates except for first ESX host, the one used during the bootstrap for the vCenter appliance.

Tip: Using the GitHub CLI to Copy Labels Between Repositories

Tip

If you manage multiple GitHub repositories and want consistent labels, drift happens quickly.

Use GitHub CLI to run gh label clone and copy a source repository's labels into a destination repository.

If gh is not installed yet, install it first:

brew install gh
sudo apt update && sudo apt install -y gh
# RHEL
sudo dnf install -y dnf-plugins-core
sudo dnf config-manager --add-repo https://cli.github.com/packages/rpm/gh-cli.repo
sudo dnf install -y gh

# Fedora
sudo dnf install -y gh
winget install GitHub.cli

Then authenticate:

gh auth login
gh auth status

That second command is worth running. It confirms that your session is active before you try to modify repository settings.

Clone Labels into the Current Repository

If you are already in the destination repository directory, the command is simple:

gh label clone OWNER/SOURCE-REPO

Example:

gh label clone tenthirtyam/example

That copies every label from tenthirtyam/example into the current repository.

Target a Different Destination Repository

If you are not inside the destination repository, use --repo:

gh label clone OWNER/SOURCE-REPO --repo OWNER/DESTINATION-REPO

Example:

gh label clone tenthirtyam/source-example --repo tenthirtyam/destination-example

What Randy Pausch's The Last Lecture Still Teaches Us Still

Some books comfort you. Others hold up a mirror.

The Last Lecture by Randy Pausch does a little of both.

Pausch was a computer science professor at Carnegie Mellon University. In 2006, he was diagnosed with pancreatic cancer. By September 18, 2007, after learning the cancer had returned and that he had only months left to live, he gave his now-famous lecture, "Really Achieving Your Childhood Dreams."

The talk became a book, but the real reason it endures is simpler than its title suggests:

It's not about dying. It's about how to live while you're still here.

That distinction matters. A lot of writing about mortality becomes soft around the edges. Pausch did something better. He stayed funny, practical, and honest about disappointment, work, family, and the ways adults drift from what once made them feel alive.

Today, him words feel especially clarifying because modern life is crowded with noise. We optimize calendars, answer messages at red lights, and confuse urgency with importance. We get very efficient at moving and very unclear about where we are going.

Pausch's voice cuts through that. He keeps asking a hard, useful question:

What would you do differently if you stopped pretending you had unlimited time?

Ubuntu 26.04: How to Upgrade from 24.04 LTS

Ubuntu 26.04 LTS Resolute Raccoon

Ubuntu 26.04 LTS, Resolute Raccoon, was officially released on April 23, 2026.

If you're like me and want to upgrade now, here's a clean step-by-step process to do it on both Ubuntu Desktop and Ubuntu Server.

Before the Upgrade

Before you begin the upgrade, review the following checklist.

  1. Back up anything you care about.
  2. If the system is a VM, take a snapshot.
  3. Make sure the current 24.04 LTS install is fully patched.
  4. Make sure you have enough free disk space.
  5. Be prepared to answer interactive prompts during the upgrade.

On Ubuntu Server, I would also review any third-party repositories or PPAs before you start. They are a common source of upgrade friction, and Ubuntu may disable them during the release upgrade anyway.

Update the current system first:

sudo apt update
sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=true
sudo reboot

EditorConfig Deep Dive: Syntax, Properties, and Best Practices

EditorConfig logo

Every shared repository eventually rediscovers the same avoidable argument: tabs or spaces, LF or CRLF, trim trailing whitespace or leave it alone, final newline or not. None of these questions are hard. They are just repetitive, noisy, and surprisingly good at wasting review time.

EditorConfig exists to move those decisions out of personal editor settings and into the repository itself. It is a simple, cross-editor standard for defining basic text file formatting rules so contributors using different editors and IDEs still save files in a consistent way.

This matters more than style bikeshedding. Inconsistent indentation creates ugly diffs. Inconsistent line endings break shell scripts and CI jobs. Trailing whitespace produces review noise that hides the change you actually care about. EditorConfig is not glamorous, but it solves a class of problems that should stay boring.

This guide covers how EditorConfig works, the syntax of .editorconfig files, the standard properties you can rely on, where editor support stands, and how to build a practical starter template for a modern repository.

Validity and Consequence

The porch light flickered in the stagnant heat.

"Well, that didn't feel a bit of good. What was you aimin' for with that?" I said, my skin prickling under the weight of her stare. "What were you aimin' for?"

I felt the hackles rise like a dog backed into a corner of the yard.

"Reckon you could find a different way to say your piece?" I stammered.

She spat into the dust, her eyes as cold and gray as a dry creek bed.

"Your feelin's are valid," she said, her voice a low rattle. "But your feelin's are your own, and I ain't sayin' they're wrong. Tho the way you went and acted on 'em sure is. Just 'cause you’re bleedin' don't give you the right to stain my floors."

The screen door slapped shut behind her.

Linux Kernel Sets Rules for AI-Generated Code

AI coding assistants were always going to force this conversation eventually. Tools like Copilot, ChatGPT, and Claude can draft code quickly, explain unfamiliar sections, and help contributors move through a patch faster than they could on their own. That is useful. It is also exactly the kind of shift that was bound to run into the Linux kernel's standards around trust, review, authorship, and licensing.

The kernel is not a project where code gets merged because it looks plausible. It is a project where contributors are expected to understand what they send, defend it under review, and stand behind it legally and technically. That is what makes the new guidance on AI-generated and tool-generated contributions worth paying attention to.