Why Our Code Smells
Odors are communication devices. They exist for a reason and are usually trying to tell us something. Our code smells and it is trying to tell us what is wrong.
I have been on a quest with a few coworkers to uncover why our code smells. In this talk, I walk through code from projects that I work on every day, looking for smells that indicate problems, understanding why it smells, what the smell is trying to tell us, and how to refactor it.
8 Comments
Great presentation Brandon. Do you have a suggested open source project (or more) that gets close to these ideals?
Matt: Thanks, glad you enjoyed it. There aren’t any open source apps that I know of that follow these patterns, but I’ll keep an eye out.
Yeah! Really Good presentation!
I agree with all points.
Congratulations.
Matt: Great question, unfortunately, I don’t have any suggestions but find myself wanting the same thing. When your team is smallish, sometimes it can be hard to learn from the collective. Most OS projects I’ve seen end up having Frankenstein style test suites.
Nice one Brandon! Totally agree!
Thanks for sharing!
The gem top_tests force you to have fast tests :)
https://github.com/officialfm/top_tests
Awesome Presentation Brandon! Thanks for sharing! I will circulate it among the developer I know..
Loved your talk at Ruby Hoedown 2012.