opensoul.org

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.

popular and talk May 23, 2012

8 Comments

  1. Matt Secoske Matt Secoske May 24, 2012

    Great presentation Brandon. Do you have a suggested open source project (or more) that gets close to these ideals?

  2. Brandon Keepers Brandon Keepers May 24, 2012

    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.

  3. Jonathan Duarte Jonathan Duarte May 31, 2012

    Yeah! Really Good presentation!
    I agree with all points.

    Congratulations.

  4. Kyle Daigle Kyle Daigle June 1, 2012

    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.

  5. Sugah Sugah June 5, 2012

    Nice one Brandon! Totally agree!
    Thanks for sharing!

  6. Alexis Alexis June 6, 2012

    The gem top_tests force you to have fast tests :)

    https://github.com/officialfm/top_tests

  7. Sudha Rana Sudha Rana June 6, 2012

    Awesome Presentation Brandon! Thanks for sharing! I will circulate it among the developer I know..

  8. Rupak Ganguly Rupak Ganguly September 21, 2012

    Loved your talk at Ruby Hoedown 2012.

I am Brandon Keepers. I build Internet things, usually with Ruby or JavaScript. I work at GitHub and live in Holland, MI.

Popular Posts