Project note, August 2026: This post records the retirement of SoCalNomad’s automated X publisher.
The X publisher was not broken.
It had posted 99 times. The schedule worked, content moved through the API, and the account accumulated an orderly history of links.
It generated effectively no traffic for SoCalNomad. When the API credits ran out, buying more would have meant paying to preserve an automation whose only demonstrated output was its own activity.
So I disabled it.
Reliability Is Not Value
Automated systems encourage an operational definition of success:
- The job ran.
- The API returned success.
- The post appeared.
- The logs stayed clean.
Those checks matter, but they say nothing about why the job exists.
The publisher’s purpose was distribution. The relevant outcome was whether it attracted readers, created meaningful engagement, or supported a durable audience. Ninety-nine successful API calls did not establish that.
Sunk Automation Is Still A Sunk Cost
Once a workflow has code, credentials, schedules, monitoring, and documentation, turning it off can feel like wasting the investment.
Keeping it also has a cost. APIs change. Credentials expire. Error handling needs maintenance. Every active channel occupies attention during incidents and reviews.
Paying for additional credits would have converted a weak experiment into a recurring obligation.
Disabling the schedule preserved the implementation without continuing the expense. If the channel’s conditions or audience change, it can be reevaluated from evidence rather than rebuilt from scratch.
Compare Channels By Their Actual Job
Facebook was producing a meaningful share of referral traffic. Instagram had limited traffic but retained value as a visual brand surface. Email offered an owned retention channel, even though it still needed a real launch.
X had neither demonstrated traffic nor a distinct strategic role.
That comparison was more useful than asking whether an X presence is generally advisable. A channel belongs in this project only if it serves this project.
Deletion Was Not Required
Retiring automation does not have to mean erasing it.
The publisher remains part of the project history. Its schedule is disabled, and resources move to experiments with measurable potential.
Automation should make useful work cheaper. When it merely manufactures activity, stopping it is not failure. It is the final step of the experiment.