Comments by "MrAbrazildo" (@MrAbrazildo) on "How To Be A GREAT Programmer" video.

  1. 8:43, this mistake I don't make. If I worked alone, I can even describe the project from a high to low level, in different "layers". 9:23, ideally, code should always follow the best design. In practice, however, code influences back the design. This is faster development, but has a cost. I use to have my overall design near intact by the code, despite often undesired splitting classes for better access control, number/types of f() parameters, and so on. 9:44, particularly to the internal design of f()s, I don't see that much of an issue. If variables or small arrays are created and destroyed inside it, and a bug arises from them, even if complex, the region is "fenced" in that f(). So design won't be a problem: it won't require to understand messages, data flow, and others. 13:32, I use to write pages describing ideas, reports, failures, and sort of. 15:06, the vague guess of billionaire companies taking my code for free, to make $$, makes my alien try to break out from my chest.
    1