Why this book?

Lance (the author) is an very experienced software engineer in the field of enterprise's software. Very interesting experience explained and good vulgarization without computer slang.

He states "things are really bad in enterprise software" and put an explanation to this situation.

What did I learn?

Common sense escapes sometimes in the field of software why?

• the rules of software world are not the same as the physical world (the effects not local and proportional to causes)
• code comments, documentation and nomenclature are key in long lasting software
• Entropy applies to code too (entropy is mostly used in thermodynamics)
• Good software are not the monopoly of large companies (I made my small guess about it before)
• The "relational" database entropy = the perfect storm... and database as a separate component is a time-limited technology.
• The evaluation of entropy can be a negotiation argument

What to do about it?

Launching the adventure of building a software is always thrilling, but making it last long is an art requiring rigor.

Thinking twice in its early stage about its architecture will certainly make solid foundations and its future brighter. Granularity and modularity and new technologies of databases/register definitely are a key components of a better software future.