Ever wondered why working in global teams feels like unravelling a mystery? You're not alone! The reality of working within such a team can differ from expectations. Often, the greatest challenge for developers isn't the actual work, but rather navigating the distance, understanding cultural disparities, and maintaining meaningful connections with team members.

Today, whether we work in Kraków or New York, Amsterdam or New Delhi, we are all part of a global network where success requires traversing vastly different cultural realities. But how do you deliver constructive feedback to colleagues from Asia, America, or Europe? And why does your Indian team really need an hour for lunch? Also, do you know the secret that a ‘NO’ can come in many disguises?

In this session, I will share personal stories and practical strategies from my years of working with multicultural teams. These strategies aim to enhance communication, bridge cultural gaps, and foster strong collaboration across continents. Join me as we embark on a journey filled with laughter, learning, and limitless possibilities.

The Problem: Modern Java applications often become prisoners of their frameworks. While tools like Spring Boot and Quarkus accelerate development, they create hidden costs: vendor lock-in, bloated dependencies and rigid architectures. What happens when your project outgrows your framework—or a new, better tool emerges?

The Solution: This talk introduces a layered approach to Java development, isolating framework dependencies while keeping core logic pure with Java and Jakarta EE. Through examples, you’ll see:

• How to decouple business logic using JSR standards
• Strategies to replace framework-specific annotations
• Cloud integration without framework coupling.

Trade-Offs: Yes, this demands more upfront effort—writing custom persistence layers, rigorous tests, and meticulous docs. But the payoff is code that’s adaptable, testable, and maintainable across frameworks, teams, and decades.

Key Takeaways:

• Practical patterns for agnostic design.
• When (and when not) to adopt this approach.
• Tools to ease the transition.

Join me to rethink Java development: less framework magic, more future-proof code.