Before you can evaluate a method, you have to understand its goals. Before you can evaluate a style of software engineering, you have to understand its goals. Quick execution of experiments? Rapid scaling in the face of unexpected bottlenecks? Sustained, profitable growth? Each goals requires a different style and yet we talk about software engineering as if it should be one thing.This talk introduces 3X and the ways software development, quality assurance, design, management, financing, planning, and staffing change depending on the goal of development.

Does TDD apply to infrastructure as code? Can you continuously deploy to a data lake?

As software engineers in this post-agile and post-devops industry we have a much much larger surface area of technology to take care of. To ship a feature we often touch everything from application code to data pipelines to infrastructure and operational tooling. The tools and platforms we use are changing rapidly. As we race towards every new set of technologies and techniques, we’re required to learn how to make use of it safely and effectively. In this talk, we will explore how a core set of engineering values and practices apply in an enduring way, illustrated with practical examples.

How much money would you save if AI could detect and fix your outages as soon as they happen? In a multi-billion dollar business, outages are very expensive. MTTR has a direct effect on the bottom-line, so every second counts in resolving issues. But with millions of metrics being generated by thousands of microservices, how do you choose which metrics to pay attention to? How do you make your alerts meaningful to avoid alert fatigue and desensitisation? How do you respond to those alerts in a timely manner?

In this talk, Matt covers how Expedia is using Machine Learning to "close the loop" involved in detecting, diagnosing and remediating outages post-release. You will learn about how to use ML to build models for anomaly detection in metrics. You will also learn about "ML-Ops" and how to build a platform for training and deploying ML models.

To be competitive today organizations need to optimize for time to value using continuous delivery, know how to build efficient and scalable cloud native serverless applications, and use chaos engineering to ensure strategic workloads are extremely resilient. This talk will cover current best practices in all these areas, based on personal experiences and conversations with organizations around the world over the last few years.

Adrian has a unique experience as an expert in Cloud Architecture gained from his work at eBay, Netflix, through Netflix OSS, working with startups and enterprises at Battery Ventures, and most recently as VP Architecture at AWS. In this workshop, Adrian will share his experience and advice on building cloud-native enterprise solutions. The workshop looks at the business and technology of moving an enterprise to the cloud. Adrian discusses the major challenges of scaling in particular fault tolerance, resilience and security as more and more major regulated businesses transition to the cloud.

Hey, yep, Hi — it’s me again! Your friendly neighbourhood accessibility advocate.In this talk, I’m gonna take a break from aria-labels, alt-tags, and screen-reader demos.

Don't get me wrong, that stuff is still important and needs to be shared as widely as possible, but, you see, I seem to have uncovered bigger problems. One of them is that basic human rights is hard to assign story points to, and we all know what happens to un-estimated stories during Sprint Planning!

There seems to be a bit of a misconception that the responsibility of accessibility falls on the shoulders of the front-end engineer or UX designer. In reality, true accessibility, and inclusivity, goes much deeper than text size and colour contrast.

In this talk, I’m going to show you how accessibility helps you print money. Nope, we’re not going to launch a new cryptocurrency, but you are leaving money on the table by locking potential customers out of your product.

I am going to talk numbers - how measurable and tangible returns can be made from an investment in accessibility and inclusion. Plus how to think about accessibility at every layer of your stack and how to build it into your workplace culture.

Over the last 9 years, REA's native mobile development has grown from a small team off to the side to an important company-wide channel. In a world where almost every new product needs a presence in our mobile apps, we've been making changes to allow us to build for mobile at scale.REA has effectively scaled technology through practices like microservices, micro frontends and continuous delivery. While these all look different for mobile apps, there are elements of each that we have adapted and applied with good effect. We are applying a software architecture, as well as building out mobile platform capability to help us effectively deliver new mobile experiences weekly with many independent teams involved.

As we level up in technical roles, often we find ourselves thrust into team leadership and management. This sneaks up on us and we can be left without the skills to adequately understand, engage with and lead our teams. This inevitably has a negative effect on our teams and this effect is multiplied as you scale.

What if we could reach into our toolbox that we use to understand technical problems – software architecture and distributed systems theory – to help us understand our teams? Could we learn to better manage people through this metaphor? We will explore the dynamics of teams and how they map to our understanding of distributed systems. Using this understanding we can apply distributed systems theory to help unpick some of the dynamics of our teams and how to optimise them for scale.

From communication to culture, we will break down the components of our distributed system and see what makes it tick using things like CAP Theorem and the 8 Fallacies of Distributed Systems. You will walk away with some tools to help understand your team, and set yourself up for successful scaling.

No organization ever complained that their IT department was delivering too fast. However, as technologies evolve ever more quickly and product cycle times keep shorting, it’s difficult for any development team or IT organization to be fast enough.

As these organizations try many things to move faster, from adopting Lean and Devops approaches, moving to the cloud, to working weekends or paying bigger bonuses. Slowly many of them realize that increasing velocity is about more than just moving a bit faster. It takes a fundamentally different mindset – one that looks at the first derivative.

This talk takes a fresh look why moving faster isn’t just about speeding things up and dissects both systems and organizational architectures that are built for economies of speed.

