Skip to content
#Software

Brain defragmentation. Building from the inside

#Software #Architecture #SoftwareDevelopment #Engineering #Management

This book by Sergey Tarasov was published ten years ago and was devoted to the creation of software. I read it for the first time seven years ago, and I had the feeling that it was a standard story about how the grass used to be greener, the sun yellower, and the sky bluer. Over the weekend, I read the book again and realized that I didn’t think it was, but it also has a useful grain. And now the thesis about the book The author has spent his whole life developing custom enterprise applications (mostly accounting) It describes the standard model of work of the customer-contractor, where the contractor connects using the model of fix-price or time and materials. The author talks well about the concept of layers, tiers, mentions CORBA and SOA. (It's a good thing the author wrote the book before microservices.) Of all the options, the author prefers 2Tier architecture with thin client and logic in the database, from which it persistently makes an application server The author does not like patterns, as they teach pattern thinking and reproduce arbitrary patterns from GoF “for any specialist with abstract thinking skills, it hardly takes more than an hour.” The author does not like processes, especially Agile, because they threw out the architectural and design stage of the solution. True, the author tells about the spiral model of Barry Boham, which still sounds interesting. (But few people know.) The author is sometimes fond of telling stories about technology and details, which few people are interested in.

Of the moments I like, I can mention The author speaks clearly and focuses on understanding the subject area. The author accurately notices the essence and pokes the weaknesses of approaches and methodologies in his stories. The author talks about accounting systems and the design of the accounting system:)

In general, it seems to me that this book is worth reading to experienced engineers to be able to appreciate the tendentious thoughts of the author and compare with his own experience:)

#Software #Architecture #SoftwareDevelopment #Engineering #Management