3 ms·

I think it's still good advice for programmers of all experiences. I have worked with too many programmers that know everything about engineering and process b

I think it's still good advice for programmers of all experiences. I have worked with too many programmers that know everything about engineering and process but can't actually DO THE WORK or solving problems, applying data structures, innovating their way out of a corner. They can go a long way with senior management because they speak all the right lingo. But when push comes to shove, and a new system needs to be built, or a bug needs to be solved quickly and safely in production without backwards incompatible changes, or business requirements collide against technology options...they are lost.

bruce511 4y ago
You are describing "bad" programmers, and clearly there are no shortage of those. But the advice in the post doesn't make bad programmers into good programmers - it just makes bad programmers "try to be clever" - which frankly doesn't end well. Do some of these techniques help bad programmers _become_ good programmers? Sometimes yes. But then it should come with the caveat never to do it in "real" code. It might be a good learning tool, but it's a terrible production tool.
- tjrDL6MjB2Zwwa 4y ago
  They're describing former programmers who stopped when their role changed.