I have been working with "Clean Architecture" on commercial projects for about three years, so the main purpose of my reading was to go deep into the I have been working with "Clean Architecture" on commercial projects for about three years, so the main purpose of my reading was to go deep into the source of where it all began. Following the corporate rules that were based on top of this book was fun, but I was always wondering if the practical approach that I used matched the point of view of the author.
The book has a really promising start. It says: "Despite all the new languages, and all the new frameworks, and all the paradigms, the rules are the same now as they were when Alan Turing wrote the first machine code in 1946. Now, with half a century of experience behind us, we have a grasp of those rules. And it is those rules—those timeless, changeless, rules—that this book is all about." "It describes what good clean architectures and designs look like so that software developers can build systems that will have long profitable lifetimes".
Unfortunately, I cannot say that the way the author "describes rules and good clean architectures" is clear and simple to understand for developers without prior practical experience of what this is all about. And reading negative comments proves that many readers did not get the point and beauty of "clean architecture". This understanding could come only by applying the information from this book in practice.
On another hand, for those who got acquainted with "clean architecture" with hands-on practical experience, this book is must read. It clears all the questions and misunderstandings that might happen. It is like seeing the whole picture from above and everything falls into place. It will be much easier to make decisions regarding planning the system and structure of the future application after reading this book.
It is a really good book, it is just after making such a big impact on software development in general I expect just a little bit more from it....more
This is not a fresh book and some parts are already not as interesting as they could be, on another hand regardless of how old this book there are somThis is not a fresh book and some parts are already not as interesting as they could be, on another hand regardless of how old this book there are some "best practices" that many programmers are willing to ignore even today. During my programming study and first job, most of the time when I heard about the "Clean Code" book was during code review, as the "dogma", a set of rules I have to follow. This is what this book has become famous for, simple rules by following which you might feel and have seen as a professional. Despite that, the book is not about rules and insists that it is not a dogma. What I see in this book is the intention of authors to work with a reader to develop in him a desire to write the best code that he can write. To achieve that throughout the book there are many fairly offensive words used to describe some style of code that in fact might be written by anyone. In contrast to technical books, where the style guide is dry, Clean Code makes you feel bad and guilty about the code that you have been writing in past....more
Коли я вперше причитав цей роман я був ще підлітком. Тоді в мене ще не було великого досвіду у читанні книжок, та й тема книжки про відносини, досвідуКоли я вперше причитав цей роман я був ще підлітком. Тоді в мене ще не було великого досвіду у читанні книжок, та й тема книжки про відносини, досвіду в яких в мене теж особливо не було. То ж на той час мені ця книжка зайшла. Тому і оцінку ставлю не погану, бо реально є коло людей, якому цей роман буде цікавий. Але звісно сьогодні я б не взявся читати щось подібне. Дуже примітивний сюжет. Буквально звичайне життя звичайної людини, яке, як я розумію, головним чином бузується на реальних історіях життя Ірени Карпи. Таке може бути цікаве лише явним фанатам творчості Ірени Карпи як особистості. Тобто це той момент, коли людина, яка її написала є тим інтересом до книжки, а не те що написано....more
Head First "Kotlin" is a really simple guide of the programming language. This book has nothing to do with Android, but it is not needed, it is only aHead First "Kotlin" is a really simple guide of the programming language. This book has nothing to do with Android, but it is not needed, it is only about pure Kotlin. The book includes many useful tricks and makes clear specific particularities without redundant theory, with only that stuff which is needed in practice....more
Core Java, Volume 1: Fundamentals by Cay S. Horstmann - is the most advised book by mentors for all android and java developers, and at the same time Core Java, Volume 1: Fundamentals by Cay S. Horstmann - is the most advised book by mentors for all android and java developers, and at the same time is the driest literature I have ever read. I believe that the space shuttle flight manual would be easier to read. In addition, I cannot understand what so special about this book as half of the information in it is outdated and useless....more
Loading...
