Software Engineering in Web Development, Backend Services, and More

Category: Projects (Page 2 of 38)

Posts introducing, updating, and covering various projects to which I’ve contributed or that I maintain.

Where Can I Watch? 1.4.0: Today, and Detail Pages Everywhere

Where Can I Watch? 1.4.0 is out, and it’s one of the bigger releases since launch. Two ideas drove most of the work: making Today its own top-level tab, and giving Episode Detail a consistent home in every place in the app where you might tap into an episode.

When 1.3.0 shipped, the plan I wrote for 1.4.0 was a detail-page overhaul:

  • content rating badges,
  • runtime,
  • on-your-services callouts,
  • and person search.

The more I continued to use the app, the more it was clear the foundation for those enhancements wasn’t quite in place yet:

  • Episode Detail only opened from one corner of the app,
  • Today was still a pinned section inside Watchlist,
  • and the streaming service name, the whole point of the app, was missing from a few places a user would most want it.

1.4.0 puts those foundations in place. The detail-page enhancements will be in 1.5.0, built on top of everything in this release.


Continue reading

Where Can I Watch? 1.3.0: A Clarity Pass

Where Can I Watch? 1.3.0 is out, and this one is less about new features and more about making controls that have been in the app since launch easier to find and easier to trust.

When 1.2.0 shipped, I wrote that 1.3.0 was going to be a detail-page overhaul. But the more I used the app, the more I noticed another set of issues specifically around the filtering controls in the Services tab. They’ve been there since 1.0.0, but they’re buried far too low beneath the list of streaming service providers. So I shifted gears. The detail-page work moved to 1.4.0, and 1.3.0 became a clarity pass on the filtering experience across Search and Trending.


Continue reading

Building (and Evaluating) a Codebase Onboarding Skill for Claude Code

If you spend any meaningful amount of time working with Claude Code, you’ll eventually hit a familiar wall: you open a conversation, ask it to do something, and it starts poking around your project like it’s never been there before.

Because it hasn’t. Every conversation starts fresh.

That’s fine for small projects. But when you’re working across a monorepo with a dozen cloud functions, shared utilities, and deployment scripts, watching Claude re-explore the same directory tree for the fifth time in yet-another-worktree in a single day, it gets old (and expensive, as far as tokens are concerned).

So I built /onboard. It’s a Claude Code skill that scans the current working directory, builds a structured summary of the codebase, and caches it so future conversations can skip the discovery phase entirely.

It started life as a slash command called /ingest, but I’ve since ported it to a proper skill with smarter defaults and a key-files-first approach that keeps token costs down.

Granted, it’s very much experimental right now (so much so I’m documenting the process of evaluating it).


Continue reading
« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