My Life as a Human Patch Note

Notes, scales, an old hard drive, and a twelve-year-old’s handwriting.

Prologue: Version 41.7.3

At 4:13 in the morning, the house is pitch black, and the only light in the room is the cool blue glow of a television screen hum-singing some low, uncritical background noise in the corner. I walk through the quiet darkness to my desk and lift the lid of my MacBook. The screen wakes against the room.. Beside the keyboard sits a glass of cold brew coffee—always cold, always the same flat bitter bite that I rely on to wake up the corners of my brain.
Before my hands touch the keys, I perform a small, silent ritual: I take off my Apple Watch and slide it onto its magnetic puck on the charger. It joins a neat, white row of cables feeding the phone, the laptop, and the AirPods—a little digital clinic designed to keep every peripheral fully charged and operational before the day can start.
On the screen, a file is already open: PerfectNotes2026v3.25_RD3.
The mechanical keyboard is cold under my fingers. As the cursor blinks in the blank space beneath the title, I feel a sudden, familiar rush of hope and excitement. This is it, I think. This is the morning I dig in. This is where I finally get it going.
Then, within ninety seconds, the wall hits. The excitement curdles into a heavy, cold weight of overwhelm. There are too many branches, too many files, too much noise. And so, instead of writing a single sentence of prose, I do what I have trained myself to do across forty years of navigating systems: I close the document, open my master outline, and slip quietly into planning.
I begin renaming files. I redesign the folder hierarchy. I adjust the tags. I write elaborate notes about how I will organize my writing once the writing actually begins. I am preparing a perfect, frictionless runway for work I keep postponing.

Version 41.7.3
[+] Added NetNewsWire support.
[+] Consolidated notes into primary OneNote vault.
[+] Improved morning movement consistency.
[-] Known issue: User continues rebuilding the writing system instead of using it.

I. The Update That Worked

I did not begin this because I was vain, or because I was obsessed with gadgets, or because I was naive. I began because it worked.
Six years ago, my operating weight was over 320 pounds. My body felt like a heavy, broken machine that I was forced to carry through the world, its gears grinding, its exhaust hot. I didn’t know how to fix it until I stopped treating health as a moral evaluation of my character and started treating it as an engineering problem.
I learned the math. I got a food scale and started weighing every gram of oats, every ounce of chicken. I tracked my calories, my macro ratios, my resting heart rate, and my daily steps. I walked. I walked up the steep, gravel-ditch line of my neighborhood hill in the freezing March rain, slipping Slipknot into my ears and pushing my heart rate against the thresholds my phone had drawn for me.
And over time, the system responded with a clarity that felt almost mechanical. The weight came off— pounds of it, leaving an absence of paperwork where a lifetime of physical anxiety had been. I could walk down stairs without my knees giving an opinion. I could buy clothes off the rack.
For the first time in my life, becoming a different person did not feel like a spiritual mystery. It felt programmable.
My mistake was not discovering that systems could change my body. My mistake was deciding that because my body could be debugged, everything else must be a system too.

Version 35.0 — Performance Update
[+] Reduced total operating weight.
[+] Improved cardiovascular performance.
[+] Added support for early-morning movement.
[-] Known issue: User now suspects every human difficulty can be solved with sufficient tracking.

II. The Changelog Self

Once you accept the premise that you are configurable, the language of the machine escapes its containment. It crawls off the scale and onto your desk, into your kitchen, and into the way you talk to your children.
I stopped being tired and started having a “sleep-protocol problem”. I stopped procrastinating and started having a “workflow-friction problem”. I stopped forgetting what I read and started suffering from an “information-retrieval problem”. Ordinary, ancient human weaknesses sounded much more encouraging once I gave them enterprise software names.
This is how you become a Changelog Self.
The Changelog Self does not ask, “Who am I?” He asks, “What has been improved since the previous version?”. He experiences identity not as a continuous history of lived years, but as a series of software updates, each one designed to deprecate the embarrassing prototype that came before it.
This model of existence is comforting because software does not have character flaws; it only has known issues. If Monday was a disaster, you don’t have to carry the shame of it; you simply release a new build on Tuesday morning.
But the logic carries a silent, devastating tax: A bug is not allowed to remain.
To justify the constant labor of the update, you must continuously find the current version of yourself inadequate. You begin to view your present self not as a person who is currently living, but as a temporary, defective draft—a placeholder waiting for the upgrade that will finally make you operational.

III. The Paragraph Logistics Company

