Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advanced topics: What to do after the session #17

Open
otagi opened this issue May 12, 2015 · 1 comment
Open

Advanced topics: What to do after the session #17

otagi opened this issue May 12, 2015 · 1 comment

Comments

@otagi
Copy link
Contributor

otagi commented May 12, 2015

In the advanced_topics guide, we go straight to using Github, Heroku and Devise. I think these are fine for an advanced topics, part 2. But there is already so much to learn from Ruby and Rails themselves, I feel like there is a missing step here.

Maybe we should first direct the participants to resources like tryruby.org, guides.rubyonrails.org, etc.

One of the students was so eager to learn more about Ruby, she actually found tryruby.org by herself, and began to play with it at the end of the session.

@wrtsprt
Copy link
Contributor

wrtsprt commented May 15, 2015

I wouldn't mind adding something more basic to the list. My feeling is, anyone reaching that point during the event, must be quite advanced so maybe they are ready for it?

In any case: whatever we do, I would NOT mention tryruby.org anywhere. It breaks in weird ways, confuses 90% of the students IMHO and also the concepts used are far from making sense. I'd compile a list of simple commands to try in rails console, maybe even linked to the app the students just created.
Here: https://github.com/railsgirls-be/RailsGirls_BE/wiki/%5BRails-Girls-2015%5D-Replacement-for-tryruby.org I already wrote a list of things happening in tryruby. I think we should improve that a tiny bit, and that would indeed make a great advanced guide!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants