The answers to this question will be a great source of (n=1) validated ideas.

In Brazilian Portuguese advertising is still most commonly called “propaganda”.

But it also has the bad connotation when it’s used in the context of politics.

Coil proposes something on these lines: https://interledger.org/case-studies/coil/

I’m finishing https://sendmyreads.com to help me tackle just that. I figured if I get all the information I gather pulled at me at a convenient time I’d be more likely to actually consume it. It’s been working well, but I’m afraid I’m now biased towards reading it (because I built the thing) so I want to give it more time to see how it goes.

If OP or anyone else is interested let me know and I’ll let you know once it’s ready.

A simple confirmation step with a relevant warning could possibly make developers think twice before proceeding.

From personal experience - no it won't. I have made mistakes with overriding warnings - when under pressure, hyper focused and already in the mental mode of - of course I am sure I want to do it - your slow brain is just shut down so you are moving a bit like on muscle memory.

Simply add a 1 hour unskippable countdown timer to the warning. Now you have to think about it.

If you have one hour you shouldn't be editing live anyway.

From the many depressing years I've done UX work I can promise you no amount of changes they make will protect users from their own mistakes. It is far better for your own sanity to accept people make mistakes. This is what development and staging environments are for.

Accepting that people make mistakes is one thing, but reducing those mistakes is another.

If it’s a simple change, why not do it? Though, I can see your point if the change is monumental but barely reduces rate of mistakes.

Commerce of art.

It can be seen as an addition, true. In my first reads of it, I couldn't think of it as an addition to contemporary Agile practice. Maybe the emotional burden caused by years of (bad) Agile practices got in the way. But even so, in multiple senses, following Software Craftsmanship principles will mean going against currently well-established agile practices.

Yeah. They use Creators on Brave's website: https://creators.brave.com/

Although I do not believe in Brave's model, it is interesting to see their publishers' growth. It is impossible to judge it objectively, but if such change would happen to be organic, I'd start questioning my belief a bit more.

It's not hard to sign up as a publisher you just need an email and have to verify the channel.

The basic idea is as follows: each week, you have an HTML file with some content, and your goal is to create the CSS file that makes this a beautiful piece of (web) art. The contest runs on Github on top of some automation. Contributions, entries, and content suggestions are all handled there. At the end of each week, the project bot selects a winning entry (you vote by reacting to the entry PR), which is then deployed to https://csscontest.com and stays there for the whole week. A more detailed explanation is here: https://github.com/bitsofart/contest/#welcome. This project is the result of a lot of my interests put together. I wanted to be a designer at the beginning of my career. Back in those days, https://www.awwwards.com/ was a fantastic source of inspiration, and I dreamed of one day having that website of the day ribbon on my website. This day never came, and my interests shifted towards programming and code. But I still love seeing amazing visuals on the web, and I've always thought how nice it would be to have an award, like the Awwwards' site of the day, but more open, both in terms of content and selection.

Along with that, I'm also fascinated by evolution and the idea of things organically progressing in ways no one can anticipate. And I've been long thinking of this idea of a "crowdsourced" code project, and where a community of coders would take it.

So I merged the two ideas in this project: An open space for the community to participate in a contest to make beautiful things on the web. All the few contest's rules and their application are open-source (there are links for them in the repo), and everything is automated so we can have as few single-person interferences as possible. In an ideal world, everyone interested can participate, and I, as the owner of the repo, don't even have to look at it.