Comments by "" (@adambickford8720) on "Kantan Coding" channel.

  1. A bad abstraction isn't the problem, it's the 900 gigs of other things that depend on that wrong abstraction that's the issue. A bad abstraction can also introduce all kinds of coupling that is near intractable in a real system
    14
  2. Inlining is great, just not with screeds of imperative code. The problem is people try to abstract things down to 1 line, putting us back in the first scenario of too much useless abstraction.
    5
  3. He explained it: open/close principle
    2