Split Project: File I/O and Serialization into two sections, then add EventManager rewrite to first section

• Split Project MD file
• Update Seed file
• Add EventManager Tutorial

This lesson should teach the student the following:

• What is RSpec?
• How to install RSpec
• Basics RSpec syntax
  • describe
  • subject and let
  • it

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Hey team,

The links in the Beginning Ruby book are linking out to an Amazon page to purchase the book whereas in previous sections, it was linking to the ebook preview itself.

Happy to fix the links myself but was wondering if there were legal issues or other reasons why we're linking out to Amazon instead of a free albeit pirated version of the book.

This lesson should teach the student the following:

• What is a mock(double) and how can you use it?
• Before blocks in RSpec
• What are stubs and how are they used?
• What are spies and how are they used?
• Scope in RSpec, over-riding lets and subjects etc.

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

I've noticed a few grammar mistakes in the Event Manager project including comma splices, sentence fragments, and singular articles referring to plural nouns. Some of the comma splices are desirable within the colloquial style, and should be kept. For example:

By making a copy and then changing the copy, we’re sure everyone’s name is unique.

Others look wrong and should be changed to a dash or split into two sentences:

ERB defines several different escape sequence tags that we can use, the most common are:

I'm finding the lesson very helpful! I would love to improve it by making these minor style edits if that's alright! :)

This lesson should teach the student the following:

• Inheritance and how it works
• The problem it solves

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Are there any small things you think we can do to improve the course right away?
This is the place to list and discuss them.

I'll keep this as an open ongoing issue so we can see the lesson completions for each lesson in the Ruby Course over time. This will give us data to use when making decisions about the course.

We should probably automate this in some way so it posts a comment on this issue each week with the percentage increase or decrease from the week before.

We are seeking people to take charge of coordinating the creation of these lessons. If you would like to fill take this role, please let us know by commenting on this issue with your desire take ownership of these lessons.

For each lesson, reply to this issue with:

1. An Introduction for the lesson
   A brief summary about what the lesson is about and why the topics or concepts it teaches are important.

2. Learning Outcomes
   A list of bullet points of what the student is expected to know or be able to do by the end of this lesson

3. Content for the lesson
   Explanations of the main concepts in the lesson, include code snippets and easy to understand metaphors where applicable.

4. Assignment
   Either a list of links to resources the user will go through to learn about the topic of this lesson more in depth. Have no more than 5 resources, ideally no more than three. Or an exercise the student should do to solidify their understanding of the lesson content.

5. Additional Resources
   A list of links to other resources which are valuable and or complement the assignment resources. Link to no more than three additional resources to avoid this section becoming too cluttered.

List of lessons:

• Blocks Procs and lambdas- What these are and how to use them.
• Advanced Enumerable’s- How to use enumerable in your own classes.
• Meta Programming basics - What is metaprogramming and what are some of the basic things you can do with it?

This lesson should teach the student the following:

• Describe for methods
  • use pound sign notation for instance methods describe "#my_method" do
  • use dot notation for class methods describe ".my_method" do
• Use context blocks for different branches

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

When switching over to using the CSV library in the Event Manager project, I get the following error when running the file:

EventManger Initialized!
Traceback (most recent call last):
	3: from lib/event_manager.rb:4:in `<main>'
	2: from /Users/scott/.rbenv/versions/2.5.0/lib/ruby/2.5.0/csv.rb:1272:in `open'
	1: from /Users/scott/.rbenv/versions/2.5.0/lib/ruby/2.5.0/csv.rb:1272:in `open'
/Users/scott/.rbenv/versions/2.5.0/lib/ruby/2.5.0/csv.rb:1272:in `initialize': No such file or directory @ rb_sysopen - event_attendess.csv (Errno::ENOENT)

Here's my event_manager.rb file:

require 'csv'
puts 'EventManger Initialized!'

contents = CSV.open 'event_attendess.csv', headers: true, header_converters: :symbol
contents.each do |row|
  name = row[:first_name]
  puts name
end

Interestingly, I'm able to access the CSV file and work with it in Pry without problems.

This has been coming up quite a lot in chat ☝️ October 26, 2017 8:40 PM

We had to remove the rspec course by codeschool from the testing lesson on web dev 101 https://www.theodinproject.com/courses/web-development-101/lessons/testing-basics

