Gregor Riegler @gregorriegler@qoto.org

@admitsWrongIfProven If you want to try TDD right now, we have a remote event running for the next 24hours and its free to join. We're practicing TDD, in different languages and groups. It's a very open and friendly environment. Just send me a DM and I will provide you with the Access.

@admitsWrongIfProven Please don't delete. Questions are the best. I practice TDD where I drive all production code through a failung test. This means I write a failing test first. And only after that, I write the code to make it pass. This ends up me spending more time writing the test - going slow, thinking about the design. The writing of the test is the act of designing here. So in my workflow, there is no "write the tests fast". The tests are first class, and they come first. The production code is what I try to write fast to get to green quickly.

The fixing of a flaky test that fails once a year will pay at one point. Assume how long it will take you to fix it, and the cost of the failure, and do the math.

"TDD is a process that encorporates failure."
~Marc [participant at GDCCR]
https://lnkd.in/dcrnuxtW

@admitsWrongIfProven Guilt counters healing and change for better

When a problem occurs, remind people not to fix each others behavior but the hazardous environment that enabled it in the first place.
Anything that can go wrong will go wrong.
This cultural thing is grounded deep down in held beliefs and takes deliberate effort to overcome.

Ok, let's do this.