YOW! 2019 Brisbane Day 1

Mon, Dec 9
Timezone: Australia/Brisbane (AEST)
08:00

    Registration for YOW! Brisbane 2019 - 45 mins

08:45

    Session Overviews and Introductions - 15 mins

09:00
  • Added to My Schedule
    keyboard_arrow_down
    Gene Kim

    Gene Kim - The Unicorn Project And The Five Ideals

    schedule  09:00 - 10:00 AM place Plaza Auditorium people 400 Interested star_halfRate

    It is impossible to overstate how much I’ve learned since co-authoring The Phoenix Project, DevOps Handbook, and Accelerate. I’m so excited that after years of work, The Unicorn Project will be published later this year.

    This book is my attempt to frame what I’ve learned studying technology leaders adopting DevOps principles and patterns in large, complex organizations, often having to fight deeply entrenched orthodoxies. And yet, despite huge obstacles, they create incredibly effective and innovative teams that create beacons of greatness that inspire us all.
    In this book, we follow a senior lead developer and architect as she is exiled to the Phoenix Project, to the horror of her friends and colleagues, as punishment for contributing to a payroll outage. She tries to survive in what feels like a heartless and uncaring bureaucracy, forced to work within a system where no one can get anything done without endless committees, paperwork, change requests, and approvals. Decades of technical debt make even small changes difficult or impossible, often causing catastrophic outcomes and fear of punishment.
    I get tremendous delight and gratification that this book is not about the bridge crew of the Starship Enterprise -- instead, it is about redshirt engineers, which as it turns out, whose heroic work matters most to the long-term survival of almost every organization.
    In my previous books, I’ve focused on principles and practices (e.g., Three Ways, Four Types of Work). However, I’ve always wanted to describe the spectrum of cultural, experiential and value decisions we make that either enable greatness or create chronic suffering and underperformance. They are currently as follows:
    • The First Ideal — Locality and Simplicity
    • The Second Ideal — Focus, Flow and Joy
    • The Third Ideal — Improvement of Daily Work
    • The Fourth Ideal — Psychological Safety
    • The Fifth Ideal — Customer Focus
10:00

    Morning Tea - 30 mins

10:30
  • Added to My Schedule
    keyboard_arrow_down
    James Shore

    James Shore - Evolutionary Design Animated

    schedule  10:30 - 11:20 AM place Red Room people 180 Interested star_halfRate

    Modern software development welcomes changing requirements, even late in the process, but how can we write our software so that those changes don’t create a mess? Evolutionary design is the key. It’s a technique that emerges from Extreme Programming, the method that brought us test-driven development, merciless refactoring, and continuous integration. James Shore first encountered Extreme Programming and evolutionary design nearly 20 years ago. Initially skeptical, he’s explored its boundaries ever since. In this session, James will share what he’s learned through in-depth animations of real software projects. You’ll see how designs evolve over time and you’ll learn how and when to use evolutionary design for your own projects.

  • Added to My Schedule
    keyboard_arrow_down
    Aino Corry

    Aino Corry - Retrospective Antipatterns

    schedule  10:30 - 11:20 AM place Green Room people 169 Interested star_halfRate

    Anti-Patterns are like patterns, only more informative. With anti-patterns you will first see what patterns reoccur in "bad" retrospectives and then you will see how to avoid, or remedy, the situation.

    Based on her experience with facilitating retrospectives, join Aino for an entertaining and informative presentation on the anti-patterns she has seen and how to overcome the problems. She gave the first version of this talk at YOW! 2014, and since then she has identified more and this talk will be interesting for everyone facilitating any kind of meeting, with retrospectives in focus.

  • Added to My Schedule
    keyboard_arrow_down
    Larene Le Gassick

    Larene Le Gassick - Full Stack Accessibility, and the Business Case for Inclusion

    schedule  10:30 - 11:20 AM place Blue Room people 89 Interested star_halfRate

    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.

11:30
12:20

    Lunch - 60 mins

13:20
14:20
15:10

    Afternoon tea - 30 mins

