: Sunday Morning Tutorials (8:30 - 12:00) : Agile Development : Sunday
Code Smells
Sunset
Sunday, 8:30, half day
| 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Ken Scott-Hlebek, Industrial Logic, Inc.
Tutorial number: 4
A "code smell" is a design problem. Code smells are found in methods, classes, hierarchies, packages (namespaces, modules) or entire systems. To be good at refactoring -- which means "improving the design of existing code" -- you must learn how to spot code that needs improvement. This tutorial will help you do that. We'll explore a comprehensive set of code smells from the books, Refactoring and Refactoring to Patterns. We'll look at real world examples of code smells, and we'll discuss which refactorings are most often used to de-odorize code.
Intermediate: Attendees should understand and regularly use OO concepts: encapsulation, polymorphism, and loose coupling.
Ken Scott-Hlebek, Industrial Logic, Inc.: Ken Scott-Hlebek is an Industrial XP Coach. Prior to joining Industrial Logic, Ken assisted teams in their transition to agility by teaching test-driven development, refactoring, and evolutionary design. Ken brings experience as a software craftsman and mentor from a variety of environments, from small in-house teams to large outsourced and offshore projects. Convinced that human factors are the key to successful software teams, Ken is passionate about promoting the warm and fuzzy side of the craft.
