Comments by "Lepi Doptera" (@lepidoptera9337) on "Reacting to Controversial Opinions of Software Engineers" video.

  1. They used to write those in COBOL and machine language (not even assembler!) and they worked just fine. ;-)
    2
  2. Two thumbs up. ;-)
    2
  3. OOP is objectively stupid but there are a few use cases. I generally find that it works well for graphics libraries, but yeah... beyond that the air gets rare.
    1
  4. OOP doesn't make code readable if you use inheritance a lot. In that case it actually disperses and even duplicates code. This is a big deal if you have to fix a problem with a method in one class because now you also have to check the code in all derived classes that have a modified version of that method. It's basically the same problem as with forking, just internally to one program.
    1
  5. You do understand that refactoring is the antithesis to "never break a working system" super-rule, right? ;-) Here is the thing... you aren't actually testing your code. You are testing your code's response to stimuli. Why do you need to refactor it for that? Unit-testing is usually done for unit-testing's sake. It keeps somebody's OCD happy at the cost of hundreds of thousands or millions of dollars. In reality that's almost never the level at which serious code problems occur. Let me give you a popular example of what happens in real life: Linux clones of Word are basically useless. Why? Not because of the billion bugs that they come with. You could fix every single one of those bugs and they would still remain broken because of the fonts. As soon as you import a non-trivial Word document into one of these tools you have to start the formatting all over, again. Nothing at the unit level and nothing at the application level can fix that. That "bug" was put in there by Microsoft's legal department by copyrighting Windows fonts.
    1
  6. Yes. OOP sucks. All versions of OOP are merely window dressing. It's fancy ways of documenting your code. Why? Because once your compiler is done with your code, all OOP has been removed. Your CPU doesn't have classes. It has arithmetic, logic and branch instructions. That's all it has. Everything is done with 32 and 64 bit pointers, no matter what your programming language wants you to believe otherwise. So what are you writing all that OOP code for? Only for yourself and to please your boss. Your CPU doesn't give a you know what. ;-)
    1
  7. Yep, and neither solves the really hard problems in programming. Both are basically at the aesthetic level and akin to asking how one should name variables. Nothing important can be learned from either technique. They are too shallow for that.
    1