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

Added 1.An Introduction for the lesson #134

wants to merge 1 commit into from

Conversation

miarhost
Copy link
Contributor

No description provided.

@leosoaivan
Copy link
Contributor

Good introduction to OOP 👍.

CouchofTomato
CouchofTomato suggested changes Jan 31, 2018
View reviewed changes
ruby_programming/in_progress/oop_basics/oop_introduction_lesson.md
@@ -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.

ruby_programming/in_progress/oop_basics/oop_introduction_lesson.md
@@ -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.
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

ruby_programming/in_progress/oop_basics/oop_introduction_lesson.md
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.
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.
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.

@CouchofTomato
Copy link
Member

Hi @mariatikhonova

Thanks for taking the time to put together something here. I've left some suggestions of where I think we can simplify and better explain some concepts. If you need any help give me a shout.

@miarhost
Copy link
Contributor Author

miarhost commented Jan 31, 2018 via email

@miarhost
Copy link
Contributor Author

miarhost commented Jan 31, 2018 via email

@KevinMulhern
Copy link
Member

Hey @miarhost, sorry its taken me so long to get back to this. I'll go through this one with you next week if thats ok? my focus is on merging the rails course back into the curriculum repo this week 😄

@miarhost
Copy link
Contributor Author

miarhost commented Apr 18, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@CouchofTomato CouchofTomato CouchofTomato requested changes

@KevinMulhern KevinMulhern Awaiting requested review from KevinMulhern

@leosoaivan leosoaivan Awaiting requested review from leosoaivan

@mindovermiles262 mindovermiles262 Awaiting requested review from mindovermiles262

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@miarhost @leosoaivan @CouchofTomato @KevinMulhern