1. You write release notes thet contain technical details. Less than 1% of your customers understand them. More than 90% probably won't even care, let alone understand the document. And then there are the folks who get confused or scared and reach out to customer support with weird questions. This generates extra workload.
2. You explain nothing. The release simply is. The technically minded people are mildly annoyed. A few customers affected by open issues wonder if it's fixed now. The rest of them doesn't even care that there is an uodate and carries on with their lives. Customer service continues to complain about the usual bunch of random and weird customer issues.
It's quite natural to start doing (2) in a consumer facing business, isn't it?
Like spoilt children. I genuinely don’t know if it’s the decades of SV pandering or what.
MOST OF THE TIME, NOBODY CARES ABOUT YOU. And they’re probably right not to.
The "tech nerds" is a bullshit term for "people with the background to understand the explanation." If you're not explaining it to them, you're not explaining it to anyone. You're just subjecting everyone to your whims, and really should be regulated into the unemployment line.
That everything has to be about profit is a lot of what's wrong these days. And yes, bitching about this on a YC-owned forum is just as silly as bitching about nerds here, I'm aware.
One of the biggest organizational anti-patterns of the modern SaaS world is the move away from release notes.
It's a question of whether a company has a competent enough change control process to be able to generate a list of changes for a given release.
If a tech product company can't meet the low bar of documenting its changes, then it probably shouldn't be trusted?
Release notes aren't for end users in the same way that the wiring diagram taped to the back of your appliances isn't for end users.
They're for experts to either directly use... or to communicate in simpler language to end users.
It's the nerds that the non-nerds/normies go to for advice on tech-y things. If you can generally make the nerds happy, and earn a good reputation among them, you'll have a customer base from which to expand from.
Or as Tim O'Reilly recommended back in the day, "Watching the Alpha Geeks":
* https://web.stanford.edu/class/ee380/Abstracts/081119-stanfo...
* https://web.archive.org/web/20130000000000*/http://origin.co...
The costs will be recouped by sacking more developers...
Or businesses would close to do inventory.
We made do.
Not my own device on my own machine.
I don't remember a time my CD player on my car would stop working due to an update.
Absolutely.
But also don't break my stuff.
However the very update that says it fixes the blank screen caused the blank screen to happen in the first place. (Never happened before that update.)
Then another silent update not listed on their site undoes that problem, but you have to wait a month or so to get it.
"Bug fixes and performance improvements "
Even worse than the "reformat" commit message that your bisect landed on.