So far you wrote programs executed line by line, in methods, as you learned them. It's called procedural programming. Now you think it's easier to understand how to make a program like that, not thinking about how your methods will be organized further, but later you will build real programs and applications. If your code will be organized that way, a single mistake, a typo, can make your build fall apart. Object-oriented approach propose you to organize your code into structures named for chosen object called CLASSES. Since the time you will know object-oriented model, you will find it easier to say that class "YourClass" implements these and that actions in methods , than to explain how that actions are run by raw methods. You will see that classes' structure and behaviour is alike to how real objects' behavior is described, inherited and working in real life. As we said, as you will have code organized in classes, classes' methods and instances, you will be able to fix and change your code easily up to your needs in future. In classes your code is serving and reused without repetitions.
Look through these now and then use them to test yourself after doing the assignment
what the student is expected to know or be able to do by the end of this lesson
- Learning outcome 1
- Learning outcome 2
- Learning outcome 3
- Start by outlining the different sections you think this lesson should include
- Include plenty of code snippets where applicable
- Use h3's for headings eg
### Title - Use h4's for subheadings eg
#### Subtitle
The list of resources the user will go through to learn about the topic of this lesson. Have no more than 5 resources, ideally no more than three.
This section contains helpful links to other content. It isn't required, so consider it supplemental for if you need to dive deeper into something
Link to no more than three additional resources to avoid this section becoming too cluttered.