Addison Wesley Code That Fits in Your Head: Heuristics for Software Engineering

Un libro molto utile che attraverso concetti di psicologia introduce un nuovo modo di affrontare il codice. Basandoci sul concetto che “passiamo più il tempo a leggere il codice che a scriverlo”, affronta metodi su come scrivere codice per essere letto facilmente da uno sviluppatore.

Learned a ton from this book. I look at legacy code with a new set of tricks now. The author did a great job explaining how to break down complex classes and methods.

Wie war das? >>Jeder Trottel kann Code schreiben, den Maschienen verstehen - die Challange ist es Code zu schreiben, den jeder versteht<< (nicht direkt aus dem Buch). Hat auf jeden Fall gute Ansätze, um die eigenen Gedanken so zu ordnen, damit andere (oder man selbst Monate später) besser und sicherer damit umgehen können. Natürlich darf TDD etc. nicht fehlen - wenn auch berechtigter weise.

This book is amazing. The author provides deep insights without being too academic. Off scale is the practical orientation, the tips and references provided and the appendix gathering all the concepts in a quick overview.

Over the years, I've come to expect great things from books in this series. I don't think this was an exception, but I will say that it was the weakest of the books in this series that I've read (which is nearly all of them). This book fell a bit short of my expectations, but they were likely unrealistically high. It was definitely worth the purchase, and I'd definitely recommend it to others. If there's any one thing I'd love to see improved upon in future editions would be that I think it could use a bit of work at the organizational level. The organization, as it currently stands, is basically, "Let's build a project, and I'll introduce you to various good ideas as they are relevant as we're building this." The various principles that came up rang true to me, but going through the book, it just didn't feel like there was a lot of cohesiveness to the ideas that were brought up. I was left wondering if the particular project had been a different one, if we'd have bumped into a totally different set of good ideas to discuss instead. It was hard to spot the thesis of the book. From the title, I had assumed it was focused on the task of ensuring code is written and structured in a way that makes it easy to figure out and remember for the duration of the time you're working on it. The concept of "code that fits in your head" was one of the many ideas that popped up in the book and was referred back to several times, but it didn't come across as the central tenet of the book, from which every other principle derived from, as I had assumed. Perhaps you'll appreciate the book a bit more if you go into it knowing that it isn't *specifically* or *only* about writing code that fits into your head, but, rather, a grab bag of good ideas that help you write better code. It was a good book, worth the money and time I spent on it, just a bit different than I had expected it to be.