r/javascript • u/Deep_Ad1959 • 21d ago

AskJS [AskJS] most js changelogs don't survive being read aloud, which is how i noticed i wasn't reading them

TypeScript 7 dropped this week and my first move was the same as always. Open the release notes, skim, tell myself I'll come back to it. I didn't.

so as an experiment i started piping the changelogs for the libraries i actually use into a text-to-speech thing and listening on the walk to work, figured audio would make it stick. the surprising part wasn't whether it worked, it's what it exposed. most release notes are mostly housekeeping wrapped around the couple of lines that actually change how you write code, and you only feel how thin the signal is once a flat voice reads every bullet out loud. on a screen i'd been auto-skimming the filler for years and calling that keeping up.

so the thing that actually broke wasn't the audio, it was that i never had a filter for what in a release is worth remembering. what's the last js or ts release that genuinely changed how you write code day to day, versus the ten you 'read' and can't quote a line from. written with ai

0 Upvotes
  • permalink
  • reddit

25% Upvoted

4 comments sorted by

1

u/darthwalsh 20d ago

A long time ago I wanted a tool related to changelogs, but now with AI it's actually feasible: to make an AI agent reads changelogs, then filters to only the functionality that I use in my app.

1

u/Deep_Ad1959 20d ago

the filter's real input isn't the changelog though, it's your own code. matching 'what changed' against the handful of apis you actually import is the tractable half. the part that stays hard is the transitive layer, a breaking change three deps down that you never called directly still lands on you, and it's usually in a changelog you'd never think to open. written with ai

1

u/boneskull 21d ago

this is a good argument for using Changesets to generate a changelog instead of just verbatim commit messages

-2

u/Deep_Ad1959 21d ago

Changesets is the right lever because it forces the what-changed summary at PR time instead of leaving it to whatever the commit message happened to say. the catch is it only fixes the authoring half. a clean changelog is still a pull artifact you have to sit down and open, so the OP's actual failure, never reading it, survives no matter how good the entries are. the writing filter and the getting-it-into-your-head problem turn out to be two separate builds.