tag:blogger.com,1999:blog-1042801964488488185.post8211833940128385890..comments2023-05-23T06:48:28.455-05:00Comments on Jake Scruggs: My Apprenticeship - Wednesday, July 21, 2004Jake Scruggshttp://www.blogger.com/profile/16274380203959781950noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1042801964488488185.post-14887177773795624382009-07-22T09:33:16.130-05:002009-07-22T09:33:16.130-05:00That "pattern trade off" you speak of is...That "pattern trade off" you speak of is something I struggle with a lot. I have been thinking about this subject matter lately. Maybe, it is beacause I am re-reading the excellent "Design Patterns in Ruby" book by Russ Olsen. <br /><br />In Chapter 1, Russ writes about "Patterns of Patterns". My favorite one is the YAGNI pattern. "You Ain't Gonna Need It" is the design pattern where we realize that "we tend to be wrong when we try to anticipate exactly what we will need in the future."<br /><br />Russ continues, "The proper use of design patterns is the art of making your system just flexible enough to deal with the problems you have today, but no more. Patterns are useful techniques, rather than ends in themselves."<br /><br />I think, in the end, this bit of YAGNI advice is the most useful for me.Fred Leehttps://www.blogger.com/profile/00687560433619842952noreply@blogger.com