Soon I'll do some automation with a #NodeRED capable device (Victron Cerbo GX)
Since I usually do #TDD and don't like web GUI graphic coding but git, IDEs, testpipelines etc. maybe anyone has a hint for software devs to code in such an environment?
Perhaps @nodered you get this question regularly?

The last core framework release was July 13. We definitely have enough for a new release next week. If you're so inclined, maybe pick up a CI build and test it before we ship and/or raise awareness of anything you want fixed. https://xunit.net/docs/using-ci-builds

Okay, so how does this work now?
Whom should I be following?
Looking for nerds, tech heads and especially #kotlin #android devs and meta topic stuff, like #TDD, #softwarearchitecture and so on

Also people to discuss why we will not lose our jobs to #AI

I let #copilot also work to create a library with a specific functionality as I was working on another project. it was something that I expect #AI can easily perform. The "demo-app" it first created was fine and thus I let it continue and develop the entire library so that it could introduce some additional optimization. I explicitly told it to develop in #TDD style since that produces the best result. Two hours later: Tests have been ignored, modified to to allow bugs and lied about.d.

Given that xUnit.net runs tests in random order by default, would changing the randomization order (in order to fix a bug) just be considered a bug fix or a breaking change?

Asking for a SemVer.

With TDD, where do you even begin? https://qualitycoding.org/tdd-where-do-you-even-begin/ #TDD

Welcome @michele_sollecito!

Michele is a former colleague of mine and one of my key references in Leadership, Software Engineering, TDD, Hexagonal Architecture, Kotlin, and Java. It took me ages to convince him to join Fedi, so please give him a warm welcome!

Claude code kinda-sorta recommends #TDD: https://www.anthropic.com/engineering/claude-code-best-practices#:~:text=b.%20Write%20tests%2C%20commit%3B%20code%2C%20iterate%2C%20commit

missing the refactor step, but still, well done @anthropicai , partial credit!

Lines up with what I'm planning to say about AI in the third edition of : https://github.com/hjwp/Book-TDD-Web-Dev-Python/blob/main/ai_preface.asciidoc -- tldr, ai works best in the context of a tdd-like workflow.

We just shipped Visual Studio adapter 3.1.3.

This is a bug fix release to address a failure case when running xUnit.net v2 tests (which was introduced in 3.1.0).

https://xunit.net/releases/visualstudio/3.1.3

We just shipped Core Framework v3 3.0.0, Analyzers 1.23.0, and Visual Studio adapter 3.1.2.

Check the release notes for breaking changes, new features, and bugs fixed.

https://xunit.net/releases/v3/3.0.0
https://xunit.net/releases/analyzers/1.23.0
https://xunit.net/releases/visualstudio/3.1.2

How I refactor my tests in Clojure

https://youtu.be/MAsQznQsCgs

For me, one of the best definitions of Test-Driven Development comes from the paper "Mock Roles, Not Objects" by Steve Freeman, Nat Pryce, Tim Mackinnon, Joe Walnes.
http://jmock.org/oopsla2004.pdf

Feedback and Test-Driven Development

https://videos.devteams.at/w/x5Hkwz6ey1GeNF5sZRKAcP

In software development, we have many ways to speed up the time until we get good feedback (in this video, I talk about test-driven development or #TDD).

So, if we are in an environment where we get feedback slowly, we are choosing slow feedback - deliberately or by neglect.

Why are so many choosing slow feedback? https://videos.devteams.at/w/x5Hkwz6ey1GeNF5sZRKAcP

If you prefer youtube, watch here: https://youtu.be/NIP13D9cEgc

We just shipped a new prerelease build of the core framework (3.0.0-pre.40).

There are no new breaking changes, so this will not reset our release clock for 3.0.0 (which should be in about a week).

https://xunit.net/releases/v3/3.0.0-pre.40