{"id":37835,"date":"2016-10-20T14:03:00","date_gmt":"2016-10-20T19:03:00","guid":{"rendered":"http:\/\/kenscourses.com\/tc1019fall2016\/?guid=86aaf2b62fae8998f0771180b135cb16"},"modified":"2016-10-20T14:03:32","modified_gmt":"2016-10-20T19:03:32","slug":"patterns-software-patterns-everywhere","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/patterns-software-patterns-everywhere\/","title":{"rendered":"Patterns. Software patterns everywhere\u2026"},"content":{"rendered":"
Ummm what?<\/span><\/div>
I didn\u2019t know what these were, either. After some research, I\u2019ll now try explaining to you what I learned. Sounds good to you?<\/span><\/div>
<\/b>
Again, this has a very continuous relationship with previous topics I\u2019ve talked about before. Specially, you\u2019ll find yourself thinking of software architecture (hopefully). Why? For starters, design patterns are something a software architect should always be able to identify. Let me too you why\u2026<\/span><\/div>
<\/b>
There are some reusable, optimized solutions to common programming problems. Solutions that people who build programming languages should also identify right away. This solutions I\u2019m talking about are, in fact, design patterns. But all these people must be careful: \u201cIf implemented in the wrong place, it can be disastrous and create many problems for you. However, implemented in the right place, at the right time, it can be your savior\u201d. (<\/span>source<\/span><\/a>)<\/span><\/div>
<\/b>
It\u2019s important to know there are basically 3 types of design patterns:<\/span><\/div>