Brazil's way ahead of that, we've had Xtreme Go Horse Programming for over a decade now

• XGH is fully reactive - Errors only exist when they show up.
• Tests are for the weak - If the code runs, it's fine.
• It's only your problem if your name is in the docs - Always remember to have someone else to blame and to keep your resume up to date.

My favorite YOLO-Driven Development practice (from a former employer) was Customers as QA. We would write code, build the code, and ship it to the customer, then the customer would run the code, file bugs for what broke, and we would have a new build ready next week.

It provides many benefits:

• No need to hire QA engineers.
• Focuses developer debugging time on features actually used by customers instead of corner cases that no customer is hitting.
• Developers deliver features faster instead of wasting time writing automated tests.
• Builds are faster because "test" stages are no-op.

One time a developer was caught writing automated tests (was not sure in the correctness of his code, a sign of a poor developer). Our manager took 15 minutes out of his busy day to yell at him about wasting company resources and putting release timelines in jeopardy.

I think I know some of the people who wrote this. Unless more than a few people work this way. That can’t be true, right? Right!?

In France we have https://www.la-rache.com/ which may be older. I may have to post a translation here because it’s realistic.