I started taking books on development seriously around June 2016. Who knew books are really helpful! Well, I knew. I was reading books for as long as I remember and am a proud member of two reading clubs and never wash dishes without listening to a speculative fiction short story. But it took me a while to start looking for and reading good books about this new profession I'm trying to acquire. And my quality of life and code changed very swiftly. Feel free to recommend anything else, I'll add it to my never-ending list.
This book delivers exactly what it promises. Well, maybe a bit more than that. I've done a rails tutorial or two in my time and that was fun but still left me almost completely in the dark. Michael Hartl is not going to leave things like this. He is extremely thorough, even going as far as creating and merging branches in every chapter, testing even smallest front-end details and being overall a lovely teacher by example. Reading this book I for a first time observed coding process of another person and it highlighted a lot of mistakes I was making. Also I finally understood what Rails actually does. Not bad for something called "tutorial".
Great book for people who want to become better developers. For experienced folk there are going to be a lot of "duh" moments. However, it felt great to experience a very non-technical approach to what development can be - a craft, a life-long learning, a purpose. I felt great sense of belonging while reading it, for once my experience was very common, people all around the world try to build their life around typing code into editor screen. Software craftsmanship may not be for everyone, but this book is as much about SC as it is about just learning how to learn, always finding a way to improve and expand. I stumbled upon it by a very lucky accident and it changed my approach to development and building a career completely.
So I decided to learn a system language, so I decided to learn Rust. I went to RustFest where I met people who've created Rust and written The Book. It is called The Book because Rust is a cult of happy developers, who are worshipping their smiling crab god and working safely with memory.
This is am big one: literally and figuratively. From the very beginning it tries to deconstruct my existing understanding of what is this thing that I am doing. It also helps to reshape my thinking into patterns better suited for that thing that I am doing. Btw, this thing is called construction and it is just a part of software development. It should be done in a correct order, with enough preparation and proper technique. This book doesn't aim to answer all of the questions about development, but it sure does let you know that those questions exist in the first place.