Mastering Legacy Code

Level
Total time
Logo QWAN - Quality Without A Name
Provider rating: starstarstarstarstar 9.6 QWAN - Quality Without A Name has an average rating of 9.6 (out of 5 reviews)

Tip: need more info about the programme, starting date or price? Request information for free!

Starting dates and places

There are no known starting dates for this product.

QWAN - Quality Without A Name offers their products as a default in the following regions: 's-Hertogenbosch, Alkmaar, Almere / Lelystad, Alphen aan den Rijn, Amersfoort, Amsterdam, Antwerpen, Apeldoorn, Arnhem, Assen, Breda, Brugge, Brussel, Delft, Den Haag, Deventer, Dordrecht, Drachten, Ede, Eindhoven, Emmen, Enschede, Gent, Gouda, Groningen, Haarlem, Haarlemmermeer, Heerenveen, Hilversum, Leeuwarden, Leiden, Luik, Maastricht, Middelburg, Nijmegen, Roermond, Rotterdam, Terneuzen, Tilburg, Utrecht, Veenendaal, Venlo, Westland, Zaanstad, Zoetermeer, Zwolle

Description

Everyone wants software that 'just works', that is a joy to maintain, and where you can add new features easily. In practice however, there are always bugs to fix and customers to please. Corners are cut and design debt accumulates, ultimately resulting in legacy code – code without tests.

You would like to improve the software piecemeal using refactoring - which means improving the design of existing code without changing its behaviour. There is a Catch-22 here: to refactor safely, you need automated tests to ensure the code behaves the same as before. To add tests, you first have to make it modular by refactoring.

There still is hope! Through presentations, demonstrations, exercises, and…

Read the complete description

Frequently asked questions

There are no frequently asked questions yet. Send an Email to info@springest.com

Didn't find what you were looking for? See also: Part time MBA, Leadership, Full time MBA, Online MBA, and Executive MBA.

Everyone wants software that 'just works', that is a joy to maintain, and where you can add new features easily. In practice however, there are always bugs to fix and customers to please. Corners are cut and design debt accumulates, ultimately resulting in legacy code – code without tests.

You would like to improve the software piecemeal using refactoring - which means improving the design of existing code without changing its behaviour. There is a Catch-22 here: to refactor safely, you need automated tests to ensure the code behaves the same as before. To add tests, you first have to make it modular by refactoring.

There still is hope! Through presentations, demonstrations, exercises, and a representative case, you will learn to identify smells, break dependencies, refactor, and add tests in messy legacy code, so that you can add new features with more ease and confidence.

The techniques taught in this course are also useful in greenfield projects, to prevent the software from turning into legacy code. They help you to recover quickly from mistakes and learn from them.

This course helps you get started and offers effective practices and courage to persevere.

Benefits

If you participate in this course, you will:

  • apply a number of techniques to break unwanted dependencies in code
  • know how to start making changes and adding tests simply and responsibly
  • be able to find seams in code and use them to break dependencies
  • understand the system dynamics of design debt
  • experience prioritizing, planning, and executing a large refactoring in small steps with a team, on real, representative legacy code
  • have fun! – we take pride in creating a fun and effective learning environment, mixing presentations with exercises and hands-on development.

Intended audience

Software developers, architects, technical team leads, Scrum masters, and agile coaches who seek to augment their refactoring knowledge, so that they are able to deliver clean(er) code more often.

Prerequisite knowledge and experience:

  • Object Oriented concepts
  • Basic knowledge of automated unit testing

Programme

Mastering Legacy Code consists of two intensive days of training.

The first day is introductory, with an overview of refactorings, code smells, and how to break dependencies by finding seams in the code. We will do this through a mix of presentations, demonstrations and small exercises. You will also learn about the systemic causes and effects of design debt and how refactoring in small steps can help you break out of a vicious cycle.

Day two is the hands-on day. In two parts we will plan and execute a large refactoring on a real-world legacy system. Participants are coached in applying what they have learnt: working on a large, messy legacy code base without getting lost, using the vocabulary of smells, refactorings, seams, and dependencies to co-ordinate, plan and execute a large refactoring with a team. And do so safely, even though in the beginning no automated tests are present.

We will use Java or C# for the examples and the practical exercises.

Stay up-to-date on new reviews

There are no reviews yet.

Share your review

Do you have experience with this course? Submit your review and help other people make the right choice. As a thank you for your effort we will donate $1.- to Stichting Edukans.

There are no frequently asked questions yet. Send an Email to info@springest.com

Where should we send the information?

Gender
(optional)
(optional)
(optional)
(optional)
(optional)
(optional)
(optional)
We store your personal details, and share them with QWAN - Quality Without A Name, in order to help you along via email and potentially via phone. You can find more info in our privacy policy.