Effective Rails - a more accurate title for a book would be hard to come up with. The entire content is described by these two words and revealed to us in a hundred recipes on 380+ pages. Waiting for the release of the final version of Rails 5, this reading is something that is worth the time, the benefit will not need it so much. But this investment will return a huge profit of knowledge and will allow, as stated on the cover,
"to create Rails-applications with inhuman speed .
" And not only Rails, and not only Ruby. The first two chapters include an abundance of information on working with the terminal and SLE. Details under the cut.
I stumbled upon the sample of the chapter from the book that was still being prepared last summer, became interested and subscribed to the newsletter so as not to lose sight of this work. For some time there was a lull, I occasionally went to the book site, just in case, but there were no changes. And now either at the end of the past, or at the beginning of this year, I received a letter, happily informing about the completion of work and a quick publication.
In the courtyard May gradually followed April, the
book was published .
')
Efficient Rails is a
collection of recipes for optimizing development workflow , which are not explicitly described in any manuals. We turn to the content:
Part 1. Tools - setting up the working environmentChapter 1. Terminal (improvement of the standard terminal and work with it)
Chapter 2. Git (approaches to working with git and solving non-standard situations encountered in the daily routine)
Chapter 3. Rails Console (Hidden Potential Rail Console)
Part 2. Code - methods for optimizing code in Rails projectsChapter 4. Models (accents are placed on poorly documented parts of working with models)
Chapter 5. Controllers (solving important in the opinion of the author problems related to controllers)
Chapter 6. Representations (the section is obligatory for analysis after reading the documentation or the book a la Agile Web Development)
Chapter 7. Assets (simplifying work with assets in dev-environments and unobvious moments of Turbolinks)
Chapter 8. Working with mail (cool tricks for setting up and testing mail sending)
Part 3. Techniques and techniques - approaches to testing and debuggingChapter 9. Testing (section on setting up a test environment on the example of live Rails projects)
Chapter 10. Debugging (advanced debugging with pry and not only)
Most of what is written in the book is recognized in two ways:
- you really ran into a problem and began to search through the Internet in search of a solution (in a book under 400 pages, just imagine how much time you have to spend to find everything);
- from more experienced colleagues (sometimes you do not even realize that the difficulty that has arisen has a solution or you do not understand at all that this is not a feature, but a real problem).
Therefore, summing up, at least 3 groups of developers are allocated for which the book is suitable:
- freelancers without direct access to colleagues for the exchange of experience;
- young professionals who have mastered Rails well on test projects and are working in their first job;
- experienced professionals, for whom the book will become a fresh look at its own set of tools and techniques for solving problems that have long been formed.
And of course, the book will suit curious Ruby developers, regardless of experience or field of activity, allowing you to save a lot of time searching for solutions to optimize the workflow, find weaknesses and see alternatives.
Personally, for myself, I discovered a lot of new useful things and learned about other possibilities in familiar tools that I use every day. For example, zsh and tig are my old friends. Having learned the basics of the first one and using the second one as a git-log reader, I could not have thought how much the first one hides, and that the second is in fact a full-fledged
“console GUI client for the gita” . The ideal work with the book, as I see it (and how I use it for myself) - having carefully run through the whole book, proceed to the daily introduction of one unfamiliar technique. Yesterday I finally cleaned the old branches, today in practice I will compare the differences between the work of tig and git, and tomorrow ...
and tomorrow is Saturday .
Summing up the story, I’ll note that I’m
not affiliated with the author in any way , I just decided to support such a great book so that you can spend the time saved. I will not even get any interest on the book sales from this article. Well, writing a review allowed me to get a promotional code for a discount for the Habra community, because the official price of a book with the current dollar rate bites even for Rails developers. By the way, I am very grateful to Andrew for such a generous discount. Even if you are not going to buy a book,
be sure to read the free chapter , it is very useful.
Buy a book for $ 20 (50% discount)Author
Andrew AllenBook siteGreat weekend to everyone!
PS Taking this opportunity, I want to say that we at Mesto.ru are inspired by good code, try to find and apply new approaches to its improvement, and invite those who are not indifferent to join our small, cozy team. Write in a personal!