Efficient Rails - a new book on optimizing the development process of Rails applications

Effective Rails - It would be difficult to come up with a more accurate title for the book. All content is described in these two words and revealed to us in a hundred recipes on 380+ pages. In anticipation of the release of the final version of Rails 5, this fiction is something worth the time to spend, since it will not take so much. But this investment will return a tremendous profit of knowledge and will allow, as the cover says, "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 hard currency. Details under the cut.

I came across a sample of a chapter from a 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 a while there was a lull, periodically, just in case, I went to the website of the book, but there were no changes. And either at the end of the past, or at the beginning of this year, I received a letter joyfully announcing the completion of work and an early publication.

In the courtyard, May gradually replaced April, the book was published .

Efficient Rails is a collection of recipes for streamlining development workflows that are not explicitly described in any manuals. Let's move on to the contents:

Part 1. Toolkit - setting up the working environment
Chapter 1. Terminal(improving the standard terminal and working 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 of the rail console)
Part 2. Code - methods for optimizing the code in Rails-projects
Chapter 4. Models (highlight key points on poorly documented part of the work with models)
Chapter 5. Controllers (decision important to the author's view of the problems associated with the controllers)
Chapter 6. Presentations (section required for parsing after reading the book or doumentatsii a- I Agile Web Development)
Chapter 7. Asset(simplification of working with assets in dev-environment and non-obvious aspects 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 debugging
Chapter 9. Testing (section on setting up a test environment using live Rails projects as an example)
Chapter 10. Debugging (advanced debugging using pry and not only)

Most of what is written in the book is recognized in two ways:

• you really encountered a problem and began to search the Internet in search of a solution (in a book under 400 pages, just imagine how much time you would have to spend to find everything);
• from more experienced colleagues (sometimes you don’t even realize that the difficulty that has arisen has a solution or you don’t understand at all that this is not a feature, but the real problem).

Therefore, to summarize, at least 3 groups of developers stand out for which the book is suitable:

1. freelancers without direct access to colleagues for the exchange of experience;
2. young professionals who have mastered Rails well on test projects and get a first place job;
3. experienced professionals for whom the book will be a fresh look at the long-established own set of tools and techniques for solving problems.

And of course, the book is suitable for curious Ruby developers, regardless of experience or field of activity, allowing you to save a lot of time looking for solutions to optimize your workflow, find weaknesses and see alternatives.

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 and using the second as a reader of git-logs, I couldn’t even think how much efficient the first one hides, and that the second is actually a full-fledged “console GUI client for the git”. The ideal work with the book, as I see it (and how I use it for myself), having carefully scanned the entire book, begin the daily introduction of an unfamiliar technique. Yesterday I finally cleaned the old branches, today in practice I will compare the differences between tig and git, and tomorrow ... and tomorrow is Saturday .

Summing up the story to the end, I note that it is not affiliated with the author, I just decided to support such an excellent book so that you could usefully spend the time saved. I won’t even get any interest for selling the book from this article. Well, writing a review made it possible to get a promotional code for a discount for the Habr community, because the official price of a book with the current dollar exchange 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)

Book author Andrew Allen
Book site

Have a nice weekend!

PS I take this opportunity to say that we are inspired by good code in Mest.ru, we try to find and apply new approaches to improve it, and we invite those who are not indifferent to join our small, cozy team. Write in a personal!