ArnhemJUG
We are excited to announce that we are welcomed by TenneT for the September meetup.
Agenda
- 17:00 CET walk-in
- 17:30 – 18:30 Food and drinks
- 18:30 – 19:30 talk: We hate code - The !joy of maintaining dead code by Gerrit Grunward
- 19:30 – 19:45 break
- 19:45 – 20:45 talk: Beyond Green: Rethinking Automated Testing through Failure by Tim Nederhoff
- 20:45 – 21:30 drinks
We hate code - The !joy of maintaining dead code
Do you love to maintain code that you didn’t wrote? Probably not…
As systems grow and evolve, the codebase inevitably accumulates clutter, including unused or “dead” code.
Often the developers who wrote that code are not even in the company anymore. So how do you know if the code is still used? Dead code can be confusing and it can be the source for vulnerabilities in your code base.
So it is not only “legacy” code we have to deal with but also “dead” code and even so called “zombie” code.
This session will give you an overview over the common struggle with this types of code and it will try to give you an idea about the differences between those types of code and about tools like JaCoCo, Scavenger or OpenRewrite in combination with Intelligence Cloud that will help you to get rid of it.
About Gerrit Grunwald
Gerrit Grunwald is a software engineer that loves coding for around 40 years already. He is a true believer in open source and he is an active member of the Java community, where he founded and leads the Java User Group Münster (Germany), he is a JavaOne rockstar and a Java Champion. He is a speaker at conferences and user groups internationally and writes for several magazines.
Beyond Green: Rethinking Automated Testing through Failure
Automated testing is often limited to green checkmarks and pass/fail pipelines. But what if the real value doesn't lie in the results, but in the process of getting there? In this talk, I will share insights from 12 years of experience as a Test Automation Engineer, exploring the invisible pain points that exist before a test even reaches the validation stage.
Through failed test setups and unreliable environments, I discovered that writing automated tests is not just about verification — it’s a learning journey. It's how we, as both testers and developers, get to know the application, the architecture, and the bottlenecks. I’ll discuss the limitations of traditional black-box testing, the merits of white-box approaches, and the practical balance between them.
You'll learn how I redefined my framework requirements to focus on traceability, reusability, and transparency—designing a test setup that not only shows what passed or failed, but also why something couldn’t be tested at all. I'll show how adopting the right tools, avoiding unnecessary complexity, and embracing structured failure has led to faster feedback, better collaboration with stakeholders, and ultimately more trust in test automation.
About Tim Nederhoff
Tim Nederhoff is a Test Automation Engineer at TenneT, where he designs and implements automated testing frameworks to improve software quality. With a strong foundation in automated testing, mocking, stubbing, and CI/CD pipelines, he’s built tools that boost both efficiency and reliability. Tim shares his insights through an active blog and GitHub projects, engaging the wider developer and tester communities.
