Navigating humans: People Mental Models for Software Engineers

Software is a people problem, and people problems are tough.
"Engineering leadership" is not just about technical prowess; it's about people, interactions and understanding the human element. 

We'll approach human interactions from the perspective of science, and look at what comes up through lens applicable to software.
Dreyfus? Meyers-Briggs? Gallup? Let's have a look at what they measure and more importantly, how can they can be useful if you're leading a software team or a whole engineering department.

We'll explore strategies for effective leadership, emphasizing the importance of decentralized management and nurturing implicit understanding within teams – that scales.

New talk - converting own notes when managing >400 people into a talk, to help others.

Scooby RAM, where are you?

Java, the runtime, likes memory.
It is a fact well known to those who know it well, that subtle differences in code, can lead to drastic changes to applications memory and runtime profiles.
I’ll take you through the memory lane part of my work, and show how do I approach analysis, problems and troubleshooting. Tools, what information can they surface, and how to navigate back to the code.
Techniques and libraries, how do they affect what the application does. Feel invited if you believe troubleshooting memory in Java is “magic”, or “only tuning the GC can save us”.

Avoiding mistakes with events, one event at a time

Some say: Use events, events are great, all will be great and rosy. Then reality bites, and.. let's talk about strangers you'd rather avoid - mistakes to make when building using events. Things change, evolve, are not and overdelivered, old events start taking a lot of space, and someone is already using the name you wanted?! Expect: problems, symptoms, consequences, and some 'get-out-of' cards. Come for the experience others gained first-hand, so you know what to avoid.