Comments by "Toby" (@toby9999) on "Stop Recommending Clean Code" video.

  1. It's not a limit. It's a huristic to limit nesting / indentation.
    1
  2. Is it, though? What is clean code? Some of the code I've seen that was considered well written OOP (is that clean code?), it was atrociously confusing. Overly engineered, in my opinion, with too much abstraction. Additionally, such code will typically run slowly. I recently refactored some OOP code, I pretty much removed all of the OOP stuff from performance critical paths and gained a 300% increase in speed. I ended up with C++ code that looked more like C. Bottome line, Im not sure how one would define clean code or measure its cleaness.
    1
  3. More abstraction typically results in worse performance. Sometimes, that matters. Too much abstraction makes code more difficult to understand, as does chopping large functions into too many small pieces that lose context.
    1
  4. I have a function containing only a 1500 line switch statement in my project. It's fine. It works.
    1