This is my first ever review. Oddly none of the other technical books (over 300) that I read ever compelled me write before.
As Dan Chak recommends, if you are new to rails, first read Agile Development for Rails, then start with Enterprise Rails. Every rails developer needs to read this book.
You are creating an application that you *hope* will actually grow in demand. Isn't that what we are all looking to do in the end - make a hot app? Why not be pragmatic by laying the foundation of robustness, scalability with that in mind in the first place?
I loved the sections on network design, database design (of course, ex-DBA), and services (I know so little about SOA).
Having read 9 other rails books, I was nervous that rails community ignored that some areas completely. Despite its principles, it was intend on re-inventing the wheel. It made me feel like Dorothy in the Oz with munchkins shouting how great Rails is no matter the issue. That made me wonder if rails community was really open and flexible as claimed.
The other books were good, but you need more than books touting rails' magic and coolness - sweet/success/awesome. Enterprise Rails is excellent in terms of readability, examples, and pragmatic practical advice. Yes - it is sweet and awesome too! There now I can be a cheerleader too.
Reading reviews and Chak's articles, I was worried that the book would be full of theory and dry. Instead it covers just the right about of theory supported with insightful examples and exercises to confirm that you really understood the problem and solution.
Thank you Dan for helping me understand rails better and getting rid of that awful in queasy feeling each time I was writing a rail app.
less
0 comments
Post a comment