Without that course the lesson is basically useless, its too early in the curriculum to be going over testing anyway.

The solution to this problem is to remove this testing lesson from the curriculum. I believe that removing this lesson will have a positive effect on the curriculum as a whole.

Tasks include

• Remove the lesson from the seeds file in the main site
• Remove any mentions of this lesson in other parts of the course. I think its mentioned in the ruby course and the rails course.

We are seeking people to take charge of coordinating the creation of these lessons. If you would like to fill take this role, please let us know by commenting on this issue with your desire take ownership of these lessons.

For each lesson, reply to this issue with:

1. An Introduction for the lesson
   A brief summary about what the lesson is about and why the topics or concepts it teaches are important.

2. Learning Outcomes
   A list of bullet points of what the student is expected to know or be able to do by the end of this lesson

3. Content for the lesson
   Explanations of the main concepts in the lesson, include code snippets and easy to understand metaphors where applicable.

4. Assignment
   Either a list of links to resources the user will go through to learn about the topic of this lesson more in depth. Have no more than 5 resources, ideally no more than three. Or an exercise the student should do to solidify their understanding of the lesson content.

5. Additional Resources
   A list of links to other resources which are valuable and or complement the assignment resources. Link to no more than three additional resources to avoid this section becoming too cluttered.

List of lessons:

• Why Object Oriented Programming - What OOP is and what problems it solves
• Classes and Instances - Whats a class and instance and whats the difference between them
• Methods in OOP - Instance methods, class methods and getter and setter methods
• Inheritance - What is inheritance, what does it do.
• Method scope- Public, protected and private methods
• Modules - Whats a module, whats the difference between them and classes and what to use them for
• Working with Collaborator Objects - How to get your objects to work together
• Intermediate Enumerables - Intermediate enumerables, inject, max, sort etc

Please someone important review this section, it surely needs some work. For example, at many places the code seemed complete but gave an error when i ran it, because it was incomplete. If its not complete on purpose then atleast state that, and at some places the code is formated as simple text.

This lesson should teach the student the following:

• Public Methods
• Private and protected methods
• Why scope methods in your objects?

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

@KevinMulhern mentioned in another issue that the final project could potentially be replaced to something less daunting.

I'm personally in two minds. One the one hand you need to challenge yourself and many students probably move on because they feel they have a good grasp of Ruby and are itching to get started with Rails.

I also am hopeful that with a new improved Ruby course most students will be better equipped to tackle it.

That said. I'm not a huge fan of the chess project because there are some aspects of it that are just a royal pain. Namely formatting to a terminal which isn't really the kind of skills most people need.

Let's throw out some project ideas no matter how crazy they sound and see what we come up with. Any that seem plausible we can discuss further.

Project ideas

1. Make a ruby gem
2. Implement a ruby DSL
3. Command line battleships
4. Web scraper
5. Leave the project idea up to the student (but leave some ideas for projects) so we get an eclectic mix of projects to inspire people in the future.

This lesson should teach the student the following:

• Instances methods
• Getters and setters
• Class methods
• The differences between the two

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

This lesson should teach the student the following:

• Test Public methods
• Test commands and quiries
  • Test what a method retuns
  • If a method is a command method test it sends the right command
• Don't test private methods and why

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Hi
The link "submit them to the project on Github" near the start of the lesson here is broken.

This lesson should teach the student the following:

• Inject
• each_with_object
• group_by
• max_by
• min_by

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Alright lads @TheOdinProject/ruby-team lets get this kicked off.

First thing we need to do is move everything ruby related over from the curriculum repo and change the seeds files on the main site to point the lessons towards their new home in this repo.

What are the long term projects and improvements you think we should work on for this course? what new sections, lessons, projects do you think we should create?

We are seeking people to take charge of coordinating the creation of these lessons. If you would like to fill take this role, please let us know by commenting on this issue with your desire take ownership of these lessons.

For each lesson, reply to this issue with:

1. An Introduction for the lesson
   A brief summary about what the lesson is about and why the topics or concepts it teaches are important.

2. Learning Outcomes
   A list of bullet points of what the student is expected to know or be able to do by the end of this lesson

3. Content for the lesson
   Explanations of the main concepts in the lesson, include code snippets and easy to understand metaphors where applicable.

