@tejaskumthekar4155
This is super amazing. Strangely, it has a pretty low view count. I wish more devs watch this stuff.
@jeandersonbc
Very wisely thoughts about why refactoring matters and how it makes difference.
@TristanBailey
This talk was very focused and clear. Like the audience or managers already know the idea but this hammers it out with the reasons that sometimes get lost in longer talks. Made some points make more sense to me to convince others.
@kris1227
Thank you Mr Fowler for the education.
@sasukesarutobi3862
Great talk by one of the titans of software engineering. Who better to discuss refactoring than the guy who originated it.
@mkgungor
Very well expressed! Great examples
@lepidoptera9337
Refactoring is usually the admission that you got it all wrong on your first try. I had projects where I gave up refactoring in the middle of it and I just wrote the entire thing from scratch by reusing just the bits that actually worked great. The final result was always much better than what the refactored code could have been under the best of circumstances. I am not even bothering with refactoring anymore. When I see an architectural flaw I go in and fix it completely.
@stevenvolckaert8419
Great talk.
@Don-jt7ch
Very engaging
@ashokguduru3870
I liked the last slide: When you talk about Refactoring, Don't talk about the Quality, Clean-Code, Professionalism, Right-Thing etc. Just think and talk about Economics.
@billysardar
Bravo
@steveroger4570
All these refactoring and TDD talks are great, but they are missing out one thing. Not everyone in team agree on what and how clean code is, or even agree on test is a thing to do in software dev. Some people just prefer long, long, Long messy procedural code in 1 method, (people see their own mess as fine) while other think refactored code is too complicated and hard to read as they scroll. (like private helper method is unnecessary) Some senior lead even punish you if you refactor even one small section of code under the belief on "if it ain't broke, don't fix it" and "we got to deliver the feature by Tuesday."
@AmericaIsFed
what about legacy code, where there are large swaths of bad code that warrant deliberate refactoring with no new features directly being added immediately, but would definitely prepare for easier addition of new features later.
@BryonLape
I would like to see the likes of Martin debate the ideals of Harlan Mills directly.
@xximo
3 dislikes? that's interesting!
@MaryMcGloinActor
why not just do it right the first time? why rush out crap and then go back and redo it? customers don't care about your process, they care that they get a quality product
@csbnikhil