RailsConf 2016 - Get a Whiff of This by Sandi Metz

Get a Whiff of This by Sandi Metz
Most code is a mess. Most new requirements change existing code. Ergo, much our work involves altering imperfect code.
That's the bad news.
The good news is that every big mess consists of many small ones. Certain small problems occur so frequently that they've been given names, and are collectively known as "Code Smells".
This talk shows how to take a pile of perplexing code, identify the "smells", and surgically apply the curative refactorings. It breaks a messy problem into clear-cut pieces, and proves that you can fix anything without being forced to understand everything.
Help us caption & translate this video!
amara.org/v/JkoP/

[@gosukiwi]

Awesome talk as always. She's the best!

[@FranciscoQuintero]

Always learn something from Sandi.

[@ismailm123]

Brilliant talk some really good points to take away, loved the categories of code smells

[@baterchen]

Great talk! Tank you so much!

[@lucang534]

I love her, ^^

[@janetli6603]

Nice video!!

[@danieldossantos8484]

I am having a hard time trying to understand how the message chain was solved. Because she keeps calling where(something).sum(otherthing) inside of Sale.total(something). But I love how she thinks of OO and I love even more that she shares it with us.

[@nuttanart]

From my understanding, it's solved because Sale itself knows "where" and "sum" anyway. It doesn't matter how many dots exist in the chain as long as it doesn't introduce more knowledge(coupling) to Sale.

[@Aupajo]

Because Sale only has to know about itself ("where") and one other object (the one returned by "where", which has a "sum" method - in Rails, this object would be equivalent to an instance of ActiveRecord::Relation). So Foo has gone from knowing about two objects - Sale and the object returned by "where" - to just Sale. This means that, for instance, if the API for the object returned by "where" changed, only Sale would have to be updated.

[@elisson357]

Great Talk. Anyone knows if we can download her slides anywhere?

[@jowilson5581]

I feel like Sandi is slowly selling me on OO the more I see of her code, lol

[@gwho]

what's the book having code smells and their corresponding curative refactors called?

[@MeaganWaller]

Refactoring by Martin Fowler

[@korytegman1252]

anybody got a link to the budgeting reality video that she is talking about at about 25:30 ?

[@dluzar]

vimeo.com/53276460

[@TwiztedHumor]

whoa! im loving these concepts! abusers Haha thank you!

[@gwho]

most people against OO don't truly know OO, and are attacking a strawman or frankenstein procedural OO. They can't see past their limited use cases and how OO provides more flexibility. Just like how graph databases allow you to do everything a table database can, but more... but some people object, saying, why would you need those other features? *facepalm*

[@oppressivefistoftyranny1395]

She had a chance to use penultimate and didn't take it. First time I haven't approved of Sandi Metz. Josh Susser would also disapprove.

[@benmaniu]

Man RailsConf you should really hire a new audio professional

[@baterchen]

Just in case someone needs the pdf in the slide. www.industriallogic.com/img/blog/2005/09/smellstorefactorings.pdf