One-liner: Read it. 3.5 stars
I came into this with super high expectations. Things I'd heard people say: "I make everyone on my team read this." or "Every developer should start with this book". So, I thought, "sweet, a great 'back to basics' book... I can't wait!". I read through this book with a host of colleagues all with quite different experience levels and in different areas of expertise.
It was the best of times. It was the worst of times.
Well... maybe not the wo ...more
"Conquer Complexity". High quality code manages complexity. No one can think of all of the levels of abstraction needed to fully understand a program at once; just admit it and try to make your code less complex. Complexity can be managed at every level of the ...more
This second edition is from 2004, and although obviously some of its content may seem a little dated, most of it still holds up well in 2015. Given that context, I find it difficult to find fault with most of the book. Much of the advice given is good advice, and as a programmer, you should adopt and i ...more
The book is filled with nuggets of wisdom. Some of my favorite quotes, some from McConnell, some ...more
После повторного прочтения данной книги окончательно убеждаюсь в том, что данная книга должны быть прочитана, как минимум раз, каждым развивающимся разработчиком, менеджером связанным с разработкой, и тем, кто так или иначе связан с областью разработки.
Мое мнение может быть предвзятым, так как на момент написания - это единственная книга по разработке, которую я прочитал, но могу сказать, что автору удалось пролить свет на разработку как таковую, и мне, как начинающему разработчику она очень пом...more
I mean, it doesn’t even feel like a proper programming book - it’s written in some “Easy way to quit smoking for dummies” style. Every idea is explained verbosely, then illustrated with some numeric stats, then with a 3D chart, then with some real-life anecdote, then with a reference to a 1973 paper, and finally reiterated in a ...more
The second half of the book is pretty much a catalog of refactoring techniques. It's definitely geared towards the aforementioned audiences.
McConnell covers a few other topics, related to design, teamwork, testing, and configuration management, but doesn't go into dept ...more
I've been reading a few articles lately about "tricks" for re ...more
But in real case, for 10 years of professional development and self improvement, that book is just repeating of basic paradigms. But still I found something new. May be not new, but obvious, what most of senior developers ignores by "authority" of experience.
I recommend that book for Mid-Senior developers. It collects a ton of best practices and advices.
For junior devs it will be hard to handle at once. Needs to return back more that once.
At least, once y ...more
Я бы выделил эту книгу в TOP10 книг которые стоит прочитать чтобы вырасти до Lead Developer.
Further, a lot of people recommend this book to beginners which is not worthless but, I would dare to say, dangerous. Many ideas are very controversial, and to yet unformed minds they may be really wrecking.
The idea which I believe can replace the w ...more
Don't get me wrong, it's hard to find fault with the content itself - all of it is excellent advice, ...more
I bought the first edition, read about 400-500 pages and then the book was lost in a move. A few years later I got the second edition and read it again from the beginning and probably got to something like page 700. I then moved overseas and once again the book didn't make it across the ocean. Therefore, I have to include a small disclaimer that I didn't read the whole book. It is close to 1000 pages.
I don't remember any useless or impractical chapter. The book ...more
So, I finished the other book (Mythical Man Month ...more
After spending some time in the industry and facing with harsh realities of software development, I decided to give it a try again. This time I gained much more insight than my first reading. Because now I had a chance to refle ...more
The book tackle ...more
The only problem I have with the book is the formatting. It's a nightmare of little quotes, references and key point icons (with a picture of a key - thanks...) cluttering up each page ...more
Goodreads is hiring!
Learn more »