# Next steps

## You know a lot about Ruby

Ruby is conquered. You're now a ninja.... okay, that's a bit hyperbolic but the fact is that you now know more than enough Ruby to take on Rails like a Boss. And, actually, the real secret is that the hard part is over. Getting to this point is the most difficult part of the learning curve.

Sure, you've still got plenty to learn, but the real conceptual leaps have already been made. You can think like a programmer now and should be able to figure out how to appropriately Google for pretty much anything you don't already know.

If you know Ruby, the world is sort of opened up for you. Want to learn Python? That would be a whole lot easier now. Nervous about Rails? Don't be. Rails is just Ruby that's been packaged up to do lots of stuff for you. With what you know, you'll have a much easier time "seeing the matrix" and understanding what Rails is up to. Even JavaScript should make a whole lot more sense to you once we get back to it.

## Project

Take on on [Rails](https://www.learnhowtocodebook.com/deep-dives/ruby-on-rails)!

## Additional resources

This section contains helpful links to other content. It isn't required, so consider it supplemental for if you need to dive deeper into something.

* [Ruby Best Practices book by Gregory Brown](http://it-ebooks.info/book/178/).
* [Why Ruby and Python are different](http://stackoverflow.com/questions/1113611/what-does-ruby-have-that-python-doesnt-and-vice-versa?rq=1)
* [exercism.io](http://exercism.io/), a site where you can grow and improve your ability to **write code** by **reading others' code** and **commenting** on it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://howtocode.trek.io/topics/deep-dives/ruby/next-steps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.