Why just migrate your existing infrastructure to the Cloud when you can remove it entirely? Serverless computing is very much the new Shiny, and proponents argue that it allows companies to focus more on their users as well as the features and business logic that are important to them. Kris was a serverless skeptic who embarked on a project last year to convert an existing server-based application to run on AWS’s Lambda. She’ll share lessons learned from that project as well as general patterns, lessons, best practices, and pitfalls that are applicable to all serverless platforms. If your skepticism has been holding you back from implementing serverless in production, this talk aims to convert you!

Programming languages are repeatedly touted to have strange edge cases. Footguns. Wats. The canonical ‘wat’ talk shows some of these for Ruby and JavaScript, but doesn’t go into any detail into the ‘why’.

In this talk, take a tour through a multitude of programming languages; and see not only the ‘wat’, but the ‘why’: is it a misunderstanding based on an assumption from another programming language? A compiler optimisation? A known bug that can’t be fixed due to backward compatibility concerns? Attendees will come away from this talk with a greater understanding about how to turn a ‘wat’ into a ‘why’.

Enterprises need to deliver better software faster. It’s no longer sufficient to release quarterly or even monthly. Instead, organizations must use methods, such as DevOps, to frequently deploy changes into production, perhaps as often as multiple times per day. One obstacle, however, to DevOps-style development is that organizations are often mired in monolithic hell. Key business applications are large, complex, unwieldy monoliths, and so it’s impossible to rapidly and safely deploy changes.

The solution is to adopt the microservice architecture, which is an architectural style that has the testability and deployability necessary for DevOps. In this 1 day workshop, you will learn about the the microservice architecture, its benefits and drawbacks and how to get started.

The microservice architecture is becoming increasing important. But what is it exactly? Why should you care about microservices? And, what do you need to do to ensure that your organization uses the microservice architecture successfully? In this talk, I’ll answer these and other questions using shapes as visual metaphors. You will learn about the motivations for the microservice architecture and why simply adopting microservices is insufficient. I describe essential characteristics of microservices, You will learn how a successful microservice architecture consist of loosely coupled services with stable APIs that communicate asynchronous. I will cover strategies for effectively testing microservices.

This is a hands-on in-depth training for everything Scrum. Basics of Agile and Scrum will be examined at the beginning of the training class, and afterwards, we’ll deep dive right into Scrum’s profundities. We’ll explore all of the essential Scrum values, principles, and elements. We’ll also cover important related topics, such as leadership, coaching, and team dynamics. If you’re already determined to change your team, department, or organisation with Scrum, this class is for you.

Even if organisations try to follow most of the Agile values and principles, they most often neglect sustainable pace as a substantial part of being Agile. Unhappy, stressed out, overworked and exhausted people are the result. And it's getting worse: Australians worked on average an extra 6 hours per week in 2018, an increase of 1.4 hours since 2016.

It makes a difference to be aware of what unsustainable pace looks like; why organisations insist on doing it, even though it doesn't make sense economically; what the causes and effects are; how bad the situation really is; and how an effort to achieve sustainable pace could pay off big time. Agility is not achieved by organisations because of working unsustainably, but—on the contrary!—because of striving towards sustainable pace.

Sprint after sprint after sprint? Burning the midnight oil? Competitive company culture? Always available thanks to tech? No focus thanks to distractions? It's a trap to think that this is good or necessary. It is not. Treating sustainable pace as a first principle in an Agile context again wins in the long run over any attempts to taking short-cuts aiming for short-termed gains.

Microservices and serverless functions have become mainstream now. Writing and deploying small, independent applications has many benefits, but on the downside, it increases the number of integration points, which increases the amount of integration testing required. How can we be confident that all our services will work correctly together, without being burdened by increasingly complex and brittle integration tests? Learn how Pact solves this problem by using consumer driven contracts, allowing you to escape Integration Testing Hell and ship your code with speed and confidence.

Microservices have become mainstream now. Writing and deploying small, independent services has many benefits, but on the downside, it increases the number of integration points, which increases the amount of integration testing required. How can we be confident that all our services will work correctly together, without being burdened by increasingly complex and brittle integration tests? Learn how Pact solves this problem by using consumer driven contracts, allowing you to escape Integration Testing Hell and ship your code with speed and confidence.

This workshop will equip you with the essential knowledge and practical skills to test synchronous and asynchronous APIs with Pact - a tool that implements contract testing - on your next project so you can ditch those lengthly end-to-end tests and deploy faster and with greater confidence.

A Programmer's Guide to Sound is a gentle introduction to digital signal processing with a focus on audio applications. With the goal or live-coding a "classic" sound synthesizer this Programmer's Guide focuses on the pragmatic application of DSP theory to digital audio practice. For the grand finale our working synthesizer will be tested against a selection of synth classics!

Distributed and concurrent systems can be considered a social group which collaborate to achieve collective goals. In order to collaborate a system of rules must be applied that affords good hygiene, fault tolerance, and effective communication to coordinate, share knowledge, and provide feedback in a trusted manner. These rules form a number of protocols which enable the group to act as a system that is greater than the sum of the individual components.

In this talk we will explore the history of protocols and their application when building distributed systems. Protocols provide the foundation on which the quality attributes are delivered. Qualities such as performance, resilience, and security.