Comments by "MrAbrazildo" (@MrAbrazildo) on "DRY Software Patterns u0026 Microservices" video.

  1. I use to duplicate code and declare global variables when developing a certain f(). It's a bit faster. But once done, I immediately get rid of those issues. 4:00, or even a macro. 11:40, I think it's kind hard to write tests when you have classes holding data global to the tested f(). Those data are read/written inside the f(), but not come as parameters.
    1
  2. ​ @antoruby  The macro I mentioned was in place of an alternative f(). Sometimes, only a macro can DRY properly. Global variables and duplicated code I keep only in development of a bit of code. It's temporarily, for a short time. PS: my comment was about 3 independent moments of the video, btw. 3 comments in 1.
    1