I can ' t think about it and not feel like laughing hysterically . I love GameDeals . <| sep |> Thought u somehow put a glass sheet into a counter . dissapointed <| sep |> Such pretty hair oI wish mine would hurry up and get that long <| sep |> i think you ' re talking about the Silver and Rainbow wings . <| sep |> Oops yeah . Grammer . I never was the best at it . <| sep |> OK , design patterns help programmers communicate with each other across technologies . They are truly the language that cuts across all OO programming languages . Let ' s say for instance I am making an iOS app for a service and another dev is making an Android app that should exactly mirror my iOS app functionality because , after all , we are making clients for the same service . Both of us are experts in our stack , and know only the basics of the other ' s stack . However , we can communicate on how to harmonize our code best by speaking in the language of design patterns . We can agree that a networking module works best using the command pattern that will differ in detailed implementation specific to each stack , but the general architecture will be equivalent . This will save our employers a ton of headache in updates , bug fixing and extensibility later on . Additionally , as the technology changes Objective C Swift , LAMP stack MEAN stack , the architecture can remain the same resulting in an improved ability to modernize technology stacks as time goes on . I don ' t see the downsides of using tested design principles in building software . Your statements also fall into the realm of opinion . That ' s fine , everyone entitled to their own . I choose to work with a set of principles that allow me to work quickly , have loosely coupled code that is readable by programmers everywhere , and that allows extensibility . Perhaps you ' ve figured out a way to achieve these things without using such principles , and if so , good for you .