My Rails on Rails

Ariel D. Barclay
3 min readApr 12, 2021

My experience with Ruby on Rails.

This is my 3rd project for Flatiron School. Which was my first experience with Ruby on Rails. I was pleasantly surprised that the rails syntax was very close to written English. I really liked how quick it is to set up C.R.U.D. for a site. The one part of the project that was challenging for me was nested routes. But with the help of my cohort lead and the trusty old internet, I was able to get my Rails project done. Let me explain.

Firstly, Ruby on Rails is the Ruby coding language that uses the Rails framework. Ruby on Rails is very beginner-friendly to English speakers because its syntax is so close to English syntax.

An example Hello World program in Ruby:

puts "Hello World!"

An example program in Ruby that asks for your name and then says it:

puts "What's your name?"
name = gets.chomp
puts "Ah hello there, #{name}"

Pretty, simple right? I thought so too.

Secondly, The C.R.U.D. (Create, Read, Update, and Destroy) process for Ruby on Rails was quickly set up. Why, because the Rails framework does a lot of repetitive tasks for you. That is actually one of the reasons that it was invented. The creator (David Heinemeier Hansson) of the Rails framework noticed that he was copying and pasting from previous projects more often than not. So He created a framework to implement all of those repetitive tasks. So all of the things you would need like setting up a model and a database can be generated with simple “rails generate” command.

Here comes the but, and it’s a big but…ROUTES. What goes where and why is the toughest question to answer. Making sure that the right page is at the end of the right button is the hurdle that I had to jump over and over until I got it right. In Rails’ defense, there are plenty of helpers like resources to help you get where you are going faster. Here’s a link to help you understand rails routes https://guides.rubyonrails.org/routing.html .

Thanks for listening hopefully this helped you in some way to understand Rails a little better.

--

--