After the anecdote, the vibe I got of the article was anti-intellectualism applied to the programming field. I'm all for simpler, communicable code and APIs. B

After the anecdote, the vibe I got of the article was anti-intellectualism applied to the programming field. I'm all for simpler, communicable code and APIs. But at the same time not everything can be solved with a junior-level technique. That doesn't mean throw a new framework at it, but it does mean explore the problem spaces, communicate possible solutions with the team, choose one, document it, move forward. Yeah, it is fun to skip some of the steps above, but usually at a big-picture detriment. You need a balance!