4. Assignment
   Either a list of links to resources the user will go through to learn about the topic of this lesson more in depth. Have no more than 5 resources, ideally no more than three. Or an exercise the student should do to solidify their understanding of the lesson content.

5. Additional Resources
   A list of links to other resources which are valuable and or complement the assignment resources. Link to no more than three additional resources to avoid this section becoming too cluttered.

List of lessons:

• File Basics - The basics of using files in Ruby, open, reading, writing and closing.
• Loading files - Require, load, require_relative etc
• Standard Ruby project set up - How to set up your ruby objects, lib and spec folder etc
• Serialization - Yaml and JSON.

Regarding the project of this lesson. If you use download the event_attendees.csv file using the link from the lesson, you don't get the actual csv but the html file. To get the actual csv you have to use the raw link:

https://raw.githubusercontent.com/TheOdinProject/ruby_course/master/ruby_programming/intermediate_ruby/event_attendees.csv

@mindovermiles262 pointed out that the URL is correct in the project's readme but If you take a look at the lesson.md for this project: https://github.com/TheOdinProject/ruby_course/blob/master/ruby_programming/intermediate_ruby/project_event_manager.md

You will see that the link doesn't point to the raw CSV file but the regular CSV file.

This should be an easy fix.

PS: On this line in the lesson:

