The real hidden message in the article is: no matter how great you think your code is, when you revisit it a few years later, it will (nearly) always be crappy.

The lesson is to keep it simple so everyone can recognize that it's crappy and help fix it/make it worse.