Also, alerts are terrible UX. At least put some effort into your example.

For anyone wondering, the South Korean birth rate is currently ~0.7: https://ourworldindata.org/grapher/children-born-per-woman?c...

The problem is centralization is more convenient for consumers. You can easily control your doorbell, your garage door, your security cameras with 1 app, and everything just works.

Open source and decentralized solutions need to be just as convenient and cheaper than centralized ones for consumers to choose them.

So at the end of this process, you've spent anywhere from $1 to $5 to fix a bug, and you don't have any of the knowledge you would have gained from being directly involved in the fix. It seems like this approach would keep a developer easily replaceable over time, regardless of how long they've been working with a codebase, because they build very little internal knowledge on it.

One problem is that people don't like learning new software interfaces, and another is that communities help support software, but communities need stable, long-lived software to foster.

I've also been using LLMs to create and maintain a "work assist" Chrome extension that I load unpacked from a local directory. Whenever I notice a minor pain point, I get the LLM to quickly implement a remedy. For example, I usually have several browser tabs open for Jira, and they all have the same company logo as the favicon, so my Chrome extension changes the favicon to be the issue type icon (e.g. Bug, Story, etc) when the page loads. It saves a little time when I'm looking for a specific ticket I've already opened.

If the goal is to attract readers without providing any value at all, it's extremely easy to do that nowadays with AI. And luckily it's just as easy to identify low-effort articles written by AI.