1.Introduction2 lessons, 09:16
2.Creational Design Patterns1 lesson, 09:14
3.Behavioural Patterns6 lessons, 1:11:30
4.Structural Patterns5 lessons, 38:41
5.Conclusion1 lesson, 01:43
Hi, folks! You've now reached the end of the course. And I hoped you learned enough to be able to put some of the patterns that we've looked at into practice in your day to day programming when the need arises. We've looked at creational patterns, which assist with the creation of the objects that are used within our applications. Structural patterns which help us to implement robust designs. And behavourial patterns that help our applications to run smoothly. We've seen that patterns exist because the same kinds of problems tend to occur in software development time and time again. Patterns are the solutions to these problems that have been tried and tested by previous generations of programmers. We can leverage the knowledge and experience of others to make solving problems and writing maintainable software easier for ourselves. We can literally stand on the shoulders of giants. We can produce more reliable software quicker using these hard one patterns. Sometimes, the need for a pattern might arise during the planning of a new feature. But other times, the need for a pattern will arise as the code grows and changes. What can seem like sensible design decisions during planning, can sometimes turn out to be counter-productive later on down the line. As well as understanding which patterns to use in which situations, which is a combination of knowledge and experience, the ability to spot when a particular pattern might solve a problem is also crucial to the effective use of patterns. This is more based on experience and is something that you will develop as you continue to use patterns. I hope that you've enjoyed this course. If you have any comments or questions, please feel free to ping me on Twitter. I'm @danwellman. From all of us here at tuts+, thanks for watching.