Comments by "MrAbrazildo" (@MrAbrazildo) on "Refactoring Legacy Code STEP BY STEP (Part 2)" video.

  1. 1:10, Java IS very nasty code! 8:40, I didn't get it: it still has the breaks. How passed this time? 14:12, I think you make too many f()s. Some thoughts about that: 1) Whenever you extract a f(), you are putting related things a bit away from each other, and a bit near to the rest of the outside code. This also can lead to accidental calls to those f()s. /*Edit: and you'll deal with more code.*/ 2) Compilers use to inline a certain amount of f()s. And if you raise that number, it can eventually get an unnecessary extra large generated byte code. This can lead to slowness. 3) 13:13, as I said on the previous video, for C++, just: return jsonString.substr (blabla) + "]" , which would be 1 line, no extra f(). But I guess Java is too bad to has that.
    2
  2.  dev null  What a surprise! People use to get pissed off by my comments.
    1