YOW! 2013 Experience

Computing Like the Brain: The Path to Machine Intelligence

Safety Not Guaranteed: How Successful Teams Ignore the Rules to Create Successful Products (AGILE)

Refactoring Legacy Codebases (AGILE)

  • Working Effectively with Legacy Code – http://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052
  • Collective code ownership – you can refactor other people’s code
  • Questions to ask before doing so
    • What are you going to refactor?
    • Why now?
    • What can it impact?
  • Code smell
  • Try to switch to new systems
  • Use good naming for methods & variables
  • Everyone can refactor
  • Make DTOs immutable
  • Use version control
  • Use automated testing
  • Code should be self-documented
  • Embrace function

Five Years of DevOps: Where are we Now? (DEVOPS)

Where we were?

Where are we now?

Problems to be solved

  • The paradox of automation
  • The legacy organization

What’s next?

Devops Modelling (Theory, Practice and Caveats) (DevOps)

Cloud Native Architecture at Netflix (Cloud)

  • No plans to roll out service in Australia
  • Rolling out to many countries in Europe
  • Start producing its own original content 
  • Plan to stream 4k content in 2014
  • Ability to scale up and down and peak and off-peak time
  • Treat machines as herds
  • Roll out software in regions (I think (1) Europe (2) East Coast and then (3) West Coast))
  • Start open source in 2012
  • Objectives – Scale, Availability, Efficiency, Agility
  • Anti-fragility – Systems need to have stress
  • High-trust organization 
  • Sharing culture
  • Responsible what you wrote. Dev get a call at 3 AM if the code breaks.
  • http://www.amazon.com/The-Phoenix-Project-Helping-Business/dp/0988262592 #book
  • Traditional IT systems need (1) Reliable hardware (2) Stable/tested software
  • Scale breaks hardware. Speed breaks software. Speed at scale break everything!
  • Fine grains of hardware / services / hosts –  Micro-service = One server does one thing
  • http://www.slideshare.net/adrianco
  • Developer self-service = Access + Responsibilities
  • IT as a cloud API (DevOps Automation)
  • GitHub everything 
  • Just do it! No meeting to synchronize
  • Scryer engine – http://techblog.netflix.com/2013/11/scryer-netflixs-predictive-auto-scaling.html
  • Suro event pipeline –  https://github.com/Netflix/suro
  • GitHub is your “App store” and resume’

Move Fast and Ship Things (Cloud, f Culture)


  • The conference really creates technical awareness
  • Suncorp should present something to promote the company
  • Good change to build networking with Brisbane / Global developers

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s