In this talk we’ll look at learning a new language from a Linguistic and Neurological perspective, while at the same time looking at how we can apply this in the IT setting we work in. At the end of this talk you will know how your brain stores new information and how that information can be retrieved and used. Next to that you will be given some practical tips and tricks on how to improve your own learning curve and how to help others support others who are in the process of learning. As a previous speech-and-language therapist I would like to give you a better understanding of how we learn languages and how this knowledge can help us in the never-ending changing world of software development!

We’ll also cover how to structure your coding sessions using the primary–recency effect. Along the way, you’ll get actionable tips for boosting focus and leveraging downtime. Whether you’re learning a new Java framework or mastering advanced concepts, you’ll walk away with science-backed tips to learn smarter, code better, and stay ahead.

But as we embrace these new technologies, we must also ask ourselves: Are we becoming less capable of thinking for ourselves?

Do these tools make us smarter, or do they risk dulling our critical thinking skills? This talk will encourage us to think critically about the role of AI in our education. Together, we will discover how to use AI to support our learning journey while still developing our ability to think critically.

That’s all nice and dandy. But we do need to deal with some concerns like:

• Knowledge gap: How can the different disciplines with their specialty understand each other and come to conclusions?
• Shared responsibilities: Where do start and where do they end?
• Efficiency: What would it do to the efficiency of the team when they get different tasks?

In this talk we’ll try to address and hopefully take away those concerns and focus on the benefits it will bring, working in a hybride team.

How to verify your Kotlin project in a Kotlin way? I am talking about test coverage and about style linter. Wouldn’t it be great if we can really use Kotlin in the full spectrum and use tools that support those features? Of course, we would also like to check our code with a linter. In Java we have multiple ways to do that, but with the specific Kotlin format, we are in need of a new linter and formatter. Ktlint (spoken as kitty-lint, for the cat-lovers among us) is the perfect plugin to fit your needs. Most of us will know or even use test coverage engines like Jacoco or IntelliJ. An advantage of this is that it’s well known and considerably solid. The disadvantage is that it doesn’t support all Kotlin features, like a Kotlin directory structure. Because of that you have to choose to OR don’t use the Kotlin directory structure, OR pick a new test coverage engine. This is where Kover comes in. In this talk I will go over both plugins to see what the advantages are, how to configure them, and to determine which child-diseases are still there.