I would not leave the train until I would find the root cause, I’ve never seen such a detailed stack trace on public transport system errors
20.02.2026 07:49
👍 3
🔁 0
💬 1
📌 0
I would not leave the train until I would find the root cause, I’ve never seen such a detailed stack trace on public transport system errors
TDD's like the brakes on your car. It enables you to get there *sooner* (presuming you wish to arrive in one piece).
codemanship.wordpress.com/2026/02/08/t...
I should start asking interview candidates what they think about KISS principle
What is the best guardrail to avoid AI making a mess of your codebase? Create tests FIRST to build a safe net around the playground where your AI can do its “magic”.
So that’s why we need tools that allow us to do meaningful reviews while the rest of the code is kept between the guardrails automatically. And we need to do it in a closely controlled loop way, prioritizing short feedback cycles.
Bugs and hallucinations are tricky to spot, and while productivity has increased, trust hasn’t kept up.
www.sonarsource.com/blog/ai-codi...
Great article that highlights a dilemma a lot of developers are facing right now: trusting the AI-generated code. The amount of effort and attention needed is far greater than with code written by a colleague.
Also in the 2000s, thinking of Avenged Sevenfold’s “City of Evil” and the ballad “Seize the Day”
Hola Java devs! 👋 The #SonarQube AI Code Assurance #article is LIVE on @foojay.io ! 🎉
Stop just finding bugs. 🛑 Use SonarQube's new AI "Magic Button" to auto-fix them instantly! 🤯🪄
Crush that tech debt fast. 🚀☕️ #Java #AI
@sonarsource.bsky.social
foojay.io/today/sonarq...
I’m trying the same in my company and the feedback I get is always “we’re too busy, come back another time”. I stopped actively advocating for it unless there’s a real engineering demand for it. Management won’t get anything out of this, it needs to come from bottom to the top.
Your tests should give you confidence, not slow you down or break on every refactor. Marco talks with J. B. Rainsberger, TDD coach and software consultant, about how TDD actually works and what most teams get wrong about testing.
Full episode: https://youtu.be/j0NjFsb-at8
Join us for our last session at the ING Leeuwarden office in two weeks! As Elias mentioned we'll have two great tech talks for you in store.
"Non perdere tempo a discutere con quell'uomo, è inutile: stai solo dando le perle ai porci." Which would translate to: “don’t waste your time discussing with that man, it’s useless: you’re just giving pearls to pigs.”
“Perle ai porci!”
We have the exact same way of saying in Italian too! We use it when a very useful thing gets used by who doesn’t understand the real value or advantage of it
What is your definition of a “bad test”? As soon as that is clear, a solution can be found
blog.jetbrains.com/kotlin/2025/... real life code examples that showcase how Kotlin can improve the quality of your codebase, by leveraging features built in the language
Short blog, but I think it really hits the spot on the skills great software engineers have 👍
terriblesoftware.org/2025/11/25/w...
JUnit is undoubtedly one of the most important projects in the #Java ecosystem. And it's 100% free and open!
Let me be frank: If we can't get THIS project to the point where a single maintainer can focus on it, then what does that say about our commitment to Free & Open Source Software?
1/3 ⏩
blog.jetbrains.com/kotlin/2025/... great blog post that proves why moving to Kotlin is a good choice. @jlengrand.bsky.social and I can vouch for that 😉
Exciting News 🎉 Spring Boot 4.0.0 is here: spring.io/blog/2025/11...
I was thinking exactly about this incremental migration to unit tests while addressing mutations, great idea. I’ve done a presentation exactly tackling this point and I think it really elevates developer experience
No it doesn’t, but then it needs to be very clear in the expectations for the developers that it will be harder to address in an agile way the mutations in the code. Lots of setup and slower feedback will not be the greatest of developer experience. All is good, as long as it’s clear from the start.
Then I would consider introducing the pyramid of testing as a guideline martinfowler.com/bliki/TestPy...
Totally agree. It was a game changer when I started and still is. I still see managers chasing the perfect code coverage as a number, while they should chase the test strength and a better philosophy of developing software. TDD even comes handy as an enabler for this.
When I introduce mutation testing to teams on the Code Craft training workshop, it's invariably one of those "How did this not occur to us before?" moments.
"Is our code broken and we don't know it?" Let's break it and see if any of your tests fail.
I think the point Ted is making is focus running the mutants only on unit tests, to increase fast feedback and allow more flexibility to address a mutation. Including integration tests in the scope increases the coverage but it’s going to be much harder to address a mutation there.
I'm documenting Spring Boot 4 features with:
✅ Code examples
✅ Video tutorials
✅ Blog deep-dives
All organized in one central repo 👇
github.com/danvega/sb4
