Code ’25 Day 2 Session 2

You could almost set your watch by it: at 2pm each day, the microservice would time out and crash, the database growing increasingly slow and deadlock prone, and the SLA perilously close to being breached. Everything looked "normal" - the logs showed typical requests and responses right up until it all fell over, the metrics showed the API received more requests at other times of the day so it wasn't overwhelmed and had capacity, but something was different. Was it a noisy neighbour problem on the shared database? Something malicious not caught by the WAF? Solar flares? What was going on?! Join us on a journey into the unknown-unknowns with our guide O11y (pronounced "Ollie", short for "Observability") as we explore:

• Observability and its "three pillars"
• OpenTelemetry Tracing
• Auto- and Manual-Instrumentation
• High Cardinality, High Dimensionality, and Sampling
• Honeycomb.io's querying and trace rendering

Cyber security (or lack of) has been covered extensively in the news. Hacker attacks range from bored school kids toying around to state-sponsored ransom-driven targeted strikes. As software engineers it’s our responsibility to incorporate cyber security best practices into the development cycle. Secure by Design initiative is being adopted by more and more countries including Australia. Products designed with Secure by Design principles prioritise the security of customers as a core business requirement, rather than merely treating it as a technical feature. This session includes the list of resources, best practices, tools for designing and implementing more secure applications and to prepare for penetration testing.

At Atlassian, we take accessibility seriously enough that we have entire teams dedicated to it. There are experts on hand to provide feedback on designs, and answer questions about implementation details. There's a team that runs audits of new features before they're launched. It's honestly pretty good. But obviously not everyone has the resources available for this kind of setup. So what can you do instead? I'm going to talk you through a range of tools and processes that we use to improve the accessibility of our products, what each does well, where they fall short, and what they cost to implement. You can then use this information to figure out which solutions best fit your particular situation, and how you can get the best bang for your accessibility buck.