The centerpiece of my optimization career was my reading system.
I had a simple human desire: I wanted to read useful things, and I wanted to remember some of them so I could use them in my writing. That was the goal. But a goal without a system is an insult, so I built one.
I replaced the infinite algorithmic feed of social media with NetNewsWire, subscribing directly to sixty hand-chosen RSS feeds. It was beautiful. On the first day, the count went to zero, and I closed my laptop with a clean, specific sense of completion.
But then I realized that reaching zero didn’t mean I had learned anything. I had merely sorted the mail. So I connected NetNewsWire to Instapaper. The feeds emptied, but the read-it-later archive grew. Instapaper became a digital cemetery, containing 342 unread articles, including a twelve-year-old dead workaround for running Adobe Flash on an iPhone 4.
To solve the cemetery problem, I built a knowledge-ingestion pipeline. I migrated my notes from Google Docs into OneNote. I set up folders using the PARA method. I designed a spaced-retrieval curriculum, mapped out Cornell notes on wide-ruled paper, and constructed an enormous, elegant mindmap linking every concept I had ever encountered. I rebuilt that mindmap from scratch five times. I named every document with clinical precision: 08.20.2026 – article.
One evening, I sat back and looked at the screen. To read a single three-thousand-word essay, the text had to enter through an RSS reader, pass into a read-later queue, be highlighted, extracted by an AI concept-summary prompt, deposited into a staging folder, sorted into OneNote, and scheduled for a weekly review.
I wanted to remember what I read. Six systems later, I had accidentally founded a small logistics company for paragraphs. I had transformed an intimate encounter between a man and a sentence into a multi-stage industrial process.

Version 38.6 — Learning Infrastructure
[+] Added NetNewsWire article capture.
[+] Migrated notes to OneNote database.
[+] Created index cards and mindmap for spaced-retrieval practice.
[-] Known issue: Categorized information remains entirely unused.

IV. Human Feature Creep

In software, Feature Creep occurs when a product accumulates so many helpful capabilities that its original, simple purpose becomes impossible to perform.
Humans do this too. We call it personal development, but very quickly it turns into personal administration.
I wanted to become a writer. To support that desire, I built a story bible, an editorial lexicon, a pitch tracker, a concept library, an automated drafting template, and an AI-assisted outline evaluation tool. None of these were silly. Each was a highly intelligent, thoughtful system designed to solve a specific creative friction.
But together, they created an administrative nightmare. I had designed a creative system so sophisticated that creativity could no longer enter the room without completing several forms first.
I wanted to write. Instead, I had become the unpaid director of operations for a writer who had not yet arrived. My life had become one of those vintage television remotes with sixty-seven rubber buttons, only three of which did anything I actually understood.
Every new feature promised to make me more capable. Instead, every new feature created maintenance. The OneNote files had to be audited. The highlight queue had to be cleared. The step-streak had to be protected. The database had to be migrated to the next, better tool.
At some point, I stopped having a life and became its full-time, unpaid system administrator.

Version 39.4 — Expanded Functionality
[+] Installed second brain for long-term project management.
[+] Added daily review protocol for tracking second-brain adherence.
[+] Created three separate reference documents explaining the review protocol.
[-] Known issue: User spends more time managing the ledger than writing the essays.

V. Regression Detected

A software regression occurs when an update fixes one bug but quietly breaks a feature that previously worked.
Last month, I pulled an old plastic storage bin out of my hallway closet. Inside were eleven external hard drives—the cold, gray skeletons of my previous digital lives. Most of them were dead; they clicked and whirred, spinning up and stopping like old hearts failing.
But the eighth drive mounted. I sat there on the kitchen floor with my back against the dishwasher, the metal drive warming up in my palm, and found a folder called READING from 2013.
Inside was an outline for a self-study course on reading comprehension and spaced retrieval. It had seven modules. As I read through them, my stomach did a cold, slow turn: they were the exact same seven modules I had spent three weekends designing last winter.
Then I found another version from 2023.
Module three in that one was called Retrieval Practice. In 2013, I had called it Teach It Back Cold.
Three different builds of the same system, thirteen years apart. I had not built it three times because I was refining it; I had built it three times because I had put the first two in cold storage and forgotten they lived. I had spent thirteen years designing a machine for holding onto things, and the machine could not survive its own subject matter.
But that wasn’t the detail that made the document hard to look at.
In the second paragraph, written in the hopeful, confident present tense of a twenty-nine-year-old, was a sentence explaining that I was building this curriculum “for my kids.”
I was twenty-nine. I was single. I lived in an apartment with a desk in the corner of the living room with no children in sight. I was designing elaborate cognitive retrieval systems for people who did not exist yet, so that when they did arrive, I would be ready.
I had spent my entire life preparing.
I kept calling myself a work in progress because unfinished things cannot be judged. A product in “perpetual beta” cannot fail, because any unrealized ambition can always be blamed on the build. It is procrastination with a venture-capital vocabulary. I was extraordinarily good at preparing better versions of my life, and strangely terrified to inhabit the one already running.

