Kevlin Henney

Consultant, Trainer, Writer, Editor of 97 Things Every Programmer Should Know

Lean Code

Lean has been applied as a toolkit to fine-tune development processes and organisational workflow, but what does it mean when we apply the practices to the detail of the code, the practices used to develop it and the people who develop it? What does Lean Code and its creation look like? There is a need to move beyond often separated worlds of software craft and agile development, to properly embrace code in its detail, but to also connect it more completely to the flow of business and the intelligence of people around it. To move beyond simple exhortations of clean code to something more human. This talk offers a fresh look at Lean principles and practices from the perspective of the code and the coder, rather than the usual scale of the organisation and the development process.

Jimmy Bogard

Chief Architect @ Headspring, Microsoft MVP, Creator of AutoMapper

Vertical Slice Architecture

Moving from a layered architecture to a vertical slice architecture can be a bit daunting. We remove abstractions, complex structures, and focus building on the axis of change, then what's next? What new structures, patterns, and policies will need to be introduced in this style of architecture? How will we deal with common business functionality, and where do concepts like CQRS and DDD fit in? In this session, we'll introduce the idea of vertical slice architectures, and dive into the patterns, tools, and techniques used with slices. We'll also cover how you can fit vertical slices into different kinds of systems, from desktop, SPA, and normal MVC applications. Finally, we'll look at some of the new challenges that come with slices and layers, and how a different approach provides a much more maintainable end result.

Peter Gfader

Consultant, Trainer, Writer, Leader of Software Craftsmanship Zurich

Achieving Technical Excellence in Your Software Teams

Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers. Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live. I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions. Why would a company like to be "agile"? How can a company achieve that? How can you achieve Technical Excellence in your software teams? What developer skills are more important than languages, methods or frameworks? This will be an interactive session with a Q&A; at the end.

Paul Stack

Staff Software Engineer @ Pulumi, ex-Software Engineer @ HashiCorp

Securing Your Infrastructure with Vault

Making sure our systems are secure has become a huge priority for companies but not everyone actually dedicated the time to making it happen. In this session, Paul will demonstrate examples of how to secure infrastructure and applications to have end to end TLS using Vault. He will be able to prove to attendees that by investing a little time upfront, we can ensure that our development and production environments have TLS throughout and will allow us to not get surprised when our systems to production.

Roy Osherove

XP, CD & Tech Leadership Consultant & Coach, Author of Elastic Leadership, The Art of Unit Testing

The Coaching Architect Manifesto

What does it take to bring your team to the next level? In this talk, you'll learn practical techniques that architects and tech leads can use to achieve that goal. Roy will share do's and don'ts from the hard won battles in the field. You'll also learn the core principles of Elastic Leadership and Coaching Manifesto and how they map to the actions outlined in the talk.

Eduards Sizovs

Consultant, Trainer, ex-CTO, Founder @ DevTernity, Founder and Dev @ Dev.Tube

Beyond Software Craftsmanship: From Dev to Chief Architect

Johnny is a full-stack developer with 5+ years of experience under the belt, M.Sc degree and ‘get sh%t done fast’ mentality. Although Johnny possesses exceptional technical skills, Milton – his manager – doesn’t promote Johnny, because Johnny lacks some important skills. What skills Milton is talking about? Together with Johnny, you will walk the thorny road to his remarkable career as a Chief Software Architect; the road full of struggles, discoveries and actions that will turn your career around.

Thierry de Pauw

Founder, Consultant @ ThinkingLabs, Continuous Delivery Advocate

Feature Branching Considered Evil

With DVCSs branch creation became very easy, but it comes at a certain cost. Long living branches break the flow of the software delivery process, impacting stability and throughput. The session explores why teams are using feature branches, what problems are introduced by using them and what techniques exist to avoid them altogether. It explores exactly what's evil about feature branches, which is not necessarily the problems they introduce - but rather, the real reasons why teams are using them. After the session, you'll understand a different branching strategy and how it relates to CI/CD.

Ian Cooper

Lead Application Architect @ Huddle, Founder of the London .NET user group

