Kiera Thomasson - Octos - Solar System

[Krashaune]

Solar System

Congratulations! You're submitting your assignment.

Comprehension Questions

Question	Answer
What was the purpose of the initialize method in your class?	The initialize method is to define what instance variables are needed to create an object in the class.
Describe an instance variable you used and what you used it for.	I used 5 instance variables in the class Planet which were name, position, color, attribute a, and attribute b. I used them to define what is needed to create a new planet.
Describe what the difference would be if your SolarSystem used an Array vs a Hash.	If Solarsystem used an array you could access the information and iterate over it using the index whereas with a hash in order to access the information (values) you would need to use the keys.
Do you feel like you used consistent formatting throughout your code?	Yes, I believe I did.

[droberts-sea]

Solar System

What We're Looking For

Feature	Feedback
Baseline
Readable code with consistent indentation.	yes
Primary Requirements
Created Custom Solar System Class with initialize, add planet & list planets methods, without using puts.	yes
Planet Class Created	yes
Created a collection of Planet objects as an instance variable in SolarSystem.	yes
Accessor methods created	yes
Method created to return the Planet's attributes and not use puts	yes
Created a user interface to interact with the SolarSystem including adding a planet and viewing a planet's details	some - adding a planet doesn't work, you get a new planet but every attribute is hard-coded
Additional Notes	This is a good start, but it feels like there's a way to go still to get comfortable with classes and methods. I've left some specific inline comments below - please read through them, and try and practice those ideas this week on WordGuess and GroceryStore. I really appreciate all the hard work you were doing this weekend. Keep that focus and things will start to fall into place!

[droberts-sea]

Files in Ruby should be named using snake_case. So this one would be solar_system.rb (little 's').

The decision is a little arbitrary, but especially once we start working on group projects it will be important to make sure everyone is doing the same thing.

[droberts-sea]

Line 32 gave me an error. Looks like the planet_user method is probably what you want.

[droberts-sea]

I don't know if this method makes sense in the context of SolarSystem. It relies on instance variables like @name and @position, which are defined in Planet but not here.

[droberts-sea]

You're shoveling these variables into an array - I'm not sure that's what you want. Instead, you should use them as the arguments to call Planet.new, and add that to your solar system:

puts "Choose a planet name"
new_planet_name = gets.chomp
puts "Choose a planet position..."
new_planet_position = gets.chomp
# ... rest of the attributes

new_planet = Planet.new(new_planet_name, new_planet_position, ...)
my_solar_system.add_planet(new_planet)

[droberts-sea]

This method should take one argument, an instance of Planet, and add it to the list. As is I think it will throw an error.

[droberts-sea]

In stead of referencing the planet_list directly here, you should go through your instance of SolarSystem: my_solar_system.add_planet. This may seem rounabout, but by making the solar system is the owner of the list of planets and requiring that all access goes through it, we can make our programs easier to reason about and debug.

[droberts-sea]

I like that you took our placeholder attributes and ran with them!