Speaker Details

Nick Ebbitt

Morgan Stanley

Nick is a software engineer working with various technologies in multiple industries for over 20 years. He is a developer with a strong interest in operations and a passion for building platforms, enabling product teams and developers to become more effective at delivering change. His passion for Java and the community have led him to become leader of his local JUG, the Manchester Java Community.

Grow yourself through communities

Byte Size
People & Culture

Communities are at the heart of everything we do and at any one moment we are likely involved with at least a few of them, whether we realise it or not. Whatever stage you are at in your tech journey there will be opportunities to engage with communities and I believe that when you do you will grow, both personally and professionally.


In this session I will share my experience of how being actively involved with communities has helped me grow in a variety of ways. Whether you are new to the tech industry or already involved you'll hear ideas around how to discover, engage with and get the most out of the communities you become involved with.


You'll come away from this session with an understanding of what a community is, why they are important and their different forms. Most importantly you'll be more likely to identify the opportunities for growth when they present themselves to you, and hopefully you'll have more confidence enabling you to embrace them.


The story of a Java 17 native memory leak

Ignite
Java

Shortly after the release of Java 17 the platform team in my organisation prepared a new Docker base image that allowed product teams to upgrade and create new services that target the latest LTS. Within a few days of some services being upgraded we spotted some interesting trends in respect of the memory usage for them. Simply switching the JDK from 11 to 17 had resulted in a slow native memory leak!


This ignite talk charts the story of how a Java 17 native memory leak played out in public on Twitter demonstrating the power of the Java community. We'll follow the journey through discovery, investigation, confusion, enlightenment, resolution and finally verification of the fix.