15:40
16:40
  • Added to My Schedule
    keyboard_arrow_down
    Edith Harbaugh

    Edith Harbaugh - Mistakes were made - Patterns & Anti-Patterns For Effective Feature Flagging

    schedule  04:40 - 05:30 PM place Red Room people 198 Interested star_halfRate

    Feature flags are a valuable DevOps technique to deliver better, more reliable software faster. Feature flags can be used for both release management (dark launches, canary rollouts, betas) as well as long term control (entitlement management, user segmentation personalization). However, if not managed properly, feature flags can be very destructive technical debt. We'll discuss patterns & anti-patterns for effective feature flag management.

  • Added to My Schedule
    keyboard_arrow_down
    Ken Scambler

    Ken Scambler - Grow your own tech leads

    schedule  04:40 - 05:30 PM place Green Room people 98 Interested star_halfRate

    Great technical leaders don't grow on trees - but they can be grown in-house all the same. This can be an important source of opportunity, learning and satisfaction for team members, and dramatically improve retention. However, there are specific things that can be done to make this process smoother - and a multitude of ways to make it fail. There is a real and underappreciated art not just to being a great technical leader, but giving new ones the tools, the space -- and the constraints -- they need to thrive.

    We'll look at the ways that architects, tech leads and managers can succeed or fail to help grow new technical leaders without excluding underrepresented folks, and a raft of actionable ideas for aspiring tech leads to take on board.

  • Added to My Schedule
    keyboard_arrow_down
    Josh Long

    Josh Long - The Reactive Revolution

    schedule  04:40 - 05:30 PM place Blue Room people 57 Interested star_halfRate

    Microservices and big-data increasingly confront us with the limitations of traditional input/output. In traditional IO, work that is IO-bound dominates threads. This wouldn't be such a big deal if we could add more threads cheaply, but threads are expensive on the JVM, and most other platforms. Even if threads were cheap and infinitely scalable, we'd still be confronted with the faulty nature of networks. Things break, and they often do so in subtle, but non-exceptional ways. Traditional approaches to integration bury the faulty nature of networks behind overly simplifying abstractions. We need something better.

    Spring Framework 5 is here! It introduces the Spring developer to a growing world of support for reactive programming across the Spring portfolio, starting with a new Netty-based web runtime, component model and module called Spring WebFlux, and then continuing to Spring Data Kay, Spring Security 5.0, Spring Boot 2.0 and Spring Cloud Finchley. Sure, it sounds like a lot, but don't worry! Join me, your guide, Spring developer advocate Josh Long, and we'll explore the wacky, wonderful world of Reactive Spring together.

17:45
  • Added to My Schedule
    keyboard_arrow_down
    Sabine Hauert

    Sabine Hauert - Swarm Engineering Across Scales: From Robots To Nanomedicine

    schedule  05:45 - 06:45 PM place Plaza Auditorium people 222 Interested star_halfRate

    Birds do it, bees do it. Even ants and fish in the sea do it. When certain individuals group together, they create a “swarm intelligence”— a collective brain capable of solving complex problems which would be insurmountable for an isolated individual. In the world of artificial intelligence, swarm engineering allows us to make robots that work in large numbers (under 1000), and tiny sizes (under 1 cm). Swarm strategies are either inspired from nature (ant colonies, fish shoals, bird flocks, cellular systems) or are automatically discovered using machine learning and crowdsourcing. Demonstrated applications range from the deployment of swarms of flying robots to create outdoor communication networks, or the use of 1000 coin-sized robots to form structures and explore the environment, to the design of nanoparticles for cancer treatment.

18:45

    Reception - 60 mins

YOW! 2019 Brisbane Day 2

Tue, Dec 10
Timezone: Australia/Brisbane (AEST)
08:45

    Session Overviews and Introductions - 15 mins

09:00
10:00

    Morning Tea - 30 mins

