New team members do not understand your system. Other teams build against your microservice architecture instead of with it. External contributors have no idea how to use your plugin interface. The root cause is almost always the same: there is no concise, convincing architectural overview. In this session, we use two very different real-world systems—the chess engine DokChess and Germany's Corona-Warn-App—to show how you can condense your architecture into something that fits on a few slides or a single flyer, without becoming superficial. We lean on arc42, but focus only on what truly matters for an overview: mission statement, context and scope, quality goals, solution strategy, and the trade-offs every decision brings with it. You will see how the same approach works equally well for a weekend hobby project and for a system operating at national scale, which format—slides, flyer, wiki, or wall—fits your audience, and how to keep your overview from going stale within six months. Two short hands-on exercises let you apply what you have learned to a system of your own right away. You will leave with a concrete, ready-to-use blueprint for your next architectural overview—and the confidence to document trade-offs openly, without talking your own architecture down. Audience: software architects, developers, and anyone who needs to communicate architectural decisions clearly. Duration: 60 minutes, including two hands-on exercises.

Think like a tester, not just a user. Join our hands-on workshop and learn how to design smarter test cases using proven techniques such as Equivalence Partitioning and Boundary Value Analysis. Through interactive exercises and real-world scenarios, you will build practical skills to improve test coverage, uncover defects more effectively, and bring more confidence to your testing. Perfect for aspiring testers, QA professionals, and anyone preparing for the ISTQB Foundation certification.

A successful project starts with a solid testing strategy. In this session, we will explore how to plan testing effectively, define clear objectives, identify risks early, and ensure the right test approach for every project. Let us discover practical techniques that help deliver high-quality software with confidence.

“LGTM”—and other lies we tell ourselves. In this talk, we will look at what actually catches bugs versus what just feels productive, and why that gap matters more now that a growing share of the code we review was written by AI. We will cover the review habits that separate teams who catch real issues from teams who just approve fast, and how to bring the same sharp scrutiny whether the author is a colleague or a model. You will walk away with a checklist you can put to work on your very next PR.

Ready to become the candidate customers remember? Join our interactive training and learn how to confidently present your skills, communicate your value, and stand out in customer project interviews. Through practical tools, role plays, and real-life scenarios, you will master the art of showcasing expertise—from test automation to consulting—with clarity and confidence. Because winning projects starts with winning trust.

AI already writes 75% of Google's new code, and agents now handle tasks that take a professional 14 hours—with their reach doubling every four months. This talk covers where we stand, the risk we are taking on (Dark Code: lines nobody wrote, read, or understood, yet that pass every test), and how the developer job changes once routine coding disappears and judgment becomes the real value.

Your domain logic shouldn't care whether it's talking to a REST API, a message queue, or a test double. Most of us learned to structure applications in layers. It works - until the domain starts quietly depending on the very things it shouldn't. We'll put hexagonal side by side with Layered and Onion architectures to see what each one buys you, and why hexagonal architecture pairs naturally with Domain-Driven Design. Then something newer: using LLMs as an architecture reviewer. I'll show the prompts and workflow that catch leaky abstractions and misplaced business rules before a human reads the diff - including where the model confidently misses things. It's a two-hour session, but not two hours of slides. The content is split into chapters, each closing with a short interactive quiz on what we just covered - quick questions and small code examples to check that the concepts actually landed before we build on them. You'll leave with a clear mental model of ports and adapters, practical patterns for applying them in Domain-Driven Design, and new AI-assisted techniques for verifying your own architecture.

What is actually behind the virtual machine you use for development, testing, or coding? In this session, we will explore the journey from the physical infrastructure inside a data center to a virtual machine that can be accessed from anywhere. Using real-world images and practical explanations, we will look inside a data center and discover what a server rack contains, including servers, storage, networking equipment, and firewalls. We will also explore how these components work together to create, manage, monitor, and provide remote access to virtual machines using technologies such as VMware, orchestration tools, Linux, and Windows. Designed for developers and beginners with no previous infrastructure experience, this session will offer a clearer understanding of the technology behind the environments they use every day, as well as the work performed by system administrators to keep those environments available and secure.

Understanding Requirements & Risk-Based Testing focuses on translating business and technical requirements into effective test cases while prioritizing testing based on the likelihood and impact of potential failures. This approach ensures that the most critical functionalities are tested first, improving product quality, reducing project risks, and optimizing testing effort.

Digital devices have nowadays become so ubiquitous that we can hardly imagine our current lifestyle without its digital component, which has steadily become a continuation of our own real life. Although we are most of the time concerned primarily with our real life, so that we always take steps to make it as comfortable, healthy and hassle-free as possible, we rarely take the same measures in the realm of its digital counterpart. Without knowing how to properly manage our digital life, we are exposing ourselves to risks that can have real and tangible negative consequences which can reflect themselves in our family and social life. Moreover, our professional life may also not remain unharmed. An IT solutions company rarely develops its own software; its most valuable asset is most of the time its know-how, which has to be protected from prying third parties so that the company can succeed in a competitive market. To empower ourselves to make the right choices while surfing the web or when buying a new device, we will learn how to configure our devices to be safer and more private, effectively manage our online accounts, develop safer communication habits, along with many practical steps we can take right away to improve our digital health, security and privacy.

Writing test cases, managing them in Xray, and running them are usually three separate jobs. This talk shows how Claude Code connects them into one workflow: analyzing code, finding coverage gaps, creating test cases directly in Jira Xray, and executing them via browser automation. Live demo, not just theory. Target audience: developers and QA leads who want to know what is automatable today—and where manual control is still required.