If it works doesn’t imply it’s good. Improving the internal structure of a project is important for many reasons. Refactor also means simplify the debug processes, tuning up performances and make the code readable to avoid a gradual spaghetti project failure. This talk shows some important bad code smells, how to assign priorities, tools useful in refactoring and code quality.


Comments are closed.

Although I did not agree with everything the speaker told, this was the overview I needed.

lots of good advice if you want to refactor code yourself. it was a good overview of the possibilities. I liked it

Refactoring...the never ending story.
I'm living the life and I always want to learn how to do it better.
I did, this talk was a great summary on how to do it. I was able to check off what I was already doing and what I'm still missing.

I believe that 'refactoring' and 'testing' should be every developer's fetish.

jonas lauwers at 10:57 on 28 Jan 2018

Very nice overview of how to start on refactoring,

Robert Broen at 17:16 on 28 Jan 2018

Obviously knowledge every professional developer should have.

Bart Reunes at 08:59 on 29 Jan 2018

Sound advice. Don't expect advanced tips, but rather a nice overview of some personal experiences you can learn from to refactor your own code base.

One slide that stood out as one to rethink: "when not to refactor". There was quite some confusion about it afterwards, even after the explanation during Q&A. It's seldom about whether or not to do it, but about how to do it as best as possible, so take some time to clearly explain your point of view.

Jasper Kennis at 14:57 on 29 Jan 2018

Good talk, nice overview, some good pointers were given. Inspiring talker.

Clear overview

An important topic to become more aware of. I would have liked to have seen the content more substantiated - I felt that there was not always enough explanation about the why and how of personal experiences.

Kudos for the great accent.