You’re on your second Rails tutorial, and you feel like flipping a table.
Writing a Rails app is supposed to be easy, right? But even if you’ve seen all the pieces, you don’t know how they fit together. Everywhere you look there’s another DSL you have to learn. When you ask for help, you’re told that you should be using minitest/spec instead. And when your tests fail, you have to figure out if it’s your fault, another library’s fault, or if the book’s out of date. Again. How are you supposed to debug your code when you don’t even know what you’re doing?
You’ve heard that Rails is delightful to use. So why are you starting to feel like you should have learned PHP instead?
But what if you could build a Rails app you could hack on today? If you had someone to guide you through the dozens of libraries you feel like you have to learn? You’d know when arguments about ‘best practices’ are worth listening to, and when you can ignore them. You could use the object-oriented skills you already have to write good tests, instead of learning a bunch of single purpose DSLs. You’d be confident that you could handle any error you run into, and you’d know how to find help when you need it. And you could regain the feeling of pure joy that comes when you really start to get a fun new language.
The Ruby ecosystem can feel overwhelming, but you don’t have to let it crush you.
Practicing Rails will help you cut through the noise and complexity and finally become the Rails developer you know you should be.
Learn more here: https://www.justinweiss.com/book