Youtube hearted comments of (@adambickford8720).

  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. Waking up in the house paid for by java isn't so bad.
    13
  3. Most developers aren't nearly as clever as they think they are, but that doesn't stop them from making a mess of even trivial things. However, in an async world they are far less brave as the 'complexity budget' is largely spent. I've found that actually makes things easier as you're tackling essential complexity, which is researchable, vs some wannabe 'architect's layer on top of JPA (or whatever).
    6
  4. 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
  5. If you're 5x smarter but I can iterate 10x faster i'll still be twice as valuable to the company... AND the jr devs understand my solution ;)
    3
  6. Most orgs don't have the culture to support scrum, they're really hoping for a high throughput waterfall.
    2
  7. He explained it: open/close principle
    2