How a new & much simpler approach called 2-Sigma Observability can massively reduce the number of false positive alerts & uncover some undetectable issues

Run through the entire process of creating a Java library from zero to publishing it to Maven Central Repository.

Integrated tests are a scam. You’re probably writing 2-5% of the integrated tests you need to test thoroughly. You’re probably duplicating unit tests…

In this session you'll learn novel techniques that help you make sense of large codebases.
You'll learn to identify the code that really matters for your ability to maintain a system, how to prioritize improvements [...]

Make Impact, Not Software. I call this ‘The GPS Talk’

Full talk title: Being glue

Your job title says "software engineer", but you seem to spend most of your time in meetings. You'd like to have time to code, but nobody else is onboarding the junior engineers, updating the roadmap, talking to the users, noticing the things that got dropped, asking questions on design documents, and making sure that everyone's going roughly in the same direction. If you stop doing those things, the team won't be as successful. But now someone's suggesting that you might be happier in a less technical role. If this describes you, congratulations: you're the glue. If it's not, have you thought about who is filling this role on your team?

Every senior person in an organisation should be aware of the less glamorous - and often less-promotable - work that needs to happen to make a team successful. Managed deliberately, glue work demonstrates and builds strong technical leadership skills. Left unconscious, it can be extremely career limiting. It pushes people into less technical roles and even out of the industry.