total failure ! ! ! ! !

I agree completely. I don't pay a subscription on here to go and look up everything on Google. Poorly explained tutorial.

I think your criticism of the course so far is mostly valid. There isn't a lot of explanation to someone who is completely new to this subject. It also doesn't explain that there may be huge inconsistencies between the video and what you actually have to do on your personal system.

However, I have worked as a developer and part of the job is being in this situation where you are stuck and don't know the answer, and you are on your own to figure it out. The most valuable skill you will have as a Dev is to know how to search to find your answers and trying them with trial and error. It takes a certain persistence and patience that you gain with time and experience. I think a lot of PC gamers understand this, as they sometimes have to search around for solution to a bug the game has on their system. They are motivated and rewarded once they find the fix by playing their favorite game.

It might sound like the worst job ever to someone who is just starting out, but it's actually really great how capable you will become. Plus the perks of being the only person in your company that understands how things actually work are what makes it worth it.

Take a break and come back to the problem with a clear head and mindset on fixing the issues. Don't give up!

Hello,

Sorry you are having issues, but you can google the things you are not being explained in the video.

They are both frameworks/libraries. Rspec is used for testing purposes, most general purpose programming languages come with libraries for testing purposes and they are often used with test driven development. Testing is really important in a business setting, basically you write tests to confirm that your methods/classes and other objects are performing as expected. It is a common standard to write test files for applications. Here is a sample of rspec read the comments to the right for descriptions:

describe Hash do #look at the class hash
  before do #before running the test create an instance of hash and pass in the hash ":hello => 'world"
    @hash = Hash.new({:hello => 'world'})
  end

  it "should return a blank instance" do
    Hash.new.should == {} # the class hash.new should be blank
  end

  it "hash the correct information in a key" do
    @hash[:hello].should == 'world' #the instance key should equal world
  end
end

You can read about CAPYBARA here:

https://github.com/jnicklas/capybara/blob/master/README.md

It is a framework for testing also but is geared towards web apps and will use syntax similar to what is above.