© Mapbox, © OpenStreetMap
Annelore Egger

Annelore Egger

Software Engineer, OpenValue Switzerland

Brugg, Switzerland

Actions

Annelore is a passionate software developer from Switzerland who values high-quality code, likes working in teams, and sharing her knowledge. She also likes to meet new people, so if you see her around, feel free to say hi!

Badges

  • Most Active Speaker 2025

Area of Expertise

  • Information & Communications Technology

Topics

  • Java
  • Spring
  • Testing
  • JUnit
  • Mockito

Why Bad Code Quality Is Not (Only) Your Fault

Code quality is often seen as the developer's responsibility, but the reality is that many roles influence the quality of code—starting with business decisions. In this talk, I will share a real-world example where simplifying redundant business rules, identified by a business analyst, led to cleaner, more maintainable code. We will dive into how collaboration between developers, business analysts, product managers, and other stakeholders can shape code quality from the ground up.

By understanding how business logic, requirements, and communication impact the codebase, teams can avoid unnecessary complexity and create software that is simpler to maintain and scale. Whether you are a developer, product manager, or analyst, you will leave with a new perspective on how your role plays a part in building high-quality software.

If you have ever thought code quality is solely a developer's problem, this talk will show you how it truly is a shared responsibility.

In a past project I was approached by the business analyst of our team to some changes in a story I was doing a refinement for. He showed me that he had found some duplications that were unnecessary and also led to more actualisations inside the application, making the performance worse. Even though the performance is not an issue in this application, simplifying the business logic also led to simplified code. At the moment there are a lot of bugs in this particular part of the application and introducing the simplification that the business analyst proposed will lead to better code and most likely to less bugs in this part of the application.

How Unit Testing Saved My Career

When I first started programming and the code did not behave as I expected, I struggled to understand why. Discovering unit testing changed that. Tests helped me validate my work, understand my code, and write it more clearly.

Later, I encountered projects where testing became a source of frustration itself. Complex unit and integration tests made it hard to understand what was actually being tested. When they failed, it was not always clear whether the problem was in the code, the test, or the setup around it.

In this talk, I will share what these experiences taught me about making tests genuinely useful during development. Using Java, JUnit and Mockito, I will explore testable code, mocking, parameterized tests and what to question when a test setup becomes harder to understand than the code it is supposed to test. I will also share an example from my work with AI, where generated code can come with passing tests while both still misunderstand the actual requirement.

Testing can do more than tell you whether code works. It can help you understand and shape your code, and give you confidence while changing it. You will leave with practical ways to recognize when tests are helping, and when the tests themselves deserve to be questioned.

Learning about unit testing was one of the most valuable things that happened to me while I was learning to program. It gave me a way to understand what my code was doing, helped me structure it better, and made programming feel much less frustrating.

Later, I also experienced the opposite side of testing, where complex setups made tests difficult to understand and trust. In this talk, I share how those different experiences changed the way I think about testing and why I now see unit tests as much more than a way to check whether code works. They can also be a tool for understanding, designing, and changing code with more confidence.

Taking Shortcuts Beyond Your IDE

Taking shortcuts in software development does not have to mean cutting corners. I have learned to look for repeated work and ask a different question: do I really need to keep doing this manually?

I will start with small shortcuts that remove friction from everyday development, then move beyond key combinations to refactoring, code generation, templates, automation, dependency updates, and tools such as OpenRewrite. Along the way, I will share examples from my own work, including shortcuts that saved time and cases where automation still required careful review.

Artificial intelligence has made it easier than ever to delegate development tasks, but it is not always the best shortcut. Sometimes a deterministic tool is faster and safer. Sometimes generated results can even send you in the wrong direction if you stop questioning them. I will briefly explore where artificial intelligence fits among the other shortcuts available to us without turning the talk into an artificial intelligence talk.

The goal is not to memorize more shortcuts. It is to develop the habit of noticing repetitive work, choosing the right level of automation, and knowing when taking a shortcut would create more problems than it solves. You will leave with practical ideas for removing unnecessary work from your development workflow while keeping control over the result.

Colleagues were often astonished how many shortcuts I used and how much quicker I can do certain things. As it is always good to check where developers can make their workload lighter I want to show different ways we can take shortcuts without compromising quality.

Testcon 2026

How Unit Testing Saved My Career

October 2026 Vilnius, Lithuania

BED-Con 2026 Sessionize Event

September 2026 Berlin, Germany

Voxxed Days Luxembourg 2026

How Unit Testing Saved My Career

June 2026 Mondorf-les-Bains, Luxembourg

DevBcn 2026 Sessionize Event

June 2026 Barcelona, Spain

GeeCON 2026

Why Bad Code Quality Is Not (Only) Your Fault

May 2026 Kraków, Poland

Voxxed Days Ticino 2026

Why Bad Code Quality Is Not (Only) Your Fault

February 2026 Lugano, Switzerland

IT-Tage 2025

Wie Unit-Tests meine Karriere retteten

December 2025 Frankfurt am Main, Germany

The San Francisco Java User Group

Taking Shortcuts Beyond Your IDE

September 2025 San Francisco, California, United States

WeAreDevelopers World Congress 2025 Sessionize Event

July 2025 Berlin, Germany

JNation 2025 Sessionize Event

May 2025 Coimbra, Portugal

JCON EUROPE 2025 Sessionize Event

May 2025 Köln, Germany

JavaLand 2025

How Unit Testing Saved My Career

April 2025 Adenau, Germany

Devnexus 2025 Sessionize Event

March 2025 Atlanta, Georgia, United States

Annelore Egger

Software Engineer, OpenValue Switzerland

Brugg, Switzerland

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top