Splitting large functions into smaller parts is a good way to follow the established principles: Small Functions, Do One Thing, Separation of Concern. All her steps are very good and show how to do a good refactoring. Your statement on "hacking a working chunk" suggests that you should read about Software Craftsmanship, and also Clean Code (Uncle Bob). If you would like to know about the Code smells, you can find a comprehensive list in "Refactoring Improving .." by Martin Fowler.
This presentation is soo good, that I intended to just check it out for the first 5 minutes and end up watch all of it for 30 minutes. yeah a repeat some parts.
Super Aweome! So am I enjoying doing refactoring! This is my favorite thing in profession! What I like in this talk most of all, that Katrina among other things mentioned Domain Driven Design practice of Extracting Non Specialized Subdomain Logic into a gem or class. [25:08] I do appreciate Katrinas work!
I have learnt something very valuable from this video. I do not use the word 'cruft' enough in my daily code dealings. I shall endeavour to use it more. kthxbye
My ugly code makes me feel really bad about myself. I have learning difficullty and I am unable to understand computer science books. Refactoring is the only way to improve my code and make me feel better about myself.
Disagree... Katrina asks the wrong question (25:02): "can this be a separate class"... the correct question is "SHOULD this be a separate class". I feel like she's a school student attempting to teach Rembrandt how to paint. Massively shallow comprehension of so many important things about code. Code is for humans to maintain - hacking a (working) ugly(to her)-looking chunk into a dozen scattered fragments simply because it makes you "feel good" is a Bad Idea(tm).
11 years later this presentation still holds up! Great delivery of some very interesting and informative material!
i've rewatched this so many times over the last 5 years, super great!
Splitting large functions into smaller parts is a good way to follow the established principles: Small Functions, Do One Thing, Separation of Concern.
All her steps are very good and show how to do a good refactoring.
Your statement on "hacking a working chunk" suggests that you should read about Software Craftsmanship, and also Clean Code (Uncle Bob).
If you would like to know about the Code smells, you can find a comprehensive list in "Refactoring Improving .." by Martin Fowler.
I was researching for refactoring material and this is one of the best I have found.
Excellent step-by-step intro to refactoring cruddy code. Essential viewing!
This presentation is soo good, that I intended to just check it out for the first 5 minutes and end up watch all of it for 30 minutes. yeah a repeat some parts.
starts off like a The Moth podcast episode. great talk.
Heard about this on this talk on the Ruby Rogues podcast, really enjoyed it!
Super Aweome! So am I enjoying doing refactoring! This is my favorite thing in profession!
What I like in this talk most of all, that Katrina among other things mentioned Domain Driven Design practice of Extracting Non Specialized Subdomain Logic into a gem or class. [25:08] I do appreciate Katrinas work!
Loved this talk! DAMN
This is such a nice talk. 👍
Excellent, just excellent
I have learnt something very valuable from this video. I do not use the word 'cruft' enough in my daily code dealings. I shall endeavour to use it more. kthxbye
Amazing talk!
Awesome!! Thanks
It sounds like she's performing an Emily Wolfe reading.
I'll start to use finger-snaps for scrum upvotes
Good. So I'm not the only one that has been refactoring code copied from stackoverflow.
My ugly code makes me feel really bad about myself. I have learning difficullty and I am unable to understand computer science books. Refactoring is the only way to improve my code and make me feel better about myself.
Great! I'm in love again.
The original author of the refactored module, disliked this video
Omg, I want to marry her. This one and Sandi Metz's OOD are the best presentations I watched lately. Why there are no women in programming?
Disagree... Katrina asks the wrong question (25:02): "can this be a separate class"... the correct question is "SHOULD this be a separate class". I feel like she's a school student attempting to teach Rembrandt how to paint. Massively shallow comprehension of so many important things about code. Code is for humans to maintain - hacking a (working) ugly(to her)-looking chunk into a dozen scattered fragments simply because it makes you "feel good" is a Bad Idea(tm).
Curious...5 years later...do you still think the same way?