Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
From PHP to Ruby on Rails

You're reading from   From PHP to Ruby on Rails Transition from PHP to Ruby by leveraging your existing backend programming knowledge

Arrow left icon
Product type Paperback
Published in Dec 2023
Publisher Packt
ISBN-13 9781804610091
Length 244 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Bernard Pineda Bernard Pineda
Author Profile Icon Bernard Pineda
Bernard Pineda
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1:From PHP to Ruby Basics
2. Chapter 1: Understanding the Ruby Mindset and Culture FREE CHAPTER 3. Chapter 2: Setting Up Our Local Environment 4. Chapter 3: Comparing Basic Ruby Syntax to PHP 5. Chapter 4: Ruby Scripting versus PHP Scripting 6. Chapter 5: Libraries and Class Syntax 7. Chapter 6: Debugging Ruby 8. Part 2:Ruby and the Web
9. Chapter 7: Understanding Convention over Configuration 10. Chapter 8: Models, DBs, and Active Record 11. Chapter 9: Bringing It All Together 12. Chapter 10: Considerations for Hosting Rails Applications versus PHP Applications 13. Index 14. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime