Comments by "MrAbrazildo" (@MrAbrazildo) on "I Was Wrong About Single Responsibility Principle | Prime Reacts" video.

  1. I agree with Prime on this: "A too opinionated junior is as dangerous as a senior with no opinions at all" .
    18
  2. I've been using SRP conceptually, rather than a technical demand. So, I write a class that starts entirely read-only. As long as the project demands changes from it, I allow those specific locations to change it. It uses to vary from 1-10 f()s. The class ends up providing several functionalities around a goal. So it's not 1 technical thing strictly, but 1 single goal/matter/subject/responsibility. This has been pretty good for understandability.
    15
  3. And for the last, make it pretty, if have time and if it's even possible.
    3
  4.  @megatrongodzilla This is a known quote. You should give credits.
    2
  5. ​ @chudchadanstud Issue is that optimization conflicts with everybody. It's likely to destroy prettiness.
    1