Login
You're viewing the functional.cafe public feed.
  • Sep 19, 2026, 8:53 PM

    @jrdepriest @jrconlin
    yeah but then you end up with 5 year old versions of stuff and never have time to upgrade...

    So I don't blame people who just upgrade on dev, wait a week to see if it blows up, if not, upgrade prod, without reading changelog at any point in the process.

    When the upstream project's rate of change is "web-scale", you're stuck between to bad options :/

    💬 1🔄 0⭐ 1

Replies

  • Sep 19, 2026, 10:39 PM

    @wolf480pl @jrdepriest

    I mean, a LOT of that supposes that the Change log is accurate. I think we've all see major, breaking changes rolled out in a minor or bug release.

    On a separate note, I noted that I would do version updates once a quarter (unless there was a critical CVE or something), and would do them by hand whenever possible. (There were a few engineers that said "Have Claude do that!", and it made a cold chill run down my spine.)

    Doing those updates re-familiarized me with the code. In addition, the changes were often subtle, and sometimes required changes in other parts of the library or code (so I didn't roll out some breaking change). Plus, they were kinda zen since it was an opportunity to learn some new approach. For instance updates to Rust generally included changes to  clippy which taught me new approaches.

    Surrendering that to some automated function basically made sure that the code was that less familiar to me, meaning that any future changes will probably have subtle errors or force me to learn the change anyway.

    💬 1🔄 0⭐ 0
  • Sep 19, 2026, 10:47 PM

    @jrconlin
    Oh, it doesn't, the second 80% of the work is fixing stuff after it broke due to things not described in the changelog, or that were described but you didn't thought would affect you.

    Also, version updates once a quarter? More like, one dependency a quarter.
    @jrdepriest

    💬 0🔄 0⭐ 2