Masterclass: Reducing Technical Debt with Michael C. Feathers

By Alexandra Szynkarski On November 30, 2012 At 9:37 am

Working Effectively With Legacy Code

Michael Feathers is hosting a Masterclass on Reducing Technical Debt in London, UK on Tuesday, 26 January and Wednesday, 27 February, 2013.

This Masterclass is aimed to help experienced developers dealing with software code in complex projects. It will help you learn how to make big changes in large software projects and learn techniques along the continuum of team coordinated re-factoring, re-writing, and advanced team projects which help maximize the potential of existing code.

Working Effectively With Legacy Code

The session in January is already sold out, so make sure you put your name on the wishlist to join the one in February here!

If you can’t make the session, I recommend reading Michael Feathers book, “Working Effectively with Legacy Code“.

7 Steps to Pay Down the Interest on Your IT Technical Debt
Learn how to handle “Technical Debt”

In 2011, there were more IT system failures, outages and data breaches occurred than any previous year since the dawn of the age of technology. And while some of these issues could be traced to intentional and malicious undermining of systems, many, if not most, had some measure of application software failure or weakness at their root.

Your Information will be kept private and secure.

Add your comment

XHTML : You may use these tags : <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

This is a Gravatar-enabled website. To get your own globally-recognized avatar, please register at Gravatar.com




Comments

  1. Hi there,

    As the February date with Michael Feathers is sold out, please note that he is delivering a 2-day masterclass on Reducing Technical Debt in London on April 10th – 11th. We still have places available. You can read more and book your places here: http://bit.ly/MFtechDebt

    Kind regards,

    Anaïs

     — Reply