For those of you interested, and in St. Louis, I’ll be speaking at the .Net Users Group meeting this month. My topic will be “Refactoring: Adding Design to your Code After It Is Written”. My underlying intent in this talk is to convince people that refactoring is a worthwhile activity, as it adds value to your code.
I intend to walk through some simple refactorings to improve a piece of procedural code and begin to flesh out its dumb data objects into living, breathing OO classes.
- Introduction of me (boring!)
- Imagine yourself walking into work and being asked to make a change to some code you’ve never seen before…
- Maybe if we improve it a bit, we can read it better…
- Good, now I can read it, maybe I can start thinking about changing it
- This is refactoring!
- New buzzword, not reworking. Can stop in middle
- Let’s improve the code a bit more and see where that goes…
- Why can I do this? (tests, better code, etc)
- These are my tools (brain, patterns, refactoring book)
- Here are the reasons why I can’t do this…
- What else can we improve in the code
- Other resources
We have 3 signed copies of Jim Newkirk’s Test Driven Development in Microsoft .Net and may have a copy or two of the Resharper refactoring tool to give away.
Hope to see lots of you there.