The Clean Architecture

What is the clean architecture and how you would build one in .NET? Recently Bob Martin has categorized a set of architectures, including hexagonal architecture, onion architecture and screaming architecture as 'the clean architecture' - a layered architecture of concentric circles with a strong emphasis on separation of concerns. This architecture has become popular because of its amenability to modification as an evolutionary architecture and its support for practices such as TDD. In this presentation we will discuss the clean architecture and its benefits. More than that, in the bulk of the presentation, we will show you how to implement a clean architecture in .NET. From first steps to working code, we will show you the moves required to embrace this approach, and introduce you to some of the OSS libraries that can help you get there. All examples will be in .NET Core

Nicolas Fränkel

Developer Advocate @ Hazelcast, ex-SAP, Author of Integration Testing from the Trenches

Object-Oriented Programming in the Enterprise

Most developers don’t write Object-Oriented code, including myself. And yet, we have learned how to do it. Why is that? One of the possible reasons, is that many frameworks (Java EE, Spring) do not favor OOP in their design. But what is OOP really? We will have a look at a super-simplified bank account model. In my demo, I’ll demo with a Java-based application how can we evolve from the traditional current approach to proper OOP. Finally, it will be time to have a look at the benefits and drawbacks of both approach.

Janne Jul Jensen

Lead UX Designer @ Elsevier

UX for Developers

Some people in the software development industry still seem to think, that UX is some kind of unicorn fairy dust, that you sprinkle on a project in the end, and then it will magically make everything, that was ever wrong with that project, all better. This talk will explore why it isn’t so, what real UX is, why it is a team effort and what UX-responsibilities the various stakeholders can, and should own up to, for the greater good of the project.

David Neal

Senior Developer Advocate @ Octa, Microsoft MVP

Leadership Guide for the Reluctant Leader

Regardless of the technology you know, regardless of the job title you have, you have amazing potential to impact your workplace, community, and beyond. In this talk, I’ll share a few candid stories of my career failures… I mean… learning opportunities. We’ll start by debunking the myth that leadership == management. Next, we’ll talk about some the attributes, behaviors and skills of good leaders. Last, we’ll cover some practical steps and resources to accelerate your journey. You’ll walk away with some essential leadership skills I believe anyone can develop, and a good dose of encouragement to be more awesome!

Bartłomiej Słota

Consultant @ Bottega IT Minds / Vattenfall

Live Refactoring Towards Solid Code

In this live coding session we will refactor a part of some legacy system. We will approach the problem pragmatically, identifying issues and fixing them by applying rules and patterns related to modularity, cohesion, testability, and more. We will also see how Domain Driven Design can help us achieving the goal of a clean and solid code.

Adam Ralph

Software Developer @ Particular Software, OSS maintainer, Microsoft MVP

Finding Your Service Boundaries – A Practical Guide

We know it's useful to split up complex systems. We've seen the benefits of modular deployment of microservices. Dealing with only one piece of code at a time eases our cognitive load. But how do we know where to draw the service boundaries? In complex business domains, it's often difficult to know where to start. When we get our boundaries wrong, the clocks starts ticking. Before long, we hear ourselves say "it would be easier to re-write it". Join Adam for practical advice on discovering the hidden boundaries in your systems. Help tease out the natural separation of concerns in a sample business domain. During 20 years of developing complex systems, Adam has had plenty of time to get things wrong. Learn to avoid the common pitfalls that can lead us down the path to "the big re-write".

Jakub Nabrdalik

Solution Architect, Developer and Mentor at Bottega IT Minds, ex-Head of Software Development @ 4Finance

Common Mistakes When Moving to Microservices

Common mistakes when moving to microservices that I'll discuss and provide solutions for: No realistic architecture process (architecture decisions too rigid, or not taken; infra vs domain; architecture guild vs no cooperation, knowledge sharing ); QA thinks testing end-to-end is possible; Management wants to control deployment; Devs not DevOps; Not understanding event based architecture; Not using the tools properly (Kafka); Relying on cloud provider shitty tools; Error prone team setup; Pivots vs domain vs team composition.

