3 Ideas on Refactoring

Nuggets from one of the most iconic programming books of all time.
🔥 Get the book! geni.us/k8KhT3

[@lyonyan]

Very good point about not doing premature optimization!

[@nickbarton3191]

The root of all evil - Donald Knuth said it first I think.

[@franssu2229]

He didn't talk about premature optimisation, but premature abstraction

[@nickbarton3191]

@@franssu2229 Good point.

[@thundaGawd]

I will always remember this book, I didn't even know about it. Nor how much it would help me. It was laying outside a bookstore in Melvlille, Johannseburg, South Africa among a collection of books that the store was giving away. Once I started reading it, what a gem it was. Saw coding completely different.

[@enowmbi2943]

Your approach and energy are out of this world. Great content. Keep it up, sir.

[@HerbertonCandidoSouza]

Your teaching is perfect... Congrats!!!!

[@carnicer78]

I'm crying. That's how I think and how I program. Flattered that Martin and you agree.

[@rudreshgp]

My approach 1. KISS 2. SOLID principles 3. Gang of Four 4. Performance optimization

[@StuartLoria]

The first rule is ignored by the smartest programmers and held by their egos and lust for speed.

[@skipodap1]

I might be wrong, but I think point #3 is actually from Tidy First by Kent Beck.

[@ChristopherOkhravi]

You are right. It’s by Kent Beck. I explain it properly in the full video but couldn’t fit it into the short 😊😊 Thank you very much for the clarification nevertheless. Thanks for watching 😊

[@ChristopherOkhravi]

Thanks for pointing out that it’s Tidy First btw! 🙏😊

[@skipodap1]

@@ChristopherOkhravi Thanks for the great content!

[@fatihtt8102]

I didn't quite understand the 3rd Point. What exactly does that mean, make the change easy, and then make the change?

[@ChristopherOkhravi]

Check out the full video for a more complete explanation 😊 In short: Don’t spend time making a difficult change. Instead spend time refactoring to make the change easy and then make the change. 😊

[@nickbarton3191]

I started implementing a complex feature, was like wading through soup. Then I realised that it would be a whole lot easier if the architect (design pattern) was like so and so. Rolled back, started refactoring, made sure tests passed, then implemented the feature.

[@fatihtt8102]

In an older Codebase, you can't really refactor to make the changes easy, or at least it would take a lot of time and also would need a lot of testing. A lot of methods are private, so no Unittests for them.. But what I can take from this is before making the changes see if you can refactor the code to make it easier maintainable and then apply that code (eg method) in other locations where you use it aswell. 👍 Sadly we developers don't get payed for refactoring only for implementing the required changes/features. Noone cares how the Code looks.

[@nickbarton3191]

@@fatihtt8102 Be kind to the next guy, of course people care but not necessarily understand. I've been re-educating management for years. They will finally get it, especially when they see cost reductions. You'll be a hero and reap the rewards.

[@7xBiox7]

Your contents helped me a lot in the past, and again excellent content!

[@ChristopherOkhravi]

Happy to hear. Thank you 🙏😊