[–] 1 point 1 year ago (1 child)

A developer here, I usually list user - facing changes in the Changelog.

Even if the changes are not listed, general "bug fixes and performance improvements" is a worthwhile update too. These updates can contain fixes to annoying UX glitches, or really speed up the app, if a new faster API endpoint was added to the backend, and app change is needed to make use of it. You will also get security updates, to the app and its bundled libraries which is important nowadays.

  • source
  • [–] -2 points 1 year ago (7 children)

    Google does a lot of A/B testing, so listing new changes may be pointless as the new features may be available only to select few.

    Also developers have no incentive to document changes. It's a hassle to compile a list of changes since last release, and people don't read the Changelog for every release, especially with auto updates on.

    I'd be great if they could at least use an LLM to compile the Changelog

  • source
  • parent
  • context
  • [–] 9 points 1 year ago

    Sounds like a flawed workflow, if this didn't go through at least code review. Was it committed directly to master?

    Curious to know what kind of system relies on hashed not changing? Technically the hashes don't change, but a new set of commits is made. The history diverges, and you can still keep the old master if you need it for some time, even cherry pick patches to it..

  • source
  • parent
  • context
  • [–] 9 points 1 year ago*

    Walkable means all you need is in reasonable walking distance.

    I wouldn't consider my neighbourhood to be particularly walkable as it's a suburb (in Europe) but my library is about 15 mins walk away.

    Sometimes the amenity you need isn't in that walkable range, but cycling is a great alternative.

  • source
  • view more: ‹ prev next ›