Ruby on Rails Tutorial

this is an classic for rails. countless entrepreneur/developers i know have used this as their first 0 to production guide for their first real (shipped, launched, live etc) software projects.

I say it's an excellent intro to someone with maybe some academic programming experience to get into web app development. it gives you the kick starter development plan you need to make a Twitter, db, grub hub, air bnb type startup alone or with a small team.

and... he keeps it up to date! with impeccable detail!

Re: Ruby on Rails Tutorial

#5

Post by sjnair96 » Sat, Jul 30, 2016, 5:32 PM UTC

sotojuan wrote: post #3

I'll always be upset that my college web development class got changed from following this tutorial to early 2000s PHP without a database.

Whoa. How did that come about?

Re: Ruby on Rails Tutorial

#6

Post by forgingahead » Sat, Jul 30, 2016, 5:36 PM UTC

Highly recommended, this tutorial got many people (myself included) started on Rails. The parent link is to the free-online version, but I do suggest folks who have benefitted from this give back to Michael by spending on the paid version:

https://www.railstutorial.org/#pricing

No affiliation at all, just want to encourage support to a resource that has been a net-positive to our ecosystem.

Re: Ruby on Rails Tutorial

#7

Post by danso » Sat, Jul 30, 2016, 5:50 PM UTC

sotojuan wrote: post #3

I'll always be upset that my college web development class got changed from following this tutorial to early 2000s PHP without a database.

The other day on my way to the airport, I had an Uber driver in Portland who was telling me that he was just about to start a lengthy coding bootcamp in JavaScript and PHP. Not Node, just front-end JS. And Rails was one of the options, but he opted to do PHP with a focus on Drupal.

Kind of blew me away. I know Rails seems to have waned relative to when coding bootcamps first became big, but I had thought PHP was well past its attractiveness for new developers, despite the number of PHP systems that need maintaining in the real world.

Re: Ruby on Rails Tutorial

#8

Post by Whitecollar » Sat, Jul 30, 2016, 6:04 PM UTC

Beginner question, having heard rails is not a hot thing anymore and SPAs being the new hot stuff, where do you guys draw the line between a SPA and a server rendered web app? I can see the extreme side cases, the highly interactive web app vs content-heavy-but-not-that interactive web app.

But for example, github doesn't have complex interactions and is not content heavy (in the walls of text sense) but its doing just fine as a non-SPA and users seem to like it the way it is.

Would a site like github benefit much from being a SPA instead of being server side rendered with some JS on the top?

Re: Ruby on Rails Tutorial

#9

Post by sotojuan » Sat, Jul 30, 2016, 6:08 PM UTC

danso wrote: post #7

sotojuan wrote: post #3

I'll always be upset that my college web development class got changed from following this tutorial to early 2000s PHP without a database.

The other day on my way to the airport, I had an Uber driver in Portland who was telling me that he was just about to start a lengthy coding bootcamp in JavaScript and PHP. Not Node, just front-end JS. And Rails was one of the options, but he opted to do PHP with a focus on Drupal. Kind of blew me away. I know Rails seems to have waned relative to when coding bootcamps first became big, but I had thought PHP was well…

While I would've also chosen Rails, the truth is that there's plenty more PHP jobs out there, even in cities like Portland so he'll be fine either way.

Re: Ruby on Rails Tutorial

#10

Post by sotojuan » Sat, Jul 30, 2016, 6:09 PM UTC

sjnair96 wrote: post #5

sotojuan wrote: post #3

I'll always be upset that my college web development class got changed from following this tutorial to early 2000s PHP without a database.

Whoa. How did that come about?

Professor thought it'd be better to "learn the basics" first, whatever that means. Just another example of academia being out of touch.

At least it was an easy A.