[Oxyrus]

I decided to start a tutorial series to explain the basics of Ruby on Rails by creating a web application!

This is the chapter 0, because in this, I will only explain you what you're going to need if you want to follow this series and learn how to create web applications.

What you will need

• Ruby 2.2 or above
  
• Ruby on Rails 4.2 or above
  
• A bitbucket account
  
• Text editor of your preference (Notepad++, Sublime Text, Atom, etc)
  
• Aim to learn
  

What you're going to learn

• Ruby on Rails basics
  
• CRUD
  
• Bootstrap basics
  
• CSS & HTML5
  
• jQuery basics
  
• Ruby gems
  
• Basic usage of the command line or terminal
  
• Git basics
  
• How to deploy your application to the web
  

If you're running on Windows you can use RailsInstaller to setup your development environment in matter of minutes, if you're running on Mac OS or Linux a quick search over Google


I have never coded before could I take this tutorial

I will do my best to keep everything as clear as possible, even for newbies developers, you will see that with practice in less than a month you can build your own applications on your own.

Why should I use Ruby on Rails?

Ruby on Rails has been out since 2005, and it has become one of the largest and most used web frameworks in the world. Websites such as GitHub, Twitter, Shopify and Basecamp are using it, because it's an stable well documented framework, with a really big community.

It also allows you to create prototype applications in short time, in fact you can build a very basic blog in 5 seconds, one of the original Twitter's developers said in an interview than they pick up Rails because of how much it improves the development, they had a prototype of Twitter in a single day!

I could be here explaining you all the day why you should and should not use Ruby on Rails, however it's up to you, because in the end you're the one who haves to take his time to learn

Learning to design or to code won’t happen by accident. Nobody is going to ‘give’ you time. You have to ‘take’ that time. #MakeItHappen

The chapter 1 is going to be published this weekend, so stay tuned!

This is going to be a large tutorial series, having about 20 chapters, however I want to teach you as much as possible so you can start hacking around and becoming a Ruby on Rails developer mile:

Any questions are welcome.

[Midnight]

This is a nice guide, always wanted to learn Ruby. :noh:

[Man]

A neatly written tutorial. Good job!

[Oxyrus]

I am almost done coding my personal site, I will start writing the chapter 1 tomorrow and I'll publish it on either my current blog or a new blog (to make use of my personal site code)

[Oxyrus]

At the end my decision was to post the tutorials on a new forum coded in Rails, it's going to have an awesome design and I haven't even started the Ruby part, however it won't take more than 5 days, so the tutorial will the published the new weekend. Sorry for the delay :awww:

[Andrew_mybb_import13657]

Honestly I've never tried using Ruby, and I don't know what it can do / how its any different from php besides the fact that you'll have to learn and get used to a whole different language to code in

[Lain]

Nice, I recently got a job as a Rails dev IRL; can't wait to see the next chapter.

[Oxyrus]

Honestly I've never tried using Ruby, and I don't know what it can do / how its any different from php besides the fact that you'll have to learn and get used to a whole different language to code in

Well, Ruby is a really friendly syntax language, the learning curve based on my experience for Rails is about 1 month, while for PHP it will take a lot more of time. Using Rails you can start your website way faster than with any other language/framework (excluding Django and Meteor). It also teach good practices, which come really handy when trying other frameworks also Ruby is a really well paid language with an average of $100,000 on US, while PHP is a bit lower.

I have tried many different PHP frameworks, however I found than they don't increase the development speed as much as RoR does. Anyway, it's really up to you as I mentioned, in my opinion you should give it a try to see how good or bad it is, but once again, it's up to you.

Nice, I recently got a job as a Rails dev IRL; can't wait to see the next chapter.

That's nice to hear, in where I live none company uses Ruby, all of them uses PHP or .NET for the websites :awww: