> On Dec 25, 2015, at 3:11 PM, bryanguillen12 <[email protected]> wrote:
> 
> Hey ROR Community, 
> I am brand new to this fun world world of programming and obviously, ruby on 
> rails too.  I have been picking up some basic skills in programming, enough 
> to write a !SIMPLE! program, and also some front end web development. With 
> that said, I am hitting walls all over the place; I know the talent and skill 
> in this community can help me and maybe, through this thread, others that are 
> also brand new and don't know where to begin, which is where we all begin.   
> 
> With that said, I am following a program for learning the fundamentals of 
> ruby on rails development.  The program claims to give you the tool set to 
> throw up a web app prototype, which is my end game.  The program teaches 
> "ruby basics", "Javascript basics", "console foundations", "git basics", 
> "Installing a Ruby development Environment", "Build a Todo List with Rails 
> 4", "Database Foundations", "Active Record Basics", and finally "User 
> Authentication with Rails". Will learning these specific topics, in that 
> exact order, help?  After these courses, will I know enough to do a very 
> simple software prototype?  Should I, or others in my position, go through 
> all those steps or skip a few which aren't a priority for a prototype?  I 
> appreciate the time and effort into any credible answer.  

There are a lot of different beginner intros to Rails. The one that is widely 
touted here as being the best is http://railstutorial.org. It's available for 
pay or for free to use on line. The book is great, the exercise applications 
are designed to work you through the basics of Rails, and give you a strong 
foundation with Test-Driven Development. One of the things I like about this is 
that it does not assume you understand very much, but never talks down to you 
(I did this after over 15 years of development, kept an open mind, and learned 
some things I thought I understood). 

It sounds from the topics as if the course you are interested in is giving you 
a similar round-the-framework cruise of Rails. If you like it, go for it. You 
probably don't have anything to lose except a week of free time, and much to 
gain.

If you get stuck, do write back. Just remember to follow these steps to get a 
better answer:

1. Briefly describe what you're doing, show what you've done to debug and what 
you've searched for. Showing effort before asking the list is the first and 
most important thing.
2. Copy and paste your errors. No screenshots, and no vague descriptions like 
"I got an error". When you are developing in Rails and running your 
application, you have a terminal window open, and that terminal is tailing the 
log after you type rails s and return. Watch that window (and scroll back) for 
valuable info about what is happening.
3. Try to only ask one question at a time. The more focused your question, the 
better the answers you will get. The people on this list are busy with their 
own work, and still make time to help you with yours.

Cheers!

Walter

> 
> Thank You ROR Community, 
> Bryan G.       
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-talk/facd853c-c9e0-4956-89fa-d5b3c59502e3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/B8DC075D-7C21-4D3E-9395-FFA2D1ACDB37%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to