Banjo Obayomi • Senior Research Engineer • Two Six Labs

Machine Learning is often referred to as a panacea to solve many organizations' problems. However, without a guiding framework to act upon many efforts are wasted on purpose non-valuable tasks. The ICON framework was built to align business value with software development in order to ensure resources are not wasted. The ICON framework is broken down into 4 parts

• Identify - This part sets up the object from the start of the effort. Questions asked in this phase are
  What are you trying to do? Why do we need this? and What is valuable to us?
• Collect - This phase is all about the data needed to reach the goals. Questions asked in this phase are
  What data do we need? How do we get the data? How do we prepare the data?
• Operate - This phase is all about operationalizing efforts to create value. Questions asked in this phase are
  What do we build? How do we scale our process? What tools do we need?
• Narrate - This phase is about narrating how your process was successfully able to create value. Questions asked in this phase are
  Did we build the right thing? Is this working as expected? Are we getting value?

By adhering to the ICON framework during the development cycle stakeholders and developers can contextualize if their efforts are aligned with creating business value. This talk will go over how to incorporate the ICON framework into your development cycles.

Petter Franzen • Principal Engineer • NotOnTheHighStreet

Let your repo and pipeline do the heavy lifting, how we are aligning multiple frontends to a shared architecture at NotOnTheHighStreet.

Michael Moynihan • Commercial Account Executive • Code Climate

Find out how Velocity can help engineering leaders make data-backed decisions that boost team productivity and efficiency. With information from Velocity, you'll gain a complete understanding of how your team is working, so you can streamline processes and set more effective goals.

Chris Harding • Solutions Engineer • Epsagon

Join our live demo to learn how our platform enables teams to instantly simplify, visualize, and understand what's happening within complex microservice architectures. With our comprehensive lightweight auto-instrumentation, users are able to eliminate the gaps in data and manual work associated with other APM solutions, providing significant reductions in issue detection, troubleshooting, and resolution times. Epsagon aggregates, unifies, analyzes, and correlates data from all the third party tools you love, delivering a single pane of glass for understanding containers, Kubernetes, serverless, and more.

Who should attend? DevOps, Engineers, Cloud Architects, CTOs, IT, Software Developers, Solution Architects and Engineers, SREs, and anyone who is running microservice-based applications (Kubernetes, containers, serverless functions, and more) in the cloud.

Charity Majors • CTO and Co-founder , Honeycomb

There is a yawning gap opening up between the best and the rest — the elite top few percent of engineering teams are making incredible gains year over year in reliability and lack of technical drag forces, while the bottom 50% are losing ground. Take an engineer out of an elite-performing team and place them in the bottom 50%, and they become subpar too; take an engineer out of a mediocre team and embed them in an elite team, and they are pulling their weight within the year. I will share with you everything I know — everything that went into building a high-performing team at Honeycomb.

Nathan LeClaire • Solutions Architect, Honeycomb

You may have heard the hype; now see it in action. With Honeycomb, modern dev teams build and operate resilient, reliable systems because they can clearly understand them.

Running queries and getting results fast should be table stakes. Ask any question and get results fast, no matter how many fields, without writing new code. Reduce toil and delight your users.

Jose Romero • Solutions Engineer, LaunchDarkly

Come to our demo to see how LaunchDarkly allows you to deploy code when your team is ready, and then let product teams independently release features when they are ready. Empower your teams to collaborate more, maintain stability, and deliver software faster. Reduce your team member’s stress of being on “pager duty” - with feature flags, you don’t have to roll back code to undo a feature release or mitigate a disaster, simply change the flag status.

Chad Carlson • Developer Relations Engineer, Platform.sh

Development teams spend time on a lot of things other than their product. They manage infrastructure, DevOps and integrations, and even create staging servers so that external agency can test out your sweet new redesign. Maybe it’s not even just one site to worry about, but a whole fleet of applications that need to be kept in-sync, secure, and up-to-date, all while sticking to a release schedule.

No one has that much attention or experience to manage it all, and it’s a lot to ask of them to keep up with.

In this demo you’ll get a view of how the same team solves these problems when their project is hosted on Platform.sh. In short, they don’t need to think much about them. The project didn’t move anywhere - it’s in the same GitHub repository the team is used to working with - but now it’s got some new tools and assurances that weren’t there before with only a few short files needed to configure it all. We’ll cover:

• Infrastructure-as-code: committed and clear infrastructure for all collaborators, where new services and upgrades are single character commits. CI: pull requests become live environments as soon as they’re opened, even for upgrades to infrastructure.
• Production data: a staging server for every proposed change, that’s not just a clone of production code, but also infrastructure and production data that the application really needs to have available for reliable testing prior to merges.
• Access: collaborators can test on isolated copies of production as easily as branching.
• One or many: control extends from a single application to a full fleet just the same.

Ivan Diaz • Solutions Engineer, Bugsnag

Every error does not concern every engineer. Your team members don’t need to be pinged about every application error, especially when an error occurs in someone else’s part of the code. In fact, it can become a negative distraction that takes away focus from their work. Join Bugsnag's Solution Engineer to discover why eliminating noise and focusing on the bugs that you can and should fix, drives a culture of code ownership, and improves developer productivity.

Prioritising and remediating security issues in your projects can be a pain, especially when you’re given a long list of tasks to complete at the end of a deployment. How can you make the build process as seamless as possible for development teams? Join this session as we show how to make developer’s lives easier. Learn how to:

• Upgrade components with the least amount of effort
• Avoid versions that will completely break your project
• How to avoid dangerous components from the get-go

Forrest Anthony Knight Jr • Senior Sales Engineer, Lightstep

Distributed systems, distributed teams, and distributed problems. We should be able to find the root cause of an issue regardless of how our software is built. After all, everything is connected. If you're interested in doing root cause analysis at scale and modernizing your toolset to do so, stop by!

Dan Lines • Co-Founder & COO (Former VP of Engineering • LinearB

Hey Dev Leader, attend this demo and you'll learn 1) which engineering metrics drive the most team improvement 2) how to start your metrics program today 3) how LinearB automates the process for you.

Montana Mendy • Developer Relations Manager • Travis CI

We'll show you how easy it is to get your code source set up with Travis CI using either GitHub, GitLab, Bitbucket or Assembla. We'll take you through running your first build, what to expect, what to look out for and how to overcome common issues with software testing.

Ryn Daniels • Site Reliability Engineer • Terraform Cloud

The world of technology changes fast. In order to keep up, the culture of our engineering organizations must be able to change as well. Using the principles of devops as an example, this talk will present a culture design process that will help engineering leaders to identify problems with their current culture, brainstorm concrete solutions, and do so in a way that is sustainable over time.

Angel Rivera • Developer Advocate • CircleCI

CircleCI is a continuous integration and continuous delivery platform that helps software teams work smarter, faster. Join our demo to discover how our platform simplifies the most complex parts of DevOps processes, giving teams confidence in their code, helping them move faster, and helping them focus on what matters: building great products and services.