I have been working at the same company for almost 4 years. During those 4 years I have worked on the same project and haven't really switched teams. I've seen employees come and go, architecture decisions made and debated ad nauseam, and so forth. I am currently in the processing of re-implementing some functionality and architecture decisions that I made when I first started (~4 years ago).
When I made these implementation decisions I thought they were the best approach based on my experience at the time. However, having stuck around all these years and seen the product and business evolve, these decisions have turned out to be either poor choices or not the most optimal. As a consequence I've derived a lot of experience and wisdom from revisiting these past decisions, as I am now able to go back with production data and performance characteristics and see how they work or do not work. This software that I wrote way back when functioned in production and worked flawlessly without ceremony for approximately 3.5 years. Only recently and under a changing production environment has this code started to become a pain point.
Had I been part of the new every two crowd I would have never been able to see how my designs and solutions would hold up, or fall down, over the years of their life span. Furthermore, I never would have gained the wisdom and experience that comes from implementing something and having to come back and re-visit it years later.
This is really the takeaway message I understand from the author. Basically, when you only do what strikes your fancy and change your priorities with the weather, you lose out on the sort of experience and opportunity for growth that I have had in the past few weeks.