As a self-taught polymath, I did a lot of research many years ago on how good teams create good products. I reached some unusual conclusions at the time, but they've stood the test of time. The main one in regards to John's tweet is this: desired behavior has to "force" out code and architecture. Typically teams and individual developers carry a lot of presumptions and assumptions into their solution space. They prob…
(“Force me to write code” suggests that we’re looking to think deeply about what we’re doing and trying to minimize unnecessary action, so the rote actions are bad.)