DeveloperWeek Europe 2021 DeveloperWeek Europe 2021

DevExec & DevLead

Tuesday, April 27, 2021

- BST
OPEN TALK: Practical Tips and Tricks for CI/CD Success
Join on Hopin
Zan Markan
Zan Markan
CircleCI, Developer Advocate

A CI/CD pipeline seems straightforward to implement and maintain. Yet it can often quickly become a tedious time sink and a source of universal frustration on many teams. From flaky builds, to long running builds, to flaky long running builds, the sources of frustration are endless. With the goal to ship more and faster as well as to compete in an ever changing industry, we can (and must) do better.

This talk will cover best practices for performance, stability, security, and maintainability of CI/CD pipelines, each supported with practical examples and counterexamples.

- BST
OPEN TALK: AppSec Testing Automation for Developers
Join on Hopin
Oliver Moradov
Oliver Moradov
NeuraLegion, VP

Shifting Application Security Left and into the hands of developers has been a topic of discussion, but remains just that, a discussion. Legacy solutions in the market are not built from the ground up to enable this and achieve DevSecOps. In this session we will discuss the key features that your AppSec testing tools need to enable shift left, or shift everywhere, to empower developers to detect, prioritize and remediate security issues EARLY, as part of your agile development and unit testing processes, without slowing down DevOps. The talk will include specific examples from leading organizations that have deployed these solutions, the business impact they have achieved and the steps you can take to achieve the same, across your applications and APIs

Wednesday, April 28, 2021

- BST
Software Development Antipatterns
Join on Hopin
Mustafa Toroman
Mustafa Toroman
Authority Partners, Solution Architect, Azure MVP

In software development, we like to recognize good choices and identify them as patterns. This leads into implementing these patterns as best practices. But as we have good choices, we have bad choices as well. We identify them as antipatterns in order to avoid them in future projects. If you identify them in time, you can avoid them on your next project. Come and check what warning signs you need to look for!

- BST
Lean Product Development through SLOs
Join on Hopin
Josh Armitage
Josh Armitage
Contino, Principal Consultant

How can you strip over-processing out of your value stream?
How can you understand and communicate what "good enough" looks like?
How can you systematically challenge and remove assumptions from you consumers?

In supporting enterprises in DevOps & agile transformations across three continents, I discovered a common theme, stories talk of what is to be enabled, but not how well it needs to perform.

Recently, upon joining a platform team drowning under the weight of their backlog, I experimented with SLOs being the beating heart of our product development flow.

To do this, we:

- Revisited all previous core usecases and determined meaningful SLIs and SLOs
- Made SLOs an inherent part of defining features
- Built a lightweight infrastructure to translate technical changes to business events
- Made a dashboard to transparently broadcast our SLOs
- Made SLOs be the core of conversations with our consumers

By doing this, we:

- Removed assumptions from consumers, driving more meaningful conversations about value
- Created a beachhead for a more data driven culture
- Created a common understanding of what "good enough" looked like
- Became better focused on maximising value delivery, over redundant gold plating of features

You'll learn:

- How to adopt an SLO driven product development flow
- From the mistakes we made along the way
- Tips and tricks for defining SLOs for low frequency usecases
- How to drive more impactful conversations

- BST
Do You Really Know Your Team?
Join on Hopin
Pablo Bouzada
Pablo Bouzada
Plain Concepts, Software Engineer Manager

One of the principles in Agile says: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

As Engineering Manager, Principal Engineer, Tech Lead or whatever your title says, do you know how to motivate individuals? Do you know how to create a safe environment and support each team member? Do you know how let them grow?

In my 10 years managing teams I learn a few things that should help you in order to know, support, and grow your team based on Agile principles, Management 3.0 and other stuff...

- BST
How Cisco Embraced a DevOps Culture within Its Network Engineering Team
Join on Hopin
Stuart Clark
Stuart Clark
Cisco, Network Automation Developer Evangelist

BUSINESS PROBLEM & CHALLENGE
Network automation was not well practiced or well understood inside our network engineering team, but was sorely needed. We needed to decrease effort and mistakes on daily management tasks by minimizing the direct human interaction with network devices. High on our priority list of goals, was improving network security by recognizing and fixing security vulnerabilities and increasing the network performance.

HOW WE OVERCAME THE CHALLENGE
We started by simplifying daily workflows, baselining our configurations and removing snowflakes. While this can be very labour-intensive at the outset when you’re working on a global scale in a highly critical customer environment, the long-term benefits far outweighed the labour.
Next, we created an inventory file which listed all network devices by type, model, location and IP address - this enabled us to retrieve info about devices and using network programming and automation, allowing us to deploy to all devices, or even a subset of devices (eg. only those in a specific area), depending on what was needed. The benefit to this is we avoided manual configuration and logging into hundreds of different devices to add configuration to each one.
Overcoming these two big challenges set us up for success and enabled us to deploy at a global scale. We lived by the mantra:

