Join this Technical Debt course and learn why it is a catch-all term that we use for entropy in software development. Systems grow, become unruly, and difficult to work with. When this happens it is hard to take concrete actions which help us control the evolution of an entire code base. This course will deepen your understanding of best practices when it comes to team-coordinated refactoring, rewriting, and advanced team practice.
- Minimize the effects of Technical Debt on your existing code base -
Going beyond what he outlined in his book Working Effectively in Legacy Code, to focus on large-scale change, Michael Feathers (founder and Director of R7K Research & Conveyance) will share what he has learned about making big changes in large software projects. You will learn specifically how to shape your legacy systems to be more robust, functional and reliable, producing company-wide effects through your efforts.
Who you will be learning with
This course in Technical Debt attracts not just developers but those in other disciplines, such as testers, project managers, Scrum Masters and anyone else interested in saving on resources usually spent dealing with legacy issues and complex, unruly systems.
How to apply these skills
Maximize the potential of your existing code base, while developing a deep understanding of how entropy in software development (Technical Debt) can be minimized and tamed.
Book early to receive a discount on the course price and in doing so you will not only commit to growing your own skill set, but help us grow our community of over 140,000 passionate techies.
Learn how to:
Identify various types of technical debt
Assess the amount of technical debt in your codebase
Develop design plans for large-scale refactoring and debt mitigation
Alter team and organizational processes to make refactoring a first-class practice
What the community says
"Although I am not a developer (tester by trade), this course gave me an excellent insight to the dev point of view - particularly around regression touchpoints and efficient best practice. Very helpful!"Paul Douglas, News UK
"I learnt some good tricks - thanks!"Jem Marsh, News UK
Topics covered include:
- A Pragmatic Definition of Technical Debt
- Design Decision Cards
- Feature Probes
- Scratch Refactoring
- Design Direction Tagging
- Limited WIP Refactoring
- Design Quality Trend Analysis
- Systematic Refactoring/Rewriting
For managers and developers with knowledge of software development.
While there is no actual coding in this course, delegates will need to have knowledge of reading code, and must feel comfortable working with code samples (provided in C#, C++ and Java) to illustrate refactoring techniques, and running the resultant code through the relevant test suite.
Bring your own hardware
Delegates are required to bring their own laptop to this course with a Text Editor (similar to TextMate, vi, or emacs) and an IDE suitable for coding in C#, C++ or Java as preferred.
A full installation guide for the course software will be provided with your joining instructions.