Think of this essay as a barbell, in the investment sense of the word. The beginning and the end of it have some really good insights that can be generalized to

Think of this essay as a barbell, in the investment sense of the word. The beginning and the end of it have some really good insights that can be generalized to a lot of technical / development work. The middle of the essay (Rules 4-16) are useful observations from Mickey's experience. (I don't know him; I am just trying to relate this paragraph of comments to his experience more explicitly.) This is not a bad thing. If you are a 1x developer yourself who is looking to improve, I think you want to read treatises like this and try to understand your fellow developer's perspective. Only truly brilliant developers can give generalized language and database platform advice. The other people who give valuable advice at this level are not developers, they are technology evangelists who have a track record of success helping real developers.