Comments by "Toby" (@toby9999) on "Clean Code is SLOW But REQUIRED? | Prime Reacts" video.

  1. I found it way easier to get into old high-performance legacy C code than new highly abstracted Java / clean code / code following 'design patterns' type stuff. Procedural C code can be read and understood. Once details are abstracted away in a language like Java, it becomes a nightmare to figure out what the code is actually doing. The cognitive load is higher. I use C++ 99% of the time, but I prefer a lightweight approach. Perhaps "C with classes". Objects used within a procedural context.
    2
  2. Possibly because clean code advocates are very often OOP advocated and are very often Java developers. That's been my observation. It was definitely the case with the last project I was involved with. Highly abstracted Java code. Almost impenetrable.
    1
  3. Clean code is typically difficult to understand and can be slow and bloated. High performance code very often looks ugly. At least, that's what my 30 years of coding has taught me.
    1