“If it’s not repeatable, it’s not automatable. And if it’s not automatable, it’s not scalable.”

LEARNINGS AND MEASURABLE OUTCOMES
So what did we learn? For starters, it can be hard to automate a use case or test in the same way you would if doing it manually. Testing that requires physical movement, for example losing service provider links or hardware failure is also a challenge, as automating something like that is very tricky. We also learned that code reviews are extremely important. Shared code ownership means the entire team can make changes anywhere, at any time.

And what we’re the measurable outcomes?

Faster deployment times - we were able to efficiently push changes to over 300 network devices and audit the configuration of our global network, taking the time to execute from days down to hours.
Removed the fear of large and complex network changes - the accuracy and efficiency with which we were able to deploy at scale, gave business and the leadership more confidence in subsequent large scale network changes and deployments.
Faster feedback on network changes - it allowed us to get reviews on network configuration changes with version control and peer review, treating infrastructure as code (IaC).
Helped with adhering to PSIRT/CSIRT challenging timeframes and security vulnerabilities.


Techniques used:
We started by simplifying daily workflows, baselining our configurations and removing snowflakes. Next, we created an inventory file which listed all network devices by type, model, location and IP address.

Metrics used:
Speed of deployment; speed of feedback on network changes; speed of adherence to PSIRT/CSIRT timeframes; confidence and buy-in from senior leadership on subsequent deployments!

- BST
Why We Need Product Management Skills in Application Modernization
Join on Hopin
Fani Bahar
Fani Bahar
VMware, Product Manager

Product Manager, this is a title that is very hard to explain and most of the time comes with big responsibilities but yet it is easy to overlook. Moreover, in the Application Modernization journey that focuses on modernizing your legacy application.
We are not delivering code or creating a prototype and definitely our job description is NOT attending meetings all day. We believe there are skills and mindset as Product Manager to accelerate the team to be successful in building modern applications. In this talk, I will share why we need product management skills to increase the success in your Application Modernization journey.

- BST
Be Future Compatible with AI/ML
Join on Hopin
Natalie Pistunovich
Natalie Pistunovich
Aerospike, Lead Developer Advocate

In 2020, OpenAI has launched GPT-3, an autoregressive language model that uses deep learning to produce human-like text which was trained on 175 Billion parameters.
In 2021, Google AI has open sourced Switch Transformer, an artificial intelligence language model which was trained on 1.6 Trillion parameters.
How do these developments affect the tech industry?

It’s a safe bet that the state of tech as we know it will change to be AI-driven. This is already affecting a wide range of fields, from meditation apps, through investment robots to the cloud infrastructure. This won’t stop there, as new fields that are being disrupted by tech, like legal-tech, med-tech and others, also have an AI component.

Keeping up with these changes requires changes across all the tech teams - product, software, DevOps, QA, etc. In this talk we will cover the current state of AI and how you can make your product and teams future-compatible.

- BST
What the Soviet Space Program Taught Me about Digital Product Development
Join on Hopin
Dean Schuster
Dean Schuster
Truematter, UX Strategy Expert and Partner

The space race between the USA and USSR was one of the great dramatic stories of the 20th century. Our very industry was born as Washington and Moscow relentlessly competed to master the stars.

For space nuts like me, this fascinating time is utterly compelling. It’s also highly instructive for digital product developers. After all, engineers drove the innovation that pushed us beyond earth. The lessons they learned and processes they created can help us today as we make software, apps, and advanced functionality online.

Of course, the Soviet side of the story tends to be less understood. And that’s exactly what we’ll explore. It’s unbelievable stuff, and a cautionary tale for development teams.

WHAT YOU’LL LEARN
- How differing philosophies of development lead to different processes and results.
- What Soviet imperatives parallel modern development approaches.
- Why the USSR led the space race early, but ultimately failed to reach the moon first.
- What we can learn, adapt, and avoid today from the 20th century Soviet model.

- BST
OPEN TALK: Driving Collaboration across Distributed Teams
Join on Hopin
Jarom Chung
Jarom Chung
Lucid, Director of Product

The future of work has arrived. As product development teams have shifted to working remotely, we’ve had to adjust our processes, communication, and culture. Join Lucidspark to learn how to effectively drive collaboration across distributed teams both now and going forward.

- BST
Getting Started with Observability for Chaos Engineering
Join on Hopin
Shelby Spees
Shelby Spees
Honeycomb, Developer Advocate

How much are you learning from your chaos experiments? How do you know it’s safe to perform them? Learn how to instrument your systems in order to gain confidence and get the most out of chaos, whether you’re injecting it on purpose or it’s already there in your system. This talk explores how Honeycomb’s engineering team leverages high-context telemetry data to measure service heath and risk in order to determine when it’s safe to perform experiments. Attendees will come away with next steps for instrumenting for observability in order to get the most out of their own chaos experiments.