The problem with the global scope
Before we can confront the actual problem in the global scope we need to first build out the core application that is going to be used throughout this chapter. In this lecture we are going to be working in the global scope developing a sudo chat application between the user and the computer. By the end of this lesson, we will have a built application that has some issues that call for a design pattern to rescue us.
What are design patterns?
A design pattern is a solution to a common programing problem in software design.
09:00
The problem with the global scope
By the end of this lesson, we will have a built application that has some issues that call for a design pattern to rescue us.
12:16
Moving to one object and namespace
In this lesson, we will condense our code into an object and move it into a unique namespace protecting it from mistaken overrides.
08:07
The Module Design Pattern
The Module Design Pattern enables us to have a separation between our private and public API %u2013 protecting the code from external resources.
08:25
The Module Reveal Pattern
While the Module design pattern was very powerful it had a few limitations and they related mainly to the fact that we had to treat the public and private members differently. The Module Reveal Patter
06:47
Controlling the global access completely
our goal in this lesson is to remove access all together to the global scope.
05:56