Comments by "MrAbrazildo" (@MrAbrazildo) on "The harsh reality of good software" video.

  1. 8:56, true. I think my spaghetti code is clean, readable and kind beautiful. But it's just me. 11:53, performance uses to fight vs all others. So if a code got kind ugly, on an apparent necessary extent to deal with performance, I don't take it as ugly. I think a code should be judged having its goals in mind. Example: Rust or C++ specifiers, to get data fit into safety constraints, is not ugly. 17:20, I think they are bad when they expose content that should be "private" of a bigger f(). Otherwise, I think it's good to not pass 1 screen. Spaghetti style helps with that. 18:14, using IDEs, just leave mouse over the abstraction, and it shows what the abstraction means, how it was declared at least (enough for macros, lambdas, types). 21:13, well, if I had the chance to refactor it, I use to be satisfied for years. 22:59, spaghetti code is the right tool for the job. :elbowcough:
    1