There is a related problem where many browser-based productivity tools follow design principles from websites that are trying to get clicks. For example, I commonly run into DB interfaces at work that will return, say, 10 (or 25, or other small number) results per page. Now, it's good design to not let a query that returns, say, a million results, crash the browser. But, if a few hundred, or even a few thousand, results will display within milliseconds, why make me page dozens (or hundreds) of times? (I'm looking at you, GitHub commit history!)
Another example would be Microsoft Office's long history of making design choices that optimize increasing "engagement with the tool" rather than making the tool unobtrusively facilitate the task. They got rid of Clippy, but now they're into obnoxious pop-ups that are designed to call attention to some new gadget or feature.
The "click" economy has had pervasive effects on the software industry.
As someone who writes for fun, I don't need to get people onto my site:
If I write a post and some people are able to get the core idea just from the title or a tweet-length summary, great!
I can include the full contents of my posts in my RSS feed and on FB, because so what if people read the whole post there and never click though to my site?
It would be different if I funded my writing through ads (maximize time on site to maximize impressions) or subscriptions (get the chance to pitch, probably want to tease a paywall).
Sometimes I notice myself accidentally copying what makes sense for other writers. For example, because I can't put full-length posts on Bluesky or Mastodon I write short intros and link my full post. Yesterday I initially drafted:
This would have gotten more people to click through, but that shouldn't be my target. Instead I posted:
No need to hold curiosity hostage.
It's common to criticize "clickbait", where a teaser entices and then doesn't deliver, but even reserving key information for the full article is a product of authors (needing to!) optimize for goals other than communicating to users. I like that this isn't a pressure that I'm under. Because our culture has so many who are under it, however, optimizing for communication can require noticing and intentionally avoiding common patterns.