Refactoring With Design Patterns

I love clean, clinical code but I feel like I can write ugly code with the best (or worst?) developers out there.  I try to be familiar with as many design patterns as I can.  I read about them in books and online.  I review their structures and sample use cases and they so rarely seem to find their way into production code.  Sometimes I even implement named patterns without recognizing them as such.  Both of these cases lead to software that works but may not be the easiest to maintain when I come back to it six months later.

For this talk I would like to share samples that emulate production code and guide discussion around cleaning up the provided samples.  "Cleaning up" will be discussed in terms of testability, maintainability, and readability.  We will discuss applicable patterns, why we would want to use them, and walk through how to implement them in existing code bases.

Eric is a senior consultant with Strategic Data Systems in Sharonville, Ohio working on the .NET project team.  He is a 2017 graduate of MAX Technical Training's .NET Bootcamp and previously received a masters degree in German Studies from the University of Cincinnati in 2014.  He has been tinkering with writing software since the mid-90s and enjoys writing software at both a high and low level against modern and classic computers.  Outside of computing, he spends most of his time reading, working in his machine shop, and endurance cycling.  

Next Month

TBD