filter_list help_outline
  • Liked Dave Thomas
    keyboard_arrow_down

    Dave Thomas - Legacy Evolution – The Innovation Opportunity! (Sydney)

    Dave Thomas
    Dave Thomas
    Chief Scientist
    CSO Kx Systems
    schedule 6 months ago
    Sold Out!
    60 Mins
    Workshop
    Advanced

    Every successful business is powered by legacy technology and applications which need to evolve. Vendors, Consultants and New Tech Enthusiasts bemoan technical debt and have the answer – Switch to Our Technology, Outsource, Use a New Language/Platform. Each of these options comes with major business and technical risks and expenses, along with long uncertain delivery dates.

    In this talk we describe an alternative lean approach to legacy evolution that focuses on high value near-term tactical business and technical innovations. We focus on data rather than code. Code has been the primary focus for traditional legacy approaches. We illustrate common patterns for identifying high return opportunities and techniques for high payback. We discuss risk mitigation and management buy-in for innovative approaches.

    Technical Debt | Innovation | Targeted Technology Adoption | Accelerated Development | Data Driven

  • Liked Dave Thomas
    keyboard_arrow_down

    Dave Thomas - Legacy Evolution – The Innovation Opportunity! (Perth)

    Dave Thomas
    Dave Thomas
    Chief Scientist
    CSO Kx Systems
    schedule 6 months ago
    Sold Out!
    60 Mins
    Workshop
    Advanced

    Every successful business is powered by legacy technology and applications which need to evolve. Vendors, Consultants and New Tech Enthusiasts bemoan technical debt and have the answer – Switch to Our Technology, Outsource, Use a New Language/Platform. Each of these options comes with major business and technical risks and expenses, along with long uncertain delivery dates.

    In this talk we describe an alternative lean approach to legacy evolution that focuses on high value near-term tactical business and technical innovations. We focus on data rather than code. Code has been the primary focus for traditional legacy approaches. We illustrate common patterns for identifying high return opportunities and techniques for high payback. We discuss risk mitigation and management buy-in for innovative approaches.

    Technical Debt | Innovation | Targeted Technology Adoption | Accelerated Development | Data Driven

  • Liked Sam Aaron
    keyboard_arrow_down

    Sam Aaron - Live Coding the intersection between the Arts, Technology and Research (Perth)

    60 Mins
    Workshop
    Advanced

    Live Coding systems encourage us to think extremely differently about programming languages. In addition to considering standard requirements such as reliability, efficiency and correctness we are also forced to deal with issues such as liveness, coordination and synchronization all whilst working in real time.

    Live Coders not only run and modify our code live — they often performing with it live on stage in front of large crowds of people who really don’t want the code to miss a beat. In this code and demo-heavy talk, Sam will introduce the motivation for Sonic Pi – a system designed specifically for live coding music – before taking a deep technical dive into the internal ideas and innovations. The audience will explore Sonic Pi’s novel temporal semantics which allows multiple concurrent threads to execute in synchronization whilst still allowing live hot-swapping of code.

    Ultimately, everyone will discover an exciting an exciting area of programming language research in an approachable and instructive manner all whilst making some sick beats and drops.

  • Liked Dave West
    keyboard_arrow_down

    Dave West - ScrumOps – Making Agile and DevOps work to build the 21 st century product delivery organization (Melbourne)

    Dave West
    Dave West
    Product Owner
    Scrum.org
    schedule 1 week ago
    Sold Out!
    60 Mins
    Workshop
    Advanced

    The Software delivery community is famous for creating new initiatives as the next silver bullet. OOP, CMMI, Spiral, Iterative, RUP, RAD are just some of the trends that have challenged how people approach the discipline of delivering software. Now it is agile and DevOps. Or should I say, it was Agile and now it is DevOps? The Agile movement, named February 2001 focused organizations on empowering teams and working in an empirical way. DevOps, started in 2009 and focuses on holistic system thinking and automation to remove waste and better connect development and operations. Both movements focus on delivering an improved delivery capability, but they approach it differently. Automation vs people, process vs empowerment. Are they different? Should organizations focus on one or another in trying to deliver more value to their customers?

    In this talk Dave West, Product Owner and CEO Scrum.org discusses how DevOps and Scrum/Agile can work effectively together to deliver improved customer value. It describes the challenges of DevOps or Scrum first, and why it is important to use the Scrum team as the foundation for DevOps maturity, and where traditional operations and IT fit.

  • Liked Dave West
    keyboard_arrow_down

    Dave West - ScrumOps – Making Agile and DevOps work to build the 21 st century product delivery organization (Sydney)

    Dave West
    Dave West
    Product Owner
    Scrum.org
    schedule 1 week ago
    Sold Out!
    60 Mins
    Workshop
    Advanced

    The Software delivery community is famous for creating new initiatives as the next silver bullet. OOP, CMMI, Spiral, Iterative, RUP, RAD are just some of the trends that have challenged how people approach the discipline of delivering software. Now it is agile and DevOps. Or should I say, it was Agile and now it is DevOps? The Agile movement, named February 2001 focused organizations on empowering teams and working in an empirical way. DevOps, started in 2009 and focuses on holistic system thinking and automation to remove waste and better connect development and operations. Both movements focus on delivering an improved delivery capability, but they approach it differently. Automation vs people, process vs empowerment. Are they different? Should organizations focus on one or another in trying to deliver more value to their customers?

    In this talk Dave West, Product Owner and CEO Scrum.org discusses how DevOps and Scrum/Agile can work effectively together to deliver improved customer value. It describes the challenges of DevOps or Scrum first, and why it is important to use the Scrum team as the foundation for DevOps maturity, and where traditional operations and IT fit.

  • Liked Michael Nygard
    keyboard_arrow_down

    Michael Nygard - Grinding the Java Monolith

    60 Mins
    Workshop
    Advanced

    Microservices sound appealing, but what can we do with those ten-million-line Java code bases? Shared domain objects, horizontal coupling, and years of boundary erosion have left us with enormous complexity and spiderwebs of coupling. Michael will share techniques at various levels of abstraction, from implementation details to API design and responsibility allocation. There’s no silver bullet that will make it easy to decompose a monolith, but you’ll learn some techniques that have helped and some pitfalls to avoid.

  • Liked Sebastian von Conrad
    keyboard_arrow_down

    Sebastian von Conrad - Go Back to the Future with Event Sourcing and CQRS (Singapore)

    60 Mins
    Workshop
    Advanced

    Event Sourcing is an approach to building software with a long track record of success. By placing business concepts at the heart of our code, we can decouple systems into small services that can be quickly built, changed, and replaced. Although Event Sourcing has been around for many years, it remains outside the mainstream paradigm of software development–much to our detriment.

    With Event Sourcing, we place the highest value on the simple capture of essential business events without attempting to interpret them. We can then relegate all interpretations of those events to subsystems that are easy to build, change, and replace when necessary. The resulting systems have single responsibilities and are decoupled from each other, which makes them simple to modify. Event Sourcing can enable us to move faster by supporting rapid experimentation with new perspectives, new user interactions, and new insights into our business.

    Event Sourcing is agnostic of technology stack and language style, but it goes well with another pattern called CQRS: Command Query Responsibility Segregation. In this talk, we will do a deep-dive into both of these two patterns and discuss:

    What is Event Sourcing, and how does it differ from systems designed around current state.
    Interpreting Events into denormalised projections for very fast reads (Queries).
    Receiving and validating Commands that, if successful, result in new Events.
    Single responsibility services for reacting to Events by creating other events and, if necessary, triggering external behaviour.
    We will cover the advantages of the pattern, to give us an idea for when and why it makes sense to use it. But it isn’t a silver bullet, and we will also talk about its disadvantages, including the most commonly mentioned downside: eventual consistency, and how we can deal with it.

  • Liked Sebastian von Conrad
    keyboard_arrow_down

    Sebastian von Conrad - Go Back to the Future with Event Sourcing and CQRS (Hong Kong)

    60 Mins
    Workshop
    Advanced

    Event Sourcing is an approach to building software with a long track record of success. By placing business concepts at the heart of our code, we can decouple systems into small services that can be quickly built, changed, and replaced. Although Event Sourcing has been around for many years, it remains outside the mainstream paradigm of software development–much to our detriment.

    With Event Sourcing, we place the highest value on the simple capture of essential business events without attempting to interpret them. We can then relegate all interpretations of those events to subsystems that are easy to build, change, and replace when necessary. The resulting systems have single responsibilities and are decoupled from each other, which makes them simple to modify. Event Sourcing can enable us to move faster by supporting rapid experimentation with new perspectives, new user interactions, and new insights into our business.

    Event Sourcing is agnostic of technology stack and language style, but it goes well with another pattern called CQRS: Command Query Responsibility Segregation. In this talk, we will do a deep-dive into both of these two patterns and discuss:

    What is Event Sourcing, and how does it differ from systems designed around current state.
    Interpreting Events into denormalised projections for very fast reads (Queries).
    Receiving and validating Commands that, if successful, result in new Events.
    Single responsibility services for reacting to Events by creating other events and, if necessary, triggering external behaviour.
    We will cover the advantages of the pattern, to give us an idea for when and why it makes sense to use it. But it isn’t a silver bullet, and we will also talk about its disadvantages, including the most commonly mentioned downside: eventual consistency, and how we can deal with it.

  • Liked Sebastian von Conrad
    keyboard_arrow_down

    Sebastian von Conrad - Go Back to the Future with Event Sourcing and CQRS (Perth)

    60 Mins
    Workshop
    Advanced

    Event Sourcing is an approach to building software with a long track record of success. By placing business concepts at the heart of our code, we can decouple systems into small services that can be quickly built, changed, and replaced. Although Event Sourcing has been around for many years, it remains outside the mainstream paradigm of software development–much to our detriment.

    With Event Sourcing, we place the highest value on the simple capture of essential business events without attempting to interpret them. We can then relegate all interpretations of those events to subsystems that are easy to build, change, and replace when necessary. The resulting systems have single responsibilities and are decoupled from each other, which makes them simple to modify. Event Sourcing can enable us to move faster by supporting rapid experimentation with new perspectives, new user interactions, and new insights into our business.

    Event Sourcing is agnostic of technology stack and language style, but it goes well with another pattern called CQRS: Command Query Responsibility Segregation. In this talk, we will do a deep-dive into both of these two patterns and discuss:

    What is Event Sourcing, and how does it differ from systems designed around current state.
    Interpreting Events into denormalised projections for very fast reads (Queries).
    Receiving and validating Commands that, if successful, result in new Events.
    Single responsibility services for reacting to Events by creating other events and, if necessary, triggering external behaviour.
    We will cover the advantages of the pattern, to give us an idea for when and why it makes sense to use it. But it isn’t a silver bullet, and we will also talk about its disadvantages, including the most commonly mentioned downside: eventual consistency, and how we can deal with it.

  • Liked Sebastian von Conrad
    keyboard_arrow_down

    Sebastian von Conrad - Go Back to the Future with Event Sourcing and CQRS (Brisbane)

    60 Mins
    Workshop
    Advanced

    Event Sourcing is an approach to building software with a long track record of success. By placing business concepts at the heart of our code, we can decouple systems into small services that can be quickly built, changed, and replaced. Although Event Sourcing has been around for many years, it remains outside the mainstream paradigm of software development–much to our detriment.

    With Event Sourcing, we place the highest value on the simple capture of essential business events without attempting to interpret them. We can then relegate all interpretations of those events to subsystems that are easy to build, change, and replace when necessary. The resulting systems have single responsibilities and are decoupled from each other, which makes them simple to modify. Event Sourcing can enable us to move faster by supporting rapid experimentation with new perspectives, new user interactions, and new insights into our business.

    Event Sourcing is agnostic of technology stack and language style, but it goes well with another pattern called CQRS: Command Query Responsibility Segregation. In this talk, we will do a deep-dive into both of these two patterns and discuss:

    What is Event Sourcing, and how does it differ from systems designed around current state.
    Interpreting Events into denormalised projections for very fast reads (Queries).
    Receiving and validating Commands that, if successful, result in new Events.
    Single responsibility services for reacting to Events by creating other events and, if necessary, triggering external behaviour.
    We will cover the advantages of the pattern, to give us an idea for when and why it makes sense to use it. But it isn’t a silver bullet, and we will also talk about its disadvantages, including the most commonly mentioned downside: eventual consistency, and how we can deal with it.

  • Liked Sebastian von Conrad
    keyboard_arrow_down

    Sebastian von Conrad - Go Back to the Future with Event Sourcing and CQRS (Sydney)

    60 Mins
    Workshop
    Advanced

    Event Sourcing is an approach to building software with a long track record of success. By placing business concepts at the heart of our code, we can decouple systems into small services that can be quickly built, changed, and replaced. Although Event Sourcing has been around for many years, it remains outside the mainstream paradigm of software development–much to our detriment.

    With Event Sourcing, we place the highest value on the simple capture of essential business events without attempting to interpret them. We can then relegate all interpretations of those events to subsystems that are easy to build, change, and replace when necessary. The resulting systems have single responsibilities and are decoupled from each other, which makes them simple to modify. Event Sourcing can enable us to move faster by supporting rapid experimentation with new perspectives, new user interactions, and new insights into our business.

    Event Sourcing is agnostic of technology stack and language style, but it goes well with another pattern called CQRS: Command Query Responsibility Segregation. In this talk, we will do a deep-dive into both of these two patterns and discuss:

    What is Event Sourcing, and how does it differ from systems designed around current state.
    Interpreting Events into denormalised projections for very fast reads (Queries).
    Receiving and validating Commands that, if successful, result in new Events.
    Single responsibility services for reacting to Events by creating other events and, if necessary, triggering external behaviour.
    We will cover the advantages of the pattern, to give us an idea for when and why it makes sense to use it. But it isn’t a silver bullet, and we will also talk about its disadvantages, including the most commonly mentioned downside: eventual consistency, and how we can deal with it.

  • Liked Neal Ford
    keyboard_arrow_down

    Neal Ford - Stories Every Developer Should Know

    60 Mins
    Workshop
    Advanced

    Those who cannot remember the past are condemned to repeat it. –George Santayana

    The past is never dead. It’s not even past. –William Faulkner

    Most developers pursue the Latest and Greatest with intense fervor, yet the history of engineering, including software projects, contains rich lessons that we risk repeating ad nauseam. This session recounts a variety of stories of projects that failed…and why. Ranging from the Vasa in 1628 to Knight Capital in 2012, each story tells of a mistaken interpretation of some architectural fundamental principle and the consequences–some good, some less so. I also look at the common threads for these stories, which resonates with problems many companies have but don’t realize.

  • Liked Evan Leybourn
    keyboard_arrow_down

    Evan Leybourn - Certain Uncertainty (Sydney)

    60 Mins
    Workshop
    Advanced

    The world is changing more rapidly than ever before and organisations of every size are struggling to remain relevant in the eyes of their customers. The simple fact that the average lifespan of a company has decreased by more than 50 years in the last century demonstrates that not all organisations are prepared for this new reality. It is only high-performing, adaptable and agile organisations that will leverage, lead and thrive in this ambiguous and unpredictable market. We call this business agility.

    The problem with a statement like that is that there is no common definition of what business agility means. And that’s actually a good thing. In a dynamic and changing market trying to lock it down will defeat the very advantage it brings. Instead, I want you to start thinking of business agility as the common thread. An adaptable and sustainable narrative that binds & guides, rather than directs, us into the uncertain future.

    This talk will share the state of business agility around the world. We’ll look at the Domains of Business Agility, interspersed with case studies from 4 multinational organisation in both the banking and utilities sector.

  • Liked Eugenia Cheng
    keyboard_arrow_down

    Eugenia Cheng - Category Theory and Life (Brisbane)

    60 Mins
    Workshop
    Advanced

    Category theory can be thought of as being “very abstract algebra”. It is thought of as “too abstract” by some people, and as “abstract nonsense” by some others. In this talk I will show that while it is abstract, it is far from being nonsense. I will argue that the abstraction has a purpose and that broad applicability is one of the powerful consequences. To demonstrate this, I will show how I apply concepts of category theory to important questions of life such as prejudice, privilege, blame and responsibility. I will introduce the category theory concepts from scratch so no prior knowledge is needed. These concepts will include objects and morphisms, isomorphisms and universal properties.

  • No more submissions exist.
Looking for your submitted proposals. Click here.