It also doesn't mean nothing breaks when people aren't making changes. Certificate expiration is the classic example of something breaking _because_ someone hasn't made a change. Or a slow memory leak. There's a whole classification of issues that get worse when nothing is redeployed for long enough.

PagerDuty wouldn't exist if this were true.

The amount of improvements to our collective understandings was super valuable. Feature devs got to help fix problems with their tools more directly (while also learning that it's not always as straightforward as it may seem), and we brought back much stronger insights into the experience of actually using our tools day-to-day.

Even if they're sometimes slower in pickup or trip time, on average, I greatly value the consistency of the experience over everything else.

Love a good "over yonder" though.

As an aside, I find it strange how many aspects of "the south" are labeled as "Texan" outside the south. I lived and visited all over the Deep South and y'all was standard vernacular pretty much everywhere. I'm not saying Texans don't say y'all, but they definitely don't have any unique claim to using it as second-person plural.

There are also annotated tags that can contain a message, have a timestamp, and sha, etc. These are proper git objects that behave a lot like commit objects, except they're still typically only referring to another git object (commit).

https://www.cdc.gov/botulism/infant-botulism.html.

What seems weird is they went through the effort of installing a nonfunctional yet functional-looking piece.