The 2015-06-15 Operational Insight presentation, without presenter notes (because the way Keynote handles presenter notes makes them dominate the presentation)
Operational Insight: Concepts and Examplesroyrapoport
The document proposes a framework called OODA (Observe, Orient, Decide, Act) for operational insight and discusses its implications. OODA describes a cycle that anyone performing operations goes through when making decisions. To improve at OODA, one aims to increase speed, decrease effort, and increase reliability. This involves improving observation (metrics), orientation (visualization), decisions (alerting), and automating actions. Examples demonstrate how Netflix has automated capacity decisions and canary analysis to improve according to the OODA framework.
DevOps: The Future is Already Here — It’s Just Unevenly Distributeddev2ops
The document discusses the history and evolution of DevOps. It traces how DevOps began as a grassroots movement among practitioners and led to numerous DevOps conferences starting in 2009. It also outlines how DevOps aims to break down silos between development and operations teams to improve organizational alignment, reduce lead times, and provide faster feedback. A key part of DevOps is taking an end-to-end view of application delivery and focusing on continuous integration, delivery, and deployment.
DevOps & Security from an Enterprise Toolsmith's Perspectivedev2ops
Slides from presentation by Alex Honor and Damon Edwards at DevOps Connect at RSA 2015 in San Francisco on April 20, 2015.
Abstract:
IT organizations are feeling the squeeze from seemingly conflicting business mandates. At one moment the message is “Go Go Go. DevOps, Lean Startup, Continuous Delivery… move faster and give more people access”. The next moment the message is “Be more secure. Compliance above all. Keep us out of the press!”. Damon Edwards and Alex Honor work with many enterprises who are facing these challenges. This talk is an in the trenches view of how these companies are responding and learning to go faster and be more secure.
Leveraging Your Company's DevOps Transformation (AppSec USA 2014)dev2ops
This document discusses how organizations can implement DevOps practices to improve productivity and reduce waste. It outlines some of the benefits organizations see from DevOps like shorter lead times, faster problem detection and resolution, and higher quality. It also describes how traditional silos between development, testing, and operations teams can be broken down by establishing cross-functional delivery teams aligned around customer needs. Implementing practices like continuous integration and shared responsibility for the full software development lifecycle are key aspects of the DevOps transformation discussed.
The document discusses the origins and evolution of the Plan-Do-Check-Act (PDCA) cycle, also known as the Deming cycle or Shewhart cycle. It traces the concept back to ideas of scientific experimentation in the 1600s and statistical process control methods developed in the 1920s-1940s. Key figures like Deming, Shewhart, Juran popularized applying the approach to quality management in manufacturing, especially in Japan from 1950 onwards. The cycle became a standard process for continuous improvement embraced by the quality movement.
SRE for Everyone: Making Tomorrow Better Than Today Rundeck
Keynote presentation at DevOps Days Austin 2019 by Damon Edwards, co-founder of Rundeck.
Wouldn't everyone doing operations work love more time to focus on exciting projects? Build out new platforms, improve performance, contribute to open source projects, pay down tech debt, level-up their automation — all things that add value to your company and advance your career.
But instead, we find ourselves buried in interruptions and repetitive work. Imagine the things you could do, if you just had the time to get to it.
This talk is about applying ideas from the SRE movement that can be applied to any organization. Ideas that can help us all make tomorrow better than today.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
Operational Insight: Concepts and Examplesroyrapoport
The document proposes a framework called OODA (Observe, Orient, Decide, Act) for operational insight and discusses its implications. OODA describes a cycle that anyone performing operations goes through when making decisions. To improve at OODA, one aims to increase speed, decrease effort, and increase reliability. This involves improving observation (metrics), orientation (visualization), decisions (alerting), and automating actions. Examples demonstrate how Netflix has automated capacity decisions and canary analysis to improve according to the OODA framework.
DevOps: The Future is Already Here — It’s Just Unevenly Distributeddev2ops
The document discusses the history and evolution of DevOps. It traces how DevOps began as a grassroots movement among practitioners and led to numerous DevOps conferences starting in 2009. It also outlines how DevOps aims to break down silos between development and operations teams to improve organizational alignment, reduce lead times, and provide faster feedback. A key part of DevOps is taking an end-to-end view of application delivery and focusing on continuous integration, delivery, and deployment.
DevOps & Security from an Enterprise Toolsmith's Perspectivedev2ops
Slides from presentation by Alex Honor and Damon Edwards at DevOps Connect at RSA 2015 in San Francisco on April 20, 2015.
Abstract:
IT organizations are feeling the squeeze from seemingly conflicting business mandates. At one moment the message is “Go Go Go. DevOps, Lean Startup, Continuous Delivery… move faster and give more people access”. The next moment the message is “Be more secure. Compliance above all. Keep us out of the press!”. Damon Edwards and Alex Honor work with many enterprises who are facing these challenges. This talk is an in the trenches view of how these companies are responding and learning to go faster and be more secure.
Leveraging Your Company's DevOps Transformation (AppSec USA 2014)dev2ops
This document discusses how organizations can implement DevOps practices to improve productivity and reduce waste. It outlines some of the benefits organizations see from DevOps like shorter lead times, faster problem detection and resolution, and higher quality. It also describes how traditional silos between development, testing, and operations teams can be broken down by establishing cross-functional delivery teams aligned around customer needs. Implementing practices like continuous integration and shared responsibility for the full software development lifecycle are key aspects of the DevOps transformation discussed.
The document discusses the origins and evolution of the Plan-Do-Check-Act (PDCA) cycle, also known as the Deming cycle or Shewhart cycle. It traces the concept back to ideas of scientific experimentation in the 1600s and statistical process control methods developed in the 1920s-1940s. Key figures like Deming, Shewhart, Juran popularized applying the approach to quality management in manufacturing, especially in Japan from 1950 onwards. The cycle became a standard process for continuous improvement embraced by the quality movement.
SRE for Everyone: Making Tomorrow Better Than Today Rundeck
Keynote presentation at DevOps Days Austin 2019 by Damon Edwards, co-founder of Rundeck.
Wouldn't everyone doing operations work love more time to focus on exciting projects? Build out new platforms, improve performance, contribute to open source projects, pay down tech debt, level-up their automation — all things that add value to your company and advance your career.
But instead, we find ourselves buried in interruptions and repetitive work. Imagine the things you could do, if you just had the time to get to it.
This talk is about applying ideas from the SRE movement that can be applied to any organization. Ideas that can help us all make tomorrow better than today.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
Testing within an Agile Environment - Beyza Sakir and Chris GollopJAXLondon2014
This document discusses testing within an agile environment. It provides an overview of the history of testing at a financial services company that trades billions daily. The company was conceived as agile and releases every two weeks. Testing includes acceptance, integration, and exploratory tests. The document outlines how testing concerns have changed over time, with a shift from manual to automated acceptance tests. It also discusses adaptations made to testing practices, including using production data, testing in live environments, improving feedback, and addressing intermittent tests. The future of testing focuses on areas like speeding up feedback and improving test coverage. Throughout, it emphasizes the need to continuously experiment, adapt, and embrace failures as learning opportunities.
Making Tomorrow Better than Today - Unlocking the Full Potential of OperationsRundeck
Keynote presentation by Damon Edward, co-founder of Rundeck, at DevOps Days Salt Lake City on May 15, 2019.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
SysAdmin to SRE: Creating Capacity to Make Tomorrow Better Than Today Rundeck
Damon Edwards, co-founder of Rundeck, talks at SCALE 17x on March 9, 2019 in Pasadena, CA.
Wouldn't everyone in operations love more time to work on exciting projects? Build out new platforms, improve performance, contribute to open source projects focus on security, level-up their automation — all things that add value to your companies and advance your career. But instead, the life of a traditional systems administrator is often buried in interruptions and repetitive work. Imagine the things you could do, if you just had the time to get to it.
Then along comes a new way of working and a new role called Site Reliability Engineering (SRE). But SRE almost seems too good to be true! People are doing what systems administrators used to do, but getting to spend more than 50% of their time doing engineering work that adds enduring value to their company? How can less than half of these SREs' time be wasted on the interruptions, repetitive work, and drudgery that seem to consume most of the traditional systems administrator's time? And do this with the same or less headcount?
This talk will first take a close look at what SRE is and what SRE isn't. We will break down the principles behind the SRE movement and highlight where SRE departs from the current conventional wisdom of Operations and Systems Administration work. You'll learn about key concepts like Toil, SLOs, Error Budgets, and Shared Responsibility Models.
Next, we'll look at how to move to an SRE style of working. We'll look at how traditional operations beliefs and practices can leave organizational scar tissue that is difficult to overcome. We'll examine examples of how silos, excessive toil, reliance on queues, and incorrectly applied governance models undermine the adoption of SRE principles and practices in the enterprise. We'll also look at the individual skills and mindset changes that you'll need to adopt an SRE way of working.
You'll leave this talk with an appreciation for how SRE can create the capacity you need to make tomorrow better than today.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
By measuring the friction in “Idea Flow”, the flow of ideas between the developer and the software, we can create a data-driven feedback loop for learning what works. Rather than making decisions based on anecdote and gut feel, we can start driving our improvement decisions with real data.
Data-Driven Software Mastery is about learning and improving faster than ever.
Find out how you can:
• Identify the biggest causes of productivity loss on your software project.
• Avoid spending tons of time solving the wrong problems
• Collaborate with other industry professionals in the art of data-driven software mastery
Idea Flow gives us a universal language for describing our experience, so we can share the patterns and principles of what works. With a feedback loop, we can run real experiments!
Idea Flow turns the development community into a scientific community.
This SolidWorks World 2006 presentation from Paul Gimbel of Razorleaf Corporation focuses on how to redesign your engineering design processes to leverage the use of 3D CAD tools like SoildWorks.
The document discusses issues with estimation in software projects. It notes that traditional estimation approaches fail because they ignore uncertainty and complexity. While Agile aims to help with lighter estimation practices, there is still risk of falling into the same traps as traditional methods. The key problems are how estimates are used, with unrealistic targets, imposed deadlines, and lack of respect causing issues. Respecting uncertainty and using estimates appropriately is emphasized as important.
This document discusses lean software development principles. It emphasizes eliminating waste and non-value adding activities from development processes. It defines value and waste from a customer perspective. It also discusses mapping the end-to-end value stream to identify improvement opportunities like reducing cycle times and increasing efficiency. A case study example shows how responding to critical defects can be improved through applying lean principles.
The presentation introduces the Lean Lego Game, which uses a hands-on simulation to teach Lean principles. It begins with a quick introduction and then guides participants through several rounds of building toy seals on an simulated production line. This allows them to experience problems with push-based mass production systems like waste and uneven workload. It then introduces Lean concepts like pull systems, kanban, continuous flow, and just-in-time production to resolve these issues. The goal is for participants to learn Lean thinking through an engaging exercise and reflect on how these principles can be applied to software development.
What does "better" really mean? If we eliminate duplication, is the code better? If we decide to skip the unit tests, are we doing worse? How do we decide if one design is better than another design?
About 8 years ago, my project failed, despite "doing all the right things", and shattered my faith in best practices. Since then, I've learned to measure developer experience, use *data* to learn what works, and I've been codifying "better" into patterns and decision principles for years. In this talk, I'll show you the paradigm shift that led to all my discoveries, and hopefully change your perspective on "better".
"Idea Flow" is an alternative to the Technical Debt metaphor that focuses on problems in human interaction rather than problems inside the code. By measuring the "friction" that occurs when developers interact with the code, we can identify the biggest causes of friction and systematically optimize developer experience.
Why go to all this trouble? From my experience, the biggest causes of pain are seldom what we think. When we try to make things "better", we can easily miss our biggest problems, or inadvertently make things worse. Visibility turned my beliefs about "better" upside-down.
First, I'll walk you through the conceptual metaphor of "Idea Flow" and how to recognize friction in developer experience.
Next, we'll write a little code and record the experience using the open source "Idea Flow Mapping" software.
Finally, we'll discuss a handful of "decision principles" for optimizing developer experience and analyze our coding experience as a group.
Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a...dev2ops
The document discusses how without self-service operations, the cloud becomes expensive hosting 2.0. It argues that conventional cloud wisdom about time and cost savings may not be realized due to legacy processes and tooling that prevent organizations from fully taking advantage of cloud capabilities. It advocates for cross-functional delivery teams, turning information flow into artifact flow to reduce handoffs, and inserting verification points to drive feedback loops and continuous delivery.
The document summarizes a workshop on introducing Lean concepts using a simulation game called "The Lego Lean Game". The workshop covers Lean principles like push/pull systems, Kanban, flow, and continuous improvement. Participants role-play building houses on an assembly line to experience problems with batched production and long lead times. They then apply Kanban and other Lean tools to smooth workflow. The document emphasizes that Lean is not just a set of tools but a management philosophy for eliminating waste and respecting people.
The Pursuit of Quality - Chasing Tornadoes or Just Hot Air?Paul Gerrard
The document discusses quality and models for quality and testing. It begins by explaining that quality depends on perspective and is a relationship between systems and stakeholders. It then discusses how models are used everywhere, including in quality and testing, but that all models simplify reality and can be incomplete. The document provides examples of different types of models used for quality and testing purposes.
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the effects of learning curves, collaboration pain, and problems building up in the code?
We could:
Identify the highest leverage opportunities for improvement
Make the case to management that budget should be allocated for a solution
Lead the organization in making better decisions with a data-driven feedback loop to guide the way
Several years ago, I stumbled into a solution for measuring the growing “friction” in developer experience. Visibility turned my world upside-down.
We've been trying to explain the pain of Technical Debt for generations, but we've never been able to measure it. Visibility introduces a whole new world of possibilities.
In this talk, I'll show you what I'm measuring, how exactly I'm measuring it, then we'll talk through the implications for our teams, our organizations, and our industry.
We can identify the highest leverage improvement opportunities and steer our projects with a data-driven feedback loop.
We can breakdown the "wall of ignorance" between developers and management by defining an explicit language for managing technical risk.
We can teach the art of software development with a data-driven feedback loop and codify our knowledge into sharable decision principles.
We can revolutionize our business accounting methods to take the pain of software development into account, so the costs and risks are visible at the highest levels of the organization.
We can conquer the challenges across the software industry by working together, learning together, and sharing our knowledge with the world.
With visibility, we can start a revolution in data-driven learning.
The document provides an overview of problem solving methods and tools, including the A3 problem solving process and DMAIC (Define, Measure, Analyze, Improve, Control). It emphasizes the importance of properly defining the problem through data collection, establishing a clear problem statement, and using tools like the Five Whys, fishbone diagrams, and Pareto charts to analyze the root causes. The document explains that problem solving is a critical leadership behavior for lean transformation and outlines steps for effectively using the A3 problem solving methodology to drive process improvement.
Devops at scale is a hard problem challenges, insights and lessons learnedkjalleda
Kishore Jalleda discusses several DevOps initiatives and lessons learned from implementing them at scale at Yahoo. The initiatives include: 1) Directed alerting to route alerts directly to development teams; 2) Continuous delivery to enable automated deployments to production; 3) Building an automation culture to reduce manual toil; and 4) Adopting AWS for certain use cases. Key lessons include facing challenges from multiple teams, using successes to gain buy-in, empowering teams to say no, embracing failures, and incentivizing the right behaviors. The talk argues for development teams taking true ownership over their services.
Innovation, Lean, Agile. Myths and MisconceptionGaetano Mazzanti
This document discusses myths and misconceptions around innovation, Lean, and Agile. It argues that while Lean and Agile principles can help foster innovation, they are often misunderstood and applied in rigid, dogmatic ways that can actually hinder innovation. True innovation emerges from an environment that accepts failure, values learning over outputs, and integrates research into workflows rather than separating it. Process improvement methods should focus on enabling conditions for innovation to emerge rather than trying to dictate or cause innovation directly.
Slides from a webinar presented on 11-17-2020 in partership with Creato Performance Systems. The webinar covers the Critical to Quality Chart, Voice of the Customer basics, and Kano Analysis.
Operations as a Service: Because Failure Still Happens Rundeck
Presentation by Damon Edwards, co-founder of Rundeck, at All Day DevOps on October 24, 2017.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
This document discusses various techniques for measuring and improving application performance. It begins by explaining the importance of measuring performance at the machine, component, and request levels. This includes collecting metrics on CPU, memory, I/O, logs, and tracing requests. Once issues are identified, the document recommends actions like caching, queueing work, and rearchitecting systems using service-oriented principles to improve performance. It stresses the importance of an ongoing process of measuring, analyzing data, taking action, and verifying the impact of changes.
Testing within an Agile Environment - Beyza Sakir and Chris GollopJAXLondon2014
This document discusses testing within an agile environment. It provides an overview of the history of testing at a financial services company that trades billions daily. The company was conceived as agile and releases every two weeks. Testing includes acceptance, integration, and exploratory tests. The document outlines how testing concerns have changed over time, with a shift from manual to automated acceptance tests. It also discusses adaptations made to testing practices, including using production data, testing in live environments, improving feedback, and addressing intermittent tests. The future of testing focuses on areas like speeding up feedback and improving test coverage. Throughout, it emphasizes the need to continuously experiment, adapt, and embrace failures as learning opportunities.
Making Tomorrow Better than Today - Unlocking the Full Potential of OperationsRundeck
Keynote presentation by Damon Edward, co-founder of Rundeck, at DevOps Days Salt Lake City on May 15, 2019.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
SysAdmin to SRE: Creating Capacity to Make Tomorrow Better Than Today Rundeck
Damon Edwards, co-founder of Rundeck, talks at SCALE 17x on March 9, 2019 in Pasadena, CA.
Wouldn't everyone in operations love more time to work on exciting projects? Build out new platforms, improve performance, contribute to open source projects focus on security, level-up their automation — all things that add value to your companies and advance your career. But instead, the life of a traditional systems administrator is often buried in interruptions and repetitive work. Imagine the things you could do, if you just had the time to get to it.
Then along comes a new way of working and a new role called Site Reliability Engineering (SRE). But SRE almost seems too good to be true! People are doing what systems administrators used to do, but getting to spend more than 50% of their time doing engineering work that adds enduring value to their company? How can less than half of these SREs' time be wasted on the interruptions, repetitive work, and drudgery that seem to consume most of the traditional systems administrator's time? And do this with the same or less headcount?
This talk will first take a close look at what SRE is and what SRE isn't. We will break down the principles behind the SRE movement and highlight where SRE departs from the current conventional wisdom of Operations and Systems Administration work. You'll learn about key concepts like Toil, SLOs, Error Budgets, and Shared Responsibility Models.
Next, we'll look at how to move to an SRE style of working. We'll look at how traditional operations beliefs and practices can leave organizational scar tissue that is difficult to overcome. We'll examine examples of how silos, excessive toil, reliance on queues, and incorrectly applied governance models undermine the adoption of SRE principles and practices in the enterprise. We'll also look at the individual skills and mindset changes that you'll need to adopt an SRE way of working.
You'll leave this talk with an appreciation for how SRE can create the capacity you need to make tomorrow better than today.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
By measuring the friction in “Idea Flow”, the flow of ideas between the developer and the software, we can create a data-driven feedback loop for learning what works. Rather than making decisions based on anecdote and gut feel, we can start driving our improvement decisions with real data.
Data-Driven Software Mastery is about learning and improving faster than ever.
Find out how you can:
• Identify the biggest causes of productivity loss on your software project.
• Avoid spending tons of time solving the wrong problems
• Collaborate with other industry professionals in the art of data-driven software mastery
Idea Flow gives us a universal language for describing our experience, so we can share the patterns and principles of what works. With a feedback loop, we can run real experiments!
Idea Flow turns the development community into a scientific community.
This SolidWorks World 2006 presentation from Paul Gimbel of Razorleaf Corporation focuses on how to redesign your engineering design processes to leverage the use of 3D CAD tools like SoildWorks.
The document discusses issues with estimation in software projects. It notes that traditional estimation approaches fail because they ignore uncertainty and complexity. While Agile aims to help with lighter estimation practices, there is still risk of falling into the same traps as traditional methods. The key problems are how estimates are used, with unrealistic targets, imposed deadlines, and lack of respect causing issues. Respecting uncertainty and using estimates appropriately is emphasized as important.
This document discusses lean software development principles. It emphasizes eliminating waste and non-value adding activities from development processes. It defines value and waste from a customer perspective. It also discusses mapping the end-to-end value stream to identify improvement opportunities like reducing cycle times and increasing efficiency. A case study example shows how responding to critical defects can be improved through applying lean principles.
The presentation introduces the Lean Lego Game, which uses a hands-on simulation to teach Lean principles. It begins with a quick introduction and then guides participants through several rounds of building toy seals on an simulated production line. This allows them to experience problems with push-based mass production systems like waste and uneven workload. It then introduces Lean concepts like pull systems, kanban, continuous flow, and just-in-time production to resolve these issues. The goal is for participants to learn Lean thinking through an engaging exercise and reflect on how these principles can be applied to software development.
What does "better" really mean? If we eliminate duplication, is the code better? If we decide to skip the unit tests, are we doing worse? How do we decide if one design is better than another design?
About 8 years ago, my project failed, despite "doing all the right things", and shattered my faith in best practices. Since then, I've learned to measure developer experience, use *data* to learn what works, and I've been codifying "better" into patterns and decision principles for years. In this talk, I'll show you the paradigm shift that led to all my discoveries, and hopefully change your perspective on "better".
"Idea Flow" is an alternative to the Technical Debt metaphor that focuses on problems in human interaction rather than problems inside the code. By measuring the "friction" that occurs when developers interact with the code, we can identify the biggest causes of friction and systematically optimize developer experience.
Why go to all this trouble? From my experience, the biggest causes of pain are seldom what we think. When we try to make things "better", we can easily miss our biggest problems, or inadvertently make things worse. Visibility turned my beliefs about "better" upside-down.
First, I'll walk you through the conceptual metaphor of "Idea Flow" and how to recognize friction in developer experience.
Next, we'll write a little code and record the experience using the open source "Idea Flow Mapping" software.
Finally, we'll discuss a handful of "decision principles" for optimizing developer experience and analyze our coding experience as a group.
Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a...dev2ops
The document discusses how without self-service operations, the cloud becomes expensive hosting 2.0. It argues that conventional cloud wisdom about time and cost savings may not be realized due to legacy processes and tooling that prevent organizations from fully taking advantage of cloud capabilities. It advocates for cross-functional delivery teams, turning information flow into artifact flow to reduce handoffs, and inserting verification points to drive feedback loops and continuous delivery.
The document summarizes a workshop on introducing Lean concepts using a simulation game called "The Lego Lean Game". The workshop covers Lean principles like push/pull systems, Kanban, flow, and continuous improvement. Participants role-play building houses on an assembly line to experience problems with batched production and long lead times. They then apply Kanban and other Lean tools to smooth workflow. The document emphasizes that Lean is not just a set of tools but a management philosophy for eliminating waste and respecting people.
The Pursuit of Quality - Chasing Tornadoes or Just Hot Air?Paul Gerrard
The document discusses quality and models for quality and testing. It begins by explaining that quality depends on perspective and is a relationship between systems and stakeholders. It then discusses how models are used everywhere, including in quality and testing, but that all models simplify reality and can be incomplete. The document provides examples of different types of models used for quality and testing purposes.
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the effects of learning curves, collaboration pain, and problems building up in the code?
We could:
Identify the highest leverage opportunities for improvement
Make the case to management that budget should be allocated for a solution
Lead the organization in making better decisions with a data-driven feedback loop to guide the way
Several years ago, I stumbled into a solution for measuring the growing “friction” in developer experience. Visibility turned my world upside-down.
We've been trying to explain the pain of Technical Debt for generations, but we've never been able to measure it. Visibility introduces a whole new world of possibilities.
In this talk, I'll show you what I'm measuring, how exactly I'm measuring it, then we'll talk through the implications for our teams, our organizations, and our industry.
We can identify the highest leverage improvement opportunities and steer our projects with a data-driven feedback loop.
We can breakdown the "wall of ignorance" between developers and management by defining an explicit language for managing technical risk.
We can teach the art of software development with a data-driven feedback loop and codify our knowledge into sharable decision principles.
We can revolutionize our business accounting methods to take the pain of software development into account, so the costs and risks are visible at the highest levels of the organization.
We can conquer the challenges across the software industry by working together, learning together, and sharing our knowledge with the world.
With visibility, we can start a revolution in data-driven learning.
The document provides an overview of problem solving methods and tools, including the A3 problem solving process and DMAIC (Define, Measure, Analyze, Improve, Control). It emphasizes the importance of properly defining the problem through data collection, establishing a clear problem statement, and using tools like the Five Whys, fishbone diagrams, and Pareto charts to analyze the root causes. The document explains that problem solving is a critical leadership behavior for lean transformation and outlines steps for effectively using the A3 problem solving methodology to drive process improvement.
Devops at scale is a hard problem challenges, insights and lessons learnedkjalleda
Kishore Jalleda discusses several DevOps initiatives and lessons learned from implementing them at scale at Yahoo. The initiatives include: 1) Directed alerting to route alerts directly to development teams; 2) Continuous delivery to enable automated deployments to production; 3) Building an automation culture to reduce manual toil; and 4) Adopting AWS for certain use cases. Key lessons include facing challenges from multiple teams, using successes to gain buy-in, empowering teams to say no, embracing failures, and incentivizing the right behaviors. The talk argues for development teams taking true ownership over their services.
Innovation, Lean, Agile. Myths and MisconceptionGaetano Mazzanti
This document discusses myths and misconceptions around innovation, Lean, and Agile. It argues that while Lean and Agile principles can help foster innovation, they are often misunderstood and applied in rigid, dogmatic ways that can actually hinder innovation. True innovation emerges from an environment that accepts failure, values learning over outputs, and integrates research into workflows rather than separating it. Process improvement methods should focus on enabling conditions for innovation to emerge rather than trying to dictate or cause innovation directly.
Slides from a webinar presented on 11-17-2020 in partership with Creato Performance Systems. The webinar covers the Critical to Quality Chart, Voice of the Customer basics, and Kano Analysis.
Operations as a Service: Because Failure Still Happens Rundeck
Presentation by Damon Edwards, co-founder of Rundeck, at All Day DevOps on October 24, 2017.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
This document discusses various techniques for measuring and improving application performance. It begins by explaining the importance of measuring performance at the machine, component, and request levels. This includes collecting metrics on CPU, memory, I/O, logs, and tracing requests. Once issues are identified, the document recommends actions like caching, queueing work, and rearchitecting systems using service-oriented principles to improve performance. It stresses the importance of an ongoing process of measuring, analyzing data, taking action, and verifying the impact of changes.
Nondeterministic Software for the Rest of UsTomer Gabel
A talk given at GeeCON 2018 in Krakow, Poland.
Classically-trained (if you can call it that) software engineers are used to clear problem statements and clear success and acceptance criteria. Need a mobile front-end for your blog? Sure! Support instant messaging for a million concurrent users? No problem! Store and serve 50TB of JSON blobs? Presto!
Unfortunately, it turns out modern software often includes challenges that we have a hard time with: those without clear criteria for correctness, no easy way to measure performance and success is about more than green dashboards. Your blog platform better have a spam filter, your instant messaging service has to have search, and your blobs will inevitably be fed into some data scientist's crazy contraption.
In this talk I'll share my experiences of learning to deal with non-deterministic problems, what made the process easier for me and what I've learned along the way. With any luck, you'll have an easier time of it!
This document discusses OutSystems' Agile development platform and expertise. It highlights key Agile concepts like iterative development, continuous delivery, and reducing technical debt. The platform promises features like one-click application publishing to help organizations adopt Agile practices across more than just development, including deployment, user feedback, and business processes. It encourages the reader to try the platform themselves at the provided URL or by contacting a sales representative.
Goto Chicago; Journeys To Cloud Native Architecture: Sun, Sea And Emergencies...OpenCredo
This document discusses journeys to cloud native architectures and provides principles for success. It begins with an overview of the cloud native dream from a business perspective, aiming for faster time to market and scalability. However, common issues that can arise include tackling too much too quickly, relying on a surface-level understanding, using ineffective tools and processes, and not anticipating failure. The document concludes with principles for a successful cloud native journey: don't take on too much too quickly, acquire sufficient expertise, choose tools wisely, engage security, and plan for failure through active testing of sad paths.
This document discusses the concepts of devops and how to transition an organization to a devops model. Some key points:
- Devops aims to break down silos between development and operations through culture, automation, measurement, and sharing.
- Traditional organizations have opposing goals between dev and ops that cause issues. Devops promotes a cross-functional team approach.
- Automating builds, testing, deployments, infrastructure management reduces risk and improves collaboration.
- Monitoring and metrics should be built in from the start so teams can learn from data and continuously improve.
- Culture change can be difficult but focusing on mindset, collaboration and incremental goals can help transition teams.
DriveBuild: Automation of Tests in the Field of Autonomous CarsUniversity of Passau
This document provides an overview and demonstration of DriveBuild, an interactive test environment for autonomous vehicles. It describes the components of a test environment, including lanes, obstacles, participants and criteria. It also covers executing tests, describing the available modes like manual, autonomous and training. Finally, it discusses how to use DriveBuild for test generation and training autonomous agents.
This document discusses DevOps concepts and practices. It emphasizes that DevOps is about culture, automation, measurement, and sharing between development and operations teams. Some key points made include: treating infrastructure as code; automating builds, testing, and deployments; implementing continuous integration and delivery practices; and breaking down barriers between teams through collaboration, shared goals, and cross-functional teams. The overall message is that DevOps aims to streamline software development through cultural and technological changes that bring development and operations teams together.
Self-Service Operations: Because Failure Still Happens (Developer Edition)Rundeck
Keynote presentation at DevNet Create 2017 by Damon Edwards, co-founder of Rundeck.
Agile and DevOps have provided plenty of lessons for how to speed up the pace of application delivery and the frequency of application deployment. But delivery and deployment only covers one part of the day-to-day life of developers in large enterprises. What about what happens after deployment? In many enterprises, increasing the pace of delivery and frequency of deployment has just increased the operational support load, work interrupts, and context switching that were already cutting deeply into development teams' time.
This talk will focus on the successful design patterns that high-performing, large scale organizations have applied to reduce the operational burden and support costs across their entire organization. Specifically, we’ll look at how they apply DevOps principles to improving the post-deployment lifecycle and how Developers play the key role in reducing the difficultly and cost of operations activity for everyone.
Damon Edwards, co-founder of Rundeck, presentation at Nexus Conf 2018 on how Security teams can help Operations and, in turn, help themselves.
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
1. The document discusses metrics-driven continuous delivery and focuses on using metrics throughout the development and delivery process.
2. It emphasizes using architectural metrics in addition to functional metrics to help determine if a new version is likely to cause catastrophic failures before deploying to production.
3. It also argues that the concept of continuous delivery pipelines should extend beyond production deployments to help evaluate user experience and gain feedback on new features beyond just technical metrics.
Monitoring Complex Systems - Chicago Erlang, 2014Brian Troutwine
Imagine being responsible for monitoring 100 servers. Now imagine 1000. Each server has 100 different things to keep track of. What do you pay attention to and what do you ignore? What is important? In this talk Brian will show how Erlang can be used to capture more information without compromising clarity — i.e. to keep track of the forest without loosing site of the trees!
Devops is about culture, not tools. It involves building cross-functional teams that share goals of helping the business by improving communication, trust, and automation. This allows features to be released more quickly, reliably, and securely by breaking down barriers between previously separate functions like development and operations. The document discusses how devops aims to continuously improve systems through measuring outcomes and eliminating fear and slogans in favor of leadership.
Keeping Your DevOps Transformation From Crushing Your Ops Capacity Rundeck
Presentation by Damon Edwards, co-founder of Rundeck, at DevOps Enterprise Summit in San Francisco, November 13, 2017
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
Navigation in 3 d environment with reinforcement learning by Predrag Njegovan...SmartCat
Reinforcement learning in today's order of things when artificial intelligence is on the rise is a favorable field for new research. One of the problems that were tried to be solved in the last year or two is the problem of environmental control or navigation. This talk is going to present one form of solution to the problem of navigation and generalization in a three-dimensional environment while there are restrictions of rewards, by forming an autonomous agent with deep learning techniques.
Devops, The future is here, it's just not evenly distributedKris Buytaert
Devops aims to break down barriers between development and operations teams through principles like continuous integration, automation, shared infrastructure access, and cross-functional teams. It advocates automating processes from building to deploying to testing in order to enable continuous delivery of new features in a secure and reliable manner. This helps improve communication between teams and allows organizations to get features to users faster while increasing stability, security, and customer satisfaction. Achieving devops culture and practices requires patience, improving collaboration, building trust between teams, and automating as many processes as possible.
Faster apps. faster time to market. faster mean time to repairCompuware ASEAN
Developers, Test Engineers, QA Engineers, Network Engineers, Operations Managers, Production Managers and Solution Architects joined us in Singapore to learn more about APM Lifecycle
The document discusses improving a company's approach to application performance. It recommends integrating performance testing into continuous integration to automate testing and monitoring. This would help find issues earlier, reduce time to market, and better monitor real user behavior and system health. The future approach is described as continuous performance integration, with performance tests running in Jenkins, automated reporting, and real user monitoring for real-time feedback.
NetGain Systems provides IT infrastructure monitoring solutions to help IT teams keep business operations running smoothly. Their flagship product, NetGain Enterprise Manager, is an all-in-one IT monitoring appliance that can automatically monitor an entire IT infrastructure, detect performance issues and failures, and correlate IT outages to business impacts to help teams shift from a reactive to proactive management approach. Over 100 enterprises across Asia use NetGain's solutions to achieve benefits like shorter response times, reduced downtime, and improved visibility into business availability.
Similar to Operational Insight: Concepts and Examples (w/o Presenter Notes) (20)
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
27. Implications …
for Observation (aka measurement, telemetry, metrics)
• Make It Easy
• Make It Scalable
• Make it pluggable
28. Implications …
for Observation (aka measurement, telemetry, metrics)
• Make It Easy
• Make It Scalable
• Make it pluggable
• (Eventually) Ruthlessly Cull
29. Implications …
for Observation (aka measurement, telemetry, metrics)
• Make It Easy
• Make It Scalable
• Make it pluggable
• (Eventually) Ruthlessly Cull
“What decision will this help me make?”
36. Implications …
for Orientation (aka graphing, visualization)
• First-class product
• Different decisions require different viz
37. Implications …
for Orientation (aka graphing, visualization)
• First-class product
• Different decisions require different viz
• Low cognitive load better than
38. Implications …
for Orientation (aka graphing, visualization)
• First-class product
• Different decisions require different viz
• Low cognitive load better than
• High refresh rates
39. Implications …
for Orientation (aka graphing, visualization)
• First-class product
• Different decisions require different viz
• Low cognitive load better than
• High refresh rates
• Deep data density
44. Implications …
for Decisions (aka alerting, real-time analytics, etc)
• You already have (some of) this
• Incremental improvement
45. Implications …
for Decisions (aka alerting, real-time analytics, etc)
• You already have (some of) this
• Incremental improvement
• Sky’s the limit
46. Implications …
for Decisions (aka alerting, real-time analytics, etc)
• You already have (some of) this
• Incremental improvement
• Sky’s the limit
• For benefits
47. Implications …
for Decisions (aka alerting, real-time analytics, etc)
• You already have (some of) this
• Incremental improvement
• Sky’s the limit
• For benefits
• For cost
99. In a Nutshell
Observe
Orient
Decide
Act
Need This First
http://bit.ly/nflx-atlas-2013
http://metrics20.org
Understand the decision
http://bit.ly/nflx-qcon-aca-2014
Make it easier for humans
100. In a Nutshell
Observe
Orient
Decide
Act
Need This First
http://bit.ly/nflx-atlas-2013
http://metrics20.org
Understand the decision
http://bit.ly/nflx-qcon-aca-2014
Make it easier for humans
Make machines
do it
101. In a Nutshell
Observe
Orient
Decide
Act
Need This First
http://bit.ly/nflx-atlas-2013
http://metrics20.org
Understand the decision
http://bit.ly/nflx-qcon-aca-2014
Make it easier for humans
Make machines
do it
Higher speed
Lower effort
Higher reliability