> The examples shown in the post aren't wrong because they fail the grep test, they are wrong because... I read it has him saying "hey I found this easily iden

> The examples shown in the post aren't wrong because they fail the grep test, they are wrong because... I read it has him saying "hey I found this easily identifiable test which seems to correlate with code that's possibly too clever for it's own good". I also believe this test is worth thinking about because I tend to use grep/Find in Files a lot on my own code. It's often just simpler and faster and equally effective to the sophisticated IDE code comprehension stuff. > a lot of people stick with those "principles" (which are rules of thumb, often weak ones at that) they have read somewhere without developing a real understanding of software design We all have to start somewhere. I don't think it's possible to get "a real understanding of software design" without making some mistakes along the way. At best, we can help newcomers avoid the most painful ones and wasting too much time on dead ends. But (IMHO) all good programmers learn by failure (their own as well as others).