Feliz año nuevo Maxi! y que el próximo sea mucho mejor que el anterior.

Great tips Maxi Contieri , I'm going to adopt a few of them to improve my writing I'm already considering using some of them as principles from now on

Fantastic article. I particularly like that you address that it can be very hard to refactor code, but many of the refactoring problems you mention are solved by focusing on writing a good suite of tests I agree with Maxi Contieri . We need more articles like this

Hi Katy, great post. I enjoyed the reading; It shows that you know what you are talking about. Although I have some clarifications to make (I hope you don't mind) A unit test is the smallest test you can do on your code. That depends. When you work with TDD or TCR you write even smaller tests (micro tests) and all together they make up a unit test. The perfect unit test class will only test ONE class. Many people associate that idea with "unit", which must be a class, function, or module. It is actually a behavior in which the behavior could be modeled by the interaction of multiple classes or functions. It doesn't necessarily mean having a to test just one class, module, or function.

Wow thanks, Maxi. It's really encouraging to receive a "must read" comment coming from you Hopefully, with practice I'll become as good as you writing

Thanks, Pranav. Glad that you like it; you can share it too if you want.

Great idea Siddhi Gate and also can be used as an alternative to the Pomodoro technique I like that it's a simple and clean idea that brings value to every dev Let's take care of those eyes!

Great example Maxi! it's exactly how I imagined it

I'm glad you liked Luis. If you have suggestions on this or other topics, please let me know

Tiger Abrodi is right, but you can also think of refactoring as the means to transform your code into clean code