Last week an issue came up where we have to upgrade from Postgres 12 to 16 because of EOL concerns. I said to another engineer, “Postgres is pretty boring so I bet it’ll be quite easy/low risk to do the upgrade.”
We got into a meta discussion about how we still have to approach it methodically, but the nice thing about boring, mature software is having a good gut feel that it probably won’t dip into the risk budget much at all.
We got into a meta discussion about how we still have to approach it methodically, but the nice thing about boring, mature software is having a good gut feel that it probably won’t dip into the risk budget much at all.