Uwe Friedrichsen

CTO @ Codecentric, Fellow, Speaker, Nerd, Consultant

DevOps is Not Enough – Re-thinking IT from Scratch

DevOps - a simple term, but tons of confusion. Some think, it is about more collaboration between Dev and Ops. Others think, it is just about tools and automation. But in its core, DevOps is about accelerating the IT value chain. How long does it take to deliver a business idea to your customer using IT? How fast can you go - repeatedly and without compromising quality? But why should we speed up in the first place? Do we really need it? How fast is fast enough? How can we implement it? What else do we need to take into account? ... lots of questions if we follow this thought for a moment. In this session we will try to answer some of the questions. We will examine the drivers and goals behind DevOps and answer the question why we need to change. Then we will see how DevOps affects the way we think and act, what else is needed to really "become DevOps" and how all these building blocks are connected to each other. Finally, we will have a brief peek into the (likely) future of DevOps.

Maxim Dorofeev

Founder @ mnogosdelal.ru, ex-Head of IT @ Kaspersky Lab, Author of Jedi Techniques

The Jedi Techniques of Problem Solving

An anthill is not a simple sum of ants. What matters most is an interaction between them. Taking into account that people are extremely more complicated creature than ants it is possible to assume that making every team member productive definitely will not give us a productive team as a whole. The fundamental feature of any productive team is the ability to collaborative problem-solving. The most common reason for a problem to occur is that too often we see the same thing in different ways (typically all of us are wrong) and at the same time, we can poorly express our thought. I’m going to share with you some simple and useful tools that could help us better understand each other and to find better solutions for the problems we face.

J.B. Rainsberger

Software Coach, Mentor and Consultant, TDD Trainer tdd.training

The Well-Balanced Programmer

A well-balanced programmer feels comfortable dealing with designing software, managing projects, and working with people. Companies seem to want to hire "the best", but well-balanced programmers relatively rare. Although many programmers feel confident arguing about algorithms, modularity, and scalability in design sessions, they would stand out from their peers if they also had incredible habits for managing their work, knew how to negotiate features with product owners, had intelligent conversations with project managers about the risks in their project, and understood what lies behind the irrationality of the people and systems around them. Sadly, most programmers don't appreciate the value of these skills. Others don't know how to get started learning them. I started programming computers because people are messy! I'd like to share a curated collection of concepts for you explore that will help you become irresistibly valuable to your employer or clients. I plan to share the design principles and programming techniques that amplified my skills the most over the last 20 years. In addition, I'll describe how I learned the key non-programming concepts, techniques, and approaches that have endeared me to fellow programmers, managers, and clients. I offer you a very practical approach to issues like influencing peers, negotiating with stakeholders, and adopting new ways of working safely. I'll help you start to build a personal work system that will free your mind to do your best work. I know how this might sound. I promise to share concrete techniques that you can begin applying right away. Of course, these techniques aren't magic, so you'll have to read some more and practise on your own, but you will know how to get started right away on becoming the well-balanced programmer that every manager and co-worker will love to have on their team.

Sergei Egorov

Staff Engineer @ Pivotal, Groovy, Reactor and Testcontainers Committer

Integration Testing with Docker and Testcontainers

Unit testing is fine, but without proper integration testing, especially if you work with external resources like databases and other services, you might not know how your application will actually behave once it has been deployed to the real production environment. Testcontainers is a popular JVM testing library that provides lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container. In this talk, we will briefly go throught the past, present and the future of the library.

none

Scott Hanselman

Principal Community Architect for Web Platform @ Microsoft, Blogger, Podcaster

Scaling Yourself

As information workers, we are asked to absorb even more information than ever before. More blogs, more documentation, more patterns, more layers of abstraction. Now Twitter and Facebook compete with Email and Texts for our attention, keeping us up-to-date on our friends dietary details and movie attendance second-by-second. Does all this information take a toll on your psyche or sharpen the saw? Is it a matter of finding the right tools and filters to capture what you need, or do you just need to unplug.