Book Image

From PHP to Ruby on Rails

By : Bernard Pineda
4 (1)
Book Image

From PHP to Ruby on Rails

4 (1)
By: Bernard Pineda

Overview of this book

Are you a PHP developer looking to take your first steps into the world of Ruby development? From PHP to Ruby on Rails will help you leverage your existing knowledge to gain expertise in Ruby on Rails. With a focus on bridging the gap between PHP and Ruby, this guide will help you develop the Ruby mindset, set up your local environment, grasp the syntax, master scripting, explore popular Ruby frameworks, and find out about libraries and gems. This book offers a unique take on Ruby from the perspective of a seasoned PHP developer who initially refused to learn other technologies, but never looked back after taking the leap. As such, it teaches with a language-agnostic approach that will help you feel at home in any programming language without learning everything from scratch. This approach will help you avoid common mistakes such as writing Ruby as if it were PHP and increase your understanding of the programming ecosystem as a whole. By the end of this book, you'll have gained a solid understanding of Ruby, its ecosystem, and how it compares to PHP, enabling you to build robust and scalable applications using Ruby on Rails.
Table of Contents (15 chapters)
1
Part 1:From PHP to Ruby Basics
8
Part 2:Ruby and the Web

Do not, I repeat, do not repeat yourself

If you’ve worked with frameworks in the past, you may be familiar with the Don’t Repeat Yourself (DRY) principle, even though the principle is more focused on coding and coding style. If you’re not, or just need a reminder, the DRY principle simply states that you should not repeat yourself.

You can find out more details here:

https://docs.getdbt.com/terms/dry

As much as we possibly can, we should try not to repeat our code. As an example in this application, we repeated the code on the edit and new views. Using the DRY principle, we should refactor our code so that it uses the same form for both actions. In the same manner, instead of building everything on your own and from scratch, you should reuse functions, tools, and even libraries altogether. One task that we as developers have done over and over is to authenticate users. If you have an authentication code that works, you may have even copied it from a previous...