10:30
  • Added to My Schedule
    keyboard_arrow_down
    Casey Rosenthal

    Casey Rosenthal - Evolving Chaos Engineering

    schedule  10:30 - 11:20 AM place Red Room people 181 Interested star_halfRate

    Almost five years ago I published at manifesto of sorts at https://principlesofchaos.org to define a new discipline in software engineering called Chaos Engineering. It wasn’t about creating chaos, but rather identifying the chaos inherent in a complex system. The other practices that commonly address availability (incident management, alerting, monitoring, disaster recovery, etc) are all reactive: they focus on time to detect, and time to remediate. Chaos Engineering on the other hand is proactive: finding systemic vulnerabilities before they affect customers. Now that Chaos Engineering has high adoption at big tech companies and non-digital native orgs alike, we can look at how the practice is maturing. Our knowledge of systemic properties of complex systems is improving and leading us into a new era of Continuous Verification.

  • Added to My Schedule
    keyboard_arrow_down
    Matthew Keesan

    Matthew Keesan - Quantum Computing and You

    schedule  10:30 - 11:20 AM place Green Room people 159 Interested star_halfRate

    Richard Feynman proposed harnessing quantum systems for computational power in a thought experiment almost forty years ago. In October, a quantum computer achieved in minutes what the world's most powerful classical supercomputer would take days to compute. Soon, quantum computers will be able to perform calculations that will never* be solvable classically.

    Yet in spite of their power, programming these devices has remained largely the province of theoretical physicists. Have you ever wondered how quantum computers work, or what's up with quantum mechanics, anyway? This talk will provide an introduction to quantum computing and quantum information science, the state of the field today, where it's headed, how it will affect us all, and how you can get involved. We'll write a simple quantum program together and turn on lasers thousands of miles away to make atoms do math.

    *All bets are off if P=NP.

  • Added to My Schedule
    keyboard_arrow_down
    Jennifer Scheurle

    Jennifer Scheurle - A Game Designer Walks Into NASA Astronaut Training: What Other Industries Can Learn From Us

    schedule  10:30 - 11:20 AM place Blue Room people 111 Interested star_halfRate

    A Game Designer walks into NASA Astronaut Training: What other industries can learn from us
    In 2016, a NASA engineer found screenshots of a technical virtual reality demo of a potential astronaut game on a Reddit forum and decided to contact the developers to discuss how game developers can help train astronauts for the next missions into space. In the upcoming two years, NASA worked closely with said game developer to introduce new and innovative techniques to virtual astronaut training.
    My name is Jennifer Scheurle and I'm a game designer. For many years, my industry has been largely isolated from other fields despite our intricate knowledge of UX, behavioural psychology and how to teach players complex and difficult systems and concepts. Games have one of the most unique parameters of an interactive experience in existence. They need to keep people interested for many, many and they need to do so with millions of different kinds of people to be successful. It is an opportunity to expose a large group of people to ideas in the most personal and compelling way imaginable. Game design has cracked the code for how to engage people deeply and thoroughly in experiences completely new and alien to them - for better or worse.

    In this talk, we will walk through how game designers think about problems, how we use behavioural psychology to guide our users and why designing with heart and compassion is your key to reach and compel the masses.

11:30
12:20

    Lunch - 60 mins

13:20
  • Added to My Schedule
    keyboard_arrow_down
    Sarah Wells

    Sarah Wells - Mature microservices and how to operate them

    schedule  01:20 - 02:10 PM place Red Room people 177 Interested star_halfRate

    At the Financial Times, we built our first microservices in 2013. We like a microservices-based approach, because by breaking up the system into lots of independently deployable services - making releases small, quick and reversible - we can deliver more value, more quickly, to our customers and we can run hundreds of experiments a year.

    This approach has had a big - and positive - impact on our culture. However, it is much more challenging to operate.

    So how do we go about building stable, resilient systems from microservices? And how do we make sure we can fix any problems as quickly as possible?

    I'll talk about building necessary operational capabilities in from the start: how monitoring can help you work out when something has gone wrong and how observability tools like log aggregation, tracing and metrics can help you fix it as quickly as possible.

    We've also now being building microservice architectures for long enough to start to hit a whole new set of problems. Projects finish and teams move on to another part of the system, or maybe an entirely new system. So how do we reduce the risk of big issues happening once the team gets smaller and there start to be services that no-one in the team has ever touched?

    The next legacy systems are going to be microservices, not monoliths, and you need to be working now to prevent that causing a lot of pain in the future.

  • Added to My Schedule
    keyboard_arrow_down
    Lee Campbell

    Lee Campbell - Cost of a Dependency

    schedule  01:20 - 02:10 PM place Green Room people 122 Interested star_halfRate

    This presentation will challenge a common movement that is sweeping the lands unnoticed. Agile micro-service projects that live in a single VCS repository, that are slow to test, hard to understand need to be deployed and versioned as a single unit. While that sounds silly, ask these questions of your project:

    • Are you using a layered architecture?
    • Do you generally have an interface for each class (Java/.NET)?
    • Do your Views live in one folder and your ViewModels in another?
    • Has your platform’s package manager made it too easy to just add, more?
    • Has your team mistaken “reuse” as a goal, not an outcome?
    • Does your team favor living code over doco, yet no one understands how the system works?
    • Could you make a one line code change, test it, commit it, package it and deploy it in under 15min?
    • Do you think you are doing Microservices, but all the code lives in the same repo? Share the same contracts? Get versioned and deployed together? Share a data store?

    Even if you are not on the Microservices band wagon, will your framework of choice be relevant in 5 years? Can your team pivot to new libraries, GUI or data store technologies in days or weeks? Or, are you actively building the next legacy project churn-and-burn style?

    This session will pose some challenges to prevailing convention and ask how did we get here. More importantly we will discover the costs of our decisions and how we start applying an engineering instead of religious approach to design.

  • Added to My Schedule
    keyboard_arrow_down
    Michael Hunger

    Michael Hunger - How Graphs Help Investigative Journalist to Connect the Dots

    schedule  01:20 - 02:10 PM place Blue Room people 118 Interested star_halfRate

    The Journalists of the ICIJ used graph technology to understand the relationships between the leaked pieces of information in the Panama and Paradise Papers.

    NBC News applied graph algorithms to the messages and follower networks of Russian Twitter trolls to gain further insights.

    The Trumpworld organizational data correlated with US bills and government contracts offers starting points for further investigations.

    New tools like graph databases allow data journalists to understand the intricate networks of the criminal, economic and political world better as those three examples show. Each journalist adding new connections helps others to validate their stories. They say "It's like magic".

    Join Michael for a look behind the scenes of graph based data ingestion, analysis and investigation.

    We will use the open source graph database Neo4j, data visualization and graph algorithms to read between the lines.

14:20
  • Added to My Schedule
    keyboard_arrow_down
    John Le Drew

    John Le Drew - Once Upon A Time In Agile

    schedule  02:20 - 03:10 PM place Red Room people 127 Interested star_halfRate

    Stories are the foundation of human experience. They are what define us, individually and collectively. They engage us, entertain us, bring us together and drive us apart.

    What stories do you tell about you? Who knows your stories? Everyone? Perhaps just a select few? Maybe, just you.

    In this session, we explore how our individual journeys to self-acceptance and alignment are also the heart of how we can work with and support teams. We will learn about how to truly help teams move towards agility, by helping them find and own their process and tell their own story. So they stay aligned and can continually realign when their context changes.

    Why authenticity and self-acceptance matters for both individuals and teams.
    How to create lasting change in teams, without imposing process or creating learned helplessness.

    How to help teams own their process and tell their own story.

    Over the last 20 years, John has helped countless teams. But in the last 3 years, when his world was turned upside down, he realised that changing a team is exactly what gets in the way of a team changing.

  • Added to My Schedule
    keyboard_arrow_down
    Cat Swetel

    Cat Swetel - 193 Easy Steps to DevOpsing Your Monolith

    schedule  02:20 - 03:10 PM place Green Room people 183 Interested star_halfRate

    Is it possible to enable the evolution of a monolith? After a hugely expensive (financially and culturally) failed attempt at a complete rewrite, Ticketmaster is attempting to do just that, bounce back and evolve the monolith that is Ticketmaster’s core ticketing platform. This multi-year effort requires striking a delicate balance between showing appropriate respect for the platform’s highly profitable 40 plus year history while not allowing past success to blind us to demands of a highly dynamic market of fans, artists, venues, and more. This is not a session about best practices for developing your monolith; this session is the true (and at times ugly) story of one company’s journey towards a more flexible, adaptable, and easily maintainable architecture supported by a culture that prizes learning and respect above all else.

  • Added to My Schedule
    keyboard_arrow_down
    Juliet Hougland

    Juliet Hougland - How to Experiment Quickly

    schedule  02:20 - 03:10 PM place Blue Room people 114 Interested star_halfRate

    The ‘science’ in data science refers to the underlying philosophy that you don’t know what works for your business until you make changes and rigorously measure impact. Rapid experimentation is a fundamental characteristic of high functioning data science teams. They experiment with models, business processes, user interfaces, marketing strategies, and anything else they can get their hands on. In this talk I will discuss what data platform tooling and organisational designs support rapid experimentation in data science teams.

15:10

    Afternoon tea - 30 mins

15:40
16:45
  • Added to My Schedule
    keyboard_arrow_down
    Troy Hunt

    Troy Hunt - Rise of the Breaches

    schedule  04:45 - 05:45 PM place Plaza Auditorium people 273 Interested star_halfRate

    Data breaches are the new normal. We’ve created ecosystems with so many moving parts and so
    many complex units, it’s little wonder that we so frequently see them go wrong. A combination of
    more systems, more people, more devices and more ways than ever of producing and publishing
    data stack the odds in favour of attackers breaching more systems than ever.

    In this talk, you’ll get a look inside the world of data breaches based on my experiences dealing with
    billions of breached records. You’ll see what’s motivating hackers, how they’re gaining access to data
    and how organisations are dealing with the aftermath of attacks. Most importantly, it will help you
    contextualise these incidents and understand both what these attacks actually look like and how to
    defend against them in your organisation.

17:45

    Closing Drinks - 60 mins