response = civic_info.representative_info_by_address(address: 80202, levels: 'country', roles: ['legislatorUpperBody', legislatorLowerBody'])

there is a missing ' for legislatorLowerBody

first sentence Web Dev 101 course goes to 404 page instead of here

Leo made a great point about drafting out a broad syllabus for this course in another issue #2

I think it's a great idea and will hopefully generate a lot of new ideas as well as get us all on the same page as to what we want this course to be and contain.

I'm not sure what format we should go with here so write out your ideas in whatever way you think is best.

I think it would also be good to mention that I think we should take an MVP philosophy with working on and rolling out the new course. We should aim to make the smallest changes that add value and then roll it out to get feedback and to allow users to get value from what we are working on as quickly as possible. We can then iterate from that to polish and 'complete' things.

We are seeking people to take charge of coordinating the creation of these lessons. If you would like to fill take this role, please let us know by commenting on this issue with your desire take ownership of these lessons.

For each lesson, reply to this issue with:

1. An Introduction for the lesson
   A brief summary about what the lesson is about and why the topics or concepts it teaches are important.

2. Learning Outcomes
   A list of bullet points of what the student is expected to know or be able to do by the end of this lesson

3. Content for the lesson
   Explanations of the main concepts in the lesson, include code snippets and easy to understand metaphors where applicable.

4. Assignment
   Either a list of links to resources the user will go through to learn about the topic of this lesson more in depth. Have no more than 5 resources, ideally no more than three. Or an exercise the student should do to solidify their understanding of the lesson content.

5. Additional Resources
   A list of links to other resources which are valuable and or complement the assignment resources. Link to no more than three additional resources to avoid this section becoming too cluttered.

List of lessons:

• Why TDD? -The philosophy behind TDD and its process, red, green refactor.
• Introduction to RSpec - Install Rspec and its basic syntax
• Matchers - The basic Matchers you will use in RSpec and when to use them
• Mocks, stubs and spies - What each of these are and when and how to use them
• What to test - The rules of what to test in unit tests and how to structure them

@KevinMulhern is responsible for coordinating the creation of these lessons, but he needs your help.

For each lesson, reply to this issue with:

1. An Introduction for the lesson
   A brief summary about what the lesson is about and why the topics or concepts it teaches are important.

2. Learning Outcomes
   A list of bullet points of what the student is expected to know or be able to do by the end of this lesson

3. Content for the lesson
   Explanations of the main concepts in the lesson, include code snippets and easy to understand metaphors where applicable.

4. Assignment
   Either a list of links to resources the user will go through to learn about the topic of this lesson more in depth. Have no more than 5 resources, ideally no more than three. Or an exercise the student should do to solidify their understanding of the lesson content.

5. Additional Resources
   A list of links to other resources which are valuable and or complement the assignment resources. Link to no more than three additional resources to avoid this section becoming too cluttered.

List of lessons:

• Ruby's Primitive Data Types - Strings, numbers and symbols
• Variables - What are variables and how to use them. Explain pass by reference.
• Input and Output - Puts, print and getting input from a user
• Conditional Logic - If and case statements. Boolean logic
• Loops - All the different loops in Ruby (Except enumerables)
• Arrays - All about arrays
• Hashes - All about hashes
• Basic Enumerables - What enumerables are, teach each, map, select
• Methods - How to write your own methods
• Problem Solving - Approaches to problem solving
• Debugging - Some techniques for debugging, using puts, reading the stack trace etc.

Now that we have moved all the files over I think It would be a good idea to decide upon the first long term project we will work on.

While we are trying to get the course to match the syllabus we drafted up, a long term project can be one of the sections of the new syllabus.

We will of course create issues and work on other smaller things as they come up while we work on a longer term project.

This lesson should teach the student the following:

• Whats a collaborator object?
• Passing in a collaborator when initializing the object
• Creating a new collaborator object within the class
• Sub classing

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Going through the Basic Ruby section, I've noticed that the link to the resource for Beginning Ruby by Peter Cooper is not a complete copy of the book and has some pages removed. Some of these removed pages are included in what we are told to read.

I did some searching and found this PDF which I believe should be used instead, as it has the full book uploaded. It is also the same edition as the one already used in this lesson.

We are seeking people to take charge of coordinating the creation of these lessons. If you would like to fill take this role, please let us know by commenting on this issue with your desire take ownership of these lessons.

For each lesson, reply to this issue with:

1. An Introduction for the lesson
   A brief summary about what the lesson is about and why the topics or concepts it teaches are important.

2. Learning Outcomes
   A list of bullet points of what the student is expected to know or be able to do by the end of this lesson

3. Content for the lesson
   Explanations of the main concepts in the lesson, include code snippets and easy to understand metaphors where applicable.

4. Assignment
   Either a list of links to resources the user will go through to learn about the topic of this lesson more in depth. Have no more than 5 resources, ideally no more than three. Or an exercise the student should do to solidify their understanding of the lesson content.

5. Additional Resources
   A list of links to other resources which are valuable and or complement the assignment resources. Link to no more than three additional resources to avoid this section becoming too cluttered.

List of lessons:

• The Ruby Object Model - How classes are structured under the hood and how ruby finds which method to use.
• Solid Design Principles - Explain all the principles of SOLID and how they make your code better.
• Basics of Refactoring and code smells - Basic code smells and solutions for refactoring them
• Composition over Inheritance - Why you should use composition over inheritance.
• Basic Design Patterns - Some of the common design patterns the student will come across in code bases.

This lesson should teach the student the following:

• What is TDD
• What problems does it solve?
• Red, green, refactor cycle

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Inspired by @CouchofTomato's final project post I think having somewhere to store project ideas would be a good idea.

Any projects or exercise ideas you have put them here please.

Creating lessons by seeding is inefficient and can be troublesome with the disjoint between the seed and the lesson.

One workaround for this would be to include metadata for each lesson in the header. There are Kramdown parsers (Kramdown-metadata-parser) that are able to read this information and return a hash.

We can then use this data to dynamically seed the ruby lessons.

I'd like to test-run this type of seeding with the ruby content before rolling it out site-wide

This lesson should teach the student the following:

• Whats a class
• Whats an instance of a class
• What are the differences between the two
• Instance variables and initialize method
• class variables

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

This lesson should teach the student the following:

• What is OOP and why it came about
• History of OOP
• The problem it solves

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

This lesson should teach the student the following:

• whats a module?
• what is the difference between a module and class
• what to use a module for?
  • Sharing methods
  • Namespacing

Please use this stub file for the lesson

Working on this task

• If you want to work on this task, please claim it by commenting below
• Branch off the redesign branch
• Check out our styleguide
• When you are submitting your pull request for this task please ensure the base branch you want to merge into is the redesign branch

Note

• Please use the contributing guide to get the app running on your local machine if you haven't already.

If you have any questions or need clarification about anything related to this task please contact the maintainers in our contributing channel on Gitter

Second assignment here goes to an Amazon page to buy the book, I don't think that was intended :)

https://www.theodinproject.com/courses/ruby-programming/lessons/common-data-structures-and-algorithms?ref=lnav
3rd point, assignment section, the video doesn't load.