Cause a Scene Conf London 2018

A lot of companies fall back to cookie cutter methods when trying to hire engineers that will enrich their teams. In a competitive market where everyone is trying to hire "the best", it helps to take a good look at what qualities you're actually looking for and how to search for people that fulfill them. By looking at your recruitment process as a user experience, you can avoid common pitfalls that put the right people off or attract people that could be toxic to your team dynamics. Many of us already have the tools and techniques to build a great product, such as ownership, stakeholder analysis, personas, field studies, usability testing, feedback, retrospectives, impact mapping and continuous improvement. I will show how you can apply these techniques and talk about my experience changing a recruitment process to fit the needs of the applicants and the teams receiving them.

NBIT 2018

European Testing Conference 2018

Introduction to coding katas

Refactoring JUnit tests

Code that grows over time without refactoring can get quite messy and hard to test. The same applies for to test code, and curiously, they often appear together. Not always is it possible to fix the design problems first, creating a need to write clean tests for hard to test code. In this workshop, participants will learn some techniques to clean up messy JUnit tests to make them more readable and easier to change. After a short introduction and an example refactoring, participants will work in pairs to refactor some example unit tests and learn how to write better ones from scratch. Key takeaways: create complex objects easily with the builder patternuse hamcrest matchers to improve your assertionsdiscover the power of JUnit rules Prerequisites: Please install the latest IntelliJ Community edition (https://www.jetbrains.com/idea/download/) which is available for Mac, Windows and Linux, and have Java and JUnit running from within this.

Refactoring Mount Doom - Tackling Legacy Code

We’ve all had that nightmare where you are try to get to your destination, and keeping moving, trying different things, but for various reasons, you never arrive. Some refactorings are like that - you extract methods, name constants, increase readability… In short, you spend a lot of time cleaning up - but you never get to a good place with the code. In this talk, I will show you how to refactor for the right reasons and the right methods to use your time efficiently. Let’s make working with that code easier in the future.

Introduction to Software Craftsmanship

Mistake proof software design

My journey towards Software Craftsmanship

Outside In TDD

TDD (Test Driven Development) has become a widespread practice and CV buzzword in the development community. When I started getting involved in the European Software Craftsmanship Community, I thought I knew what it was - I was surprised to learn there are many variations of it, and two main schools: the classic approach and the London school. Three years later, and I have been using the outside-in approach successfully in multiple projects and combining it with the classic approach. This talk will give you an introduction with code examples using Java, Mockito and JUnit, illustrating the basic principles and when to choose it over other styles of TDD. I will tell from my experiences on how to choose and combine an appropriate TDD approach for typical situations when developing business software.

Scary Refactorings

Refactoring

How to make more people feel welcome and safe at your conference

How to set up your own _ebooks Twitter bot

Source: @boodooperson http://blog.boodoo.co/how-to-make-an-_ebooks/