Journal

NJP volunteering and small useful tools

Some tools only make sense because a real context keeps them modest. Volunteering at Nancy Jazz Pulsations is one of those contexts for me. YTMusic Liked Sorter does not serve the...

Article5 tagged threads
A festival stage, a volunteer's list with one line highlighted in yellow, and a single small tool for that line

Some tools only make sense because a real context keeps them modest. Volunteering at Nancy Jazz Pulsations is one of those contexts for me. YTMusic Liked Sorter does not serve the festival, but it comes from the same habit.

Problem

It is easy to talk about side projects as if they needed a startup-scale justification. Most do not. The more common failure is the opposite: a recurring annoyance exists, but nobody captures it because it feels too small to deserve a proper tool.

Volunteering helps against that reflex because the work is concrete. You see how information moves, where friction accumulates, which tasks repeat, and what people actually tolerate. That is a better design brief than a generic idea for an app.

My own friction was a YouTube Music like history: too much liked music, no useful way to revisit it. Platform histories are good at accumulation and bad at retrieval. Once the list grows, the archive is technically present but practically lost, and you remember that something existed without any realistic path back to it.

Decision

The decision is to keep these tools intentionally narrow. They do not need to become products, they need to remove one concrete inconvenience.

For YTMusic Liked Sorter, that meant three things:

  • a way to ingest an existing history;
  • a way to sort and filter it more usefully than the default interface;
  • an output that stays readable instead of becoming another pile of data.

The repository is public on GitHub for that reason: the interesting part is the clarity of the retrieval flow, not a polished shell around it. The alternative would have been to overbuild it with accounts, sync or a broader product pitch. That usually kills the clarity of a small utility.

Result

The history becomes sortable again, what had been lost in the volume comes back, and the tool stays close to the problem it was built for. The result is modest, and that is the right scale.

That lesson carries back into professional work. In ecommerce or content projects, not every pain point deserves a new subsystem. Sometimes the best move is still a small utility, a clearer export, a tighter data flow, or a calmer admin path. The difference is not prestige. It is fitness to the problem.

A concrete context keeps that judgment calibrated. It shows quickly that a tool is worth the comfort it gives back, not the size of its code or of the story told around it.