{"id":1100,"date":"2018-02-14T12:34:14","date_gmt":"2018-02-14T20:34:14","guid":{"rendered":"http:\/\/zuill.us\/WoodyZuill\/?p=1100"},"modified":"2018-02-14T14:09:58","modified_gmt":"2018-02-14T22:09:58","slug":"practical-refactoring-workshop-austin","status":"publish","type":"post","link":"https:\/\/zuill.us\/WoodyZuill\/2018\/02\/14\/practical-refactoring-workshop-austin\/","title":{"rendered":"Practical Refactoring Workshop – Austin"},"content":{"rendered":"

Practical Refactoring – Tiny Steps to Better Code<\/strong><\/h2>\n

2-Day Lab, Austin, Texas, USA<\/strong><\/h2>\n

May 3-4, 2018\u00a0<\/strong><\/h2>\n

With Llewellyn Falco and Woody Zuill<\/strong><\/p>\n

Eventbrite registration:\u00a0https:\/\/www.eventbrite.com\/e\/2-day-practical-refactoring-lab-austin-tickets-40431719361<\/a><\/p>\n

The goal: “Clean Code That Works” (Ron Jeffries) , and getting there is half the fun.\u00a0 Working with a legacy mess can be frustrating, boring, dangerous, and time-consuming.\u00a0 When FIBS occur (FIBs = Fixes that Introduce Bugs) you often enter an endless Test and Fix cycle that can quickly escalate into a nightmare.\u00a0 I’ve been there, you’ve been there.\u00a0 How do we return to pleasant dreams?<\/p>\n

In this code-centric workshop we’ll look at ways to introduce sanity and calmness into the process of\u00a0maintaining and improving buggy, poorly written, poorly designed code. \u00a0Few slides, mostly code. We’ve been fighting the good fight for a long time and we are going to show you how to turn any project around and have fun doing it. \u00a0It is our opinion that we can fix and enhance any code.<\/p>\n

We’ll be working on an example project, and learn the steps of making changes to code in tiny steps. We’ll explore ways to introduce tests to legacy code, and find ways to clean up the most common problems of duplication, clutter, complexity, and cleverness, as well as identifying and removing duplication.<\/p>\n

Our approach will have us using Solo, Pair, and Mob Programming to do exercises and work with others as we\u00a0experiment\u00a0with many simple techniques that combine together to make a big impact on the quality and cleanliness of our code.<\/p>\n

Learning Goals<\/h3>\n