VI. The Walk as a Dashboard

Even the most beautiful, life-saving habits can be ruined by this diagnostic reflex.
Walking saved my life. But once my phone and watch got hold of the practice, they turned movement into a real-time performance dashboard.
Steps. Rings. Streaks. Awards. An ordinary walk acquired a pass/fail state.
So I found myself performing some truly absurd behaviors. I would walk on my lunch break, walk after work, and then—at 11:00 PM—find myself circling the kitchen island in rubber flip-flops, my heel clicking like a sewing machine against the tile, because some number or ring was still unfinished.
The absurd part was not that the measurements were useless. They had helped me change my life. The absurd part was how quickly a useful measurement could become a verdict.
Ten thousand steps itself was never a biological threshold. The number was popularized in the 1960s by a Japanese pedometer marketed as the manpo-kei—the “10,000-step meter.” It was a memorable benchmark before it was a scientific one.
And there I was, walking circles through my own dark house, ignoring the actual life around me, trying to satisfy a number I had mistaken for nature.

VII. Planned Obsolescence

Every exciting future version of your life requires an inadequate current version to justify the update.
To sustain the fantasy of the next launch, you must treat your present self with a cold, relentless contempt. The old you is embarrassing; the current you is a temporary inconvenience; the future you receives all your respect, all your savings, and all your tenderness.
I had spent decades showing an extraordinary loyalty to my future self, and absolutely no gentleness toward the man required to build him.
The heavier version of me was the one who had the courage to step out of the house in flip-flops and walk those first painful two hundred feet. The confused version was the one who kept reading and copying code onto wide-ruled paper. The disorganized version was the one who kept raising kids, working the night shifts, and keeping the kitchen clean.
They were not defective prototypes. They were the developers. And I had treated them like obsolete software because they weren’t perfect.

VIII. The Version Number Is a Clock

The humor of “Version 41.0” evaporates when you look at the schedule.
A software company can release three hundred builds in a season. A human being receives exactly one numbered update per year, and the release schedule is completely nonnegotiable.
At forty-one, the years contained inside my project folders are not metadata. They are the only life I am going to get.
This weekend, my daughter Summer and I are sitting at the kitchen table working on her cookbook. She is twelve. Her handwriting on the paper is incredible—jagged, creative, decorated with colored markers and stickers.
My contribution is, predictably, a mess of un-optimized files. My recipes are scattered across four different notes in my phone, written in the precise, clinical language of a chemist: everything weighed to the single gram on a digital scale.
“Can you just tell me how much a teaspoon is?” she asks.
And so, I sit there and translate. I translate my hyper-optimized gram weights into messy, ordinary tablespoons so she can cook these things at a friend’s house without needing a laboratory scale. I have to fight the diagnostic reflex that wants to explain why the gram weight is the only true way to bake.
Her version of the cookbook will be full of pictures, collages, and recipes that use “more cheese and more cinnamon” than any system would ever recommend. It is completely un-optimized, and it is the only version of family history that will survive the transition from my hands to hers.
I had spent years waiting to finish my perfect, digital recipe archive before starting the cookbook, because I wanted to be “ready”.
But Summer did not need the final, optimized version of me. She needed access to the current one. Children do not experience their parents as works in progress; they experience whichever version shows up to the table. Other people cannot postpone their relationships with us until we are out of beta.

Epilogue: Long-Term Support

I am not going to delete my apps. I am not going to throw away my computer, move into the woods, or declare a new, minimalist era of “authentic unplugged living.” That would simply be Version 42.0—another dramatic update designed to replace the man I was yesterday.
I still like systems. I still walk, I still use NetNewsWire, and I still take notes at four in the morning.
But the purpose of the work has shifted.
In software, Long-Term Support (LTS) is reserved for builds that are stable, reliable, and trusted. They do not receive new, flashing features. They are maintained, protected, and supported because people depend on them to do real work every single day.
That is the arrangement. I am no longer trying to release a version of myself worth becoming. I am simply trying to take care of the one my children already know.

Version 42.0 — Long-Term Support
[+] Continued support for existing interests.
[+] Reduced unnecessary system migrations.
[+] Improved compatibility with unfinished work.
[+] Removed requirement that every activity produce measurable improvement.
[-] Known issues remain. Known issues no longer prevent normal operation.
[-] No major redesign currently planned.

For the first time, the current version will remain supported.