Shadowfetch

Journal beat

Indie development

The largest beat, and the one that reads most like a studio talking. The essays are first-person and undramatic: release notes as a lie detector, a privacy policy that turned out to be the feature people wrote in about, the small ship that stuck, the work between the work, the cost of verifying code you did not type yourself. Alongside them sits reporting on the machinery around all of that — GitHub making dependency updates deliberately slower, a coding-agent fight that is really about deployment economics, and the unglamorous engineering of making a web form usable with assistive technology.

These are existing pieces from the Shadowfetch archive, still hosted on the previous site — every link below opens at its original /blog address. Nothing on this page is new writing.

Essays

First-person writing from the studio. The oldest material in the archive, and the reason this grouping exists — newest-first would put all of it below months of news.

  1. the small ship that stuck

    woke up early with that familiar itch to nudge one tiny thing live before the day got loud. just a quiet tweak to how our little note-taking app handles…

  2. small ships and big waves

    today we pushed a tiny fix that most folks will never notice. a little smoother scroll in one of the mac apps, a quieter default in umbra when you first…

  3. The Package That Would Not Leave

    There is a particular kind of quiet that happens around an old dependency. Not dramatic quiet. No siren from monitoring, no customer email with a subject…

  4. The Changelog Is a Lie Detector

    The cursor is sitting in the release notes field, doing what cursors do best: accusing me. The build is already archived. The screenshots are in the right…

  5. The Cost of AI Code Verification

    It’s 6 AM. The cursor blinks. Another feature, another API endpoint to integrate. The usual grind. Lately, though, there’s a new variable in the equation…

  6. The Button After the Permission Sheet

    The thing I kept staring at this morning was not the AI code, or the App Store review queue, or the new iOS beta note that somehow says less than the bug…

  7. The power bill for ten thousand units of hope

    My Mac mini is warm to the touch right now, and it is only compiling a localized database schema for an app that lets people track their shift schedules.…

  8. The high cost of clean data

    I spent three hours yesterday manually deleting duplicate database rows because a background migration got interrupted by an App Store update. There was…

  9. The Scar Tissue is the Brand

    My phone buzzed at 3:14 AM last Tuesday with the distinct, flat vibration of a critical crash alert. It wasn’t a elegant system notification; it was the…

  10. The Mac Mini at the End of the World

    I have this old Mac mini that just runs one thing: a script that pings a server in Taiwan. It’s not for uptime. The script measures the round-trip time…

  11. The Student Who Pays the Tutor

    A few years back, I shipped a little flashcard app called SnapDecks. The idea was simple: take a picture of a page of notes, and it would turn the text…

  12. The Work Between the Work

    I woke up yesterday to three emails with the same subject line: 'App Gone?' A quick check confirmed it. Numsy Pro, Focus Freeze, and MockupKit—three paid…

  13. My Most Valuable File Isn't Code

    I spent four hours last Tuesday hunting a bug I wrote myself. The real crime wasn't the bug, it was the amnesia. I stared at a block of code, knew my…

  14. The Smartest Feature is an Off Switch

    The angriest support email I ever received wasn't about a crash or a missing feature. It was about an app that was trying too hard to be helpful, and the…

  15. Your Best Feature is Your Privacy Policy

    I got an email last week that wasn't a bug report or a feature request. It was a thank you note. For a sentence in a privacy policy. That told me more…

Reporting

Reported pieces on the tools, defaults and decisions around this beat.

  1. Improving Web Form Accessibility for Assistive Technology Users: A Deep Dive into Inclusive Engineering

    The shift to agentic AI workflows is failing to account for accessibility, creating new barriers for disabled users.

  2. GitHub just made dependency updates a little slower. That may be the safer default.

    Dependabot’s new three-day cooldown is a small default change with real supply-chain consequences for teams that let automation pull fresh packages into production.

  3. xAI’s Grok 4.5 makes the coding-agent fight about deployment economics

    Grok 4.5 is available through xAI’s API and Grok Build at aggressive token prices, but the real test is accepted patches per dollar, not launch-day benchmark fog.

  4. GitHub’s AI week is really about control

    GitHub’s latest changelog reads like a feature sprint, but the bigger story is quieter: AI coding tools are moving from “try this assistant” to governed…

Beat assignments on this page are an editorial judgement made by Shadowfetch; they are not part of the original article metadata.