Skip to content
This repository has been archived by the owner on Oct 1, 2018. It is now read-only.

Added 1.An Introduction for the lesson #134

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
### Introduction
A brief summary about what this lesson is about and why the topics or concepts it covers are important.
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to simplify this to better explain some OOP concepts. A person with no programming experience won't know what classes or objects are.

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A beginner might not be able to relate to the idea of OOP being modelled on real objects without a small example

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can possibly introduce the DRY acronym here.


### Learning Outcomes
*Look through these now and then use them to test yourself after doing the assignment*
Expand Down