Lessons: 24Length: 3.5 hours
- Overview
- Transcript
5.1 Conclusion
I hope you've enjoyed spending some time learning about design patterns and how they are implemented in the Swift programming language. My name's Derek Jensen, and from all of us here at Envato Tuts+, thanks for watching.
1.Introduction
1.1Introduction01:39
1.2Prerequisites02:48
2.Creational Patterns
2.1Factory10:16
2.2Abstract Factory12:24
2.3Singleton09:09
2.4Prototype09:18
2.5Builder11:40
3.Structural Patterns
3.1Adapter10:07
3.2Flyweight10:33
3.3Proxy05:53
3.4Bridge10:35
3.5Decorator11:44
3.6Composite09:43
3.7Facade07:19
4.Behavioral Patterns
4.1Iterator09:32
4.2Command07:48
4.3Chain of Responsibility13:47
4.4Mediator08:16
4.5Memento08:53
4.6Interpreter14:31
4.7Observer08:58
4.8Strategy07:36
4.9State06:21
5.Conclusion
5.1Conclusion02:42
5.1 Conclusion
Wow, congratulations, you have really come a long way in this course. To be honest, this course was rather intense. There was a lot of content, a lot of information being thrown at you constantly for quite a large amount of time. But what I wanna do is I wanna boil it down to the absolute basics and what you really need to pull from this course and that is this. As you continue to evolve your learning and software development skills, it's important for you to push beyond just the syntax of a particular language. It's good and very powerful to be able to look at existing code and be able to identify certain anti-patterns and problems. And being able to say, okay, maybe in this scenario I should use the strategy pattern, or maybe in this scenario I should use the command pattern. Because all of those things are very important as you begin to move up either ranks in software development organization and begin having conversations with people about software. Now the important thing here is not to be able to regurgitate the strategy pattern, the command pattern, any of these patterns at a moment's notice. But to be able to identify scenarios to say you know what, something about this doesn't feel right, I think there's a better way to do it. Because at that point you can do some research and you can come back to this course and come back to these lessons and say, you know what, that's the scenario that I'm running into right now. I wanna be able to apply the factory pattern or something like that. That is what you need to take from this course. Now obviously, as you start to learn about these patterns, they're very generic. They're very applicable to just about any object oriented programming language. And because of that, it's important to be able to have a number of resources at your disposal to understand how to identify and apply these patterns based on the languages. And because of that, if you head over to Tuts+ at any given time and you search for design patterns, there's a number of very good tutorials. And courses about all of these different types of patterns, and how they are applicable to different languages. So at any point in time, if you feel like you have identified some sort of pain point in your code, or in other code that you're inheriting. And you're really not sure what it is that you need to do to fix it, come here. Search for it, take a look at some of these related courses. And even if you don't find the course that is applicable for design patterns to your language, you should still be able to see where these types of patterns are applicable. And be able to identify those pain points and really that's all it's all about. So I hope you've enjoyed this course as much as I've enjoyed presenting it to you and as usual my name is Derick Johnson and I can't wait to see you next time.
