As the digital economy changes the rules of the game for enterprises, the role of software …. Today, software engineers need to know not only how to program effectively but also how to …. Skip to main content. Start your free trial. Buy on Amazon. Book description In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. Show and hide more.
Table of contents Product information. Application Architecture Determines Application Performance 6. Seek the Value in Requested Capabilities 7. Stand Up! Everything Will Ultimately Fail 9. Quantify Commit-and-Run Is a Crime Business Drives Architects Must Be Hands On Continuously Integrate Avoid Scheduling Failures Architectural Tradeoffs Database As a Fortress Use Uncertainty As a Driver Get the 1,Foot View Try Before Choosing Most of them talk about concrete scenarios and how to deal with them.
They are also independent and can be read one-by-one — there is no progression from one essay to the next. As someone who has been this role for some time now, it really resonated with me that a lot of the advice is not technical but rather focussed around team work and enablement.
The role of an architect is more than, as the many voices on this book repeatedly tell us. I have included here what I feel are the highlights from the book and cover most of the messages conveyed in it. So this book is as Short and easy read.
So this book is as goos as you and your own experience in the field. If you are familiar with Agile software development and Domain Driven Design, you will find many of the tips in the book have relevance!
To sum up the most important things I got from the book: - Go Agile, Go Agile, Go Agile - Design patterns is important they are not those of GoF patterns only , but you should know anti-patterns, and refactor to patterns not try to force applying them in the first place! Oct 22, Tomi Turtiainen rated it it was ok. The problem is that this is not really a book per se, but instead just a collection of short articles circling around the topic of software architects.
It does give you some sort of an idea about the work of software architects — what they job consists of, what kinds of problems they're dealing with. But then again most of the advice given is really common sense. The most interesting part was the story how a database was selected for the M1 Abrams battle tank's software system.
I'm sure there ar The problem is that this is not really a book per se, but instead just a collection of short articles circling around the topic of software architects. I'm sure there are better books if you're interested in being a software architect.
Nov 15, Robson Castilho rated it liked it Shelves: software. This book is a set of 97 short essays written by a lot of software architects. It brings us nice advises encompassing technical aspects and soft skills.
Easy and fast reading, it's a good book for everyone who wishes to understand better the skills needed to a software architect and a good start to think about the "big picture" of a software project. May 29, Sebastian Gebski rated it it was ok. Fit more for an aspiring developer than actual architect.
Not really revealing, bloated with repeated expert bios. Skip it. It's a must-read position, not should-read. I would even say that it should be reread every year. Very convenient to read chunk by chunk, you don't need to spend too much time to read a whole chapter at once.
Most of the chapters apply not only for architects, just remember, you don't have to be called an architect to think about an architecture.
Good book. Pretty much philosophic. Needs from you not just to read it and close it forever, but to reread some parts of it now and then, think about given suggestions, try to change yourself and your environment. This book is useful not only for software architects, but for software developers as well.
Dec 27, Ankita Mogha rated it really liked it. After a long time, I have read a technical book and reading this book has been a completely different experience as compared to the other technical books I have read before.
This book gives insights of the things a software architect should know from the perspective of the technical experts. I have an urge of re-reading the book and write another refined article of my other majo After a long time, I have read a technical book and reading this book has been a completely different experience as compared to the other technical books I have read before. I have an urge of re-reading the book and write another refined article of my other major learnings from this book.
Feb 16, Danylo Bilokha rated it liked it Shelves: tech-skills. I am not sure what for this book as personally I found it as the book which gives general and overall understood, by everybody more or less experienced, rules and approaches.
Aug 26, Christoph Kappel rated it it was amazing Shelves: , l-english , c-architecture. This book is basically a collection of well-intended advises, picked from a long list initially collected in some kind of forum, which appears to be absent right now. Too bad some things don't age that well. Anyway, some of the advices here are common sense, other ones are really interesting and worth to follow or rather try out, like if there is only one solution to a problem you really need to get a second opinion to verify, if you really understood the problem.
The premise here is that there s This book is basically a collection of well-intended advises, picked from a long list initially collected in some kind of forum, which appears to be absent right now. The premise here is that there should be more than one, just with trait-offs. Jun 11, Ahmed Gamal rated it it was ok. A collection of short advices from different individuals.
Which makes it very repetitive and shallow. Very good advices from experienced people but Probably the table of content with a line description on each point was enough to deliver the message. I completed the whole book but it was very easy to speed read many parts.
Jul 03, Leo Mazzi rated it liked it. Well why 97? That was my first question. Then after reading it it was - it was not even 97! Several advices are same thing said with other words, a lot of it are advices from same autors so in general was not much usefull or new. That is why I probbably needed almost a month to finish it.
Mar 15, Dhara Patel rated it liked it. This book contains a lot of really great advice, but the tips are poorly structured. It would be much easier to read and retain the information if the 97 things were organized into sections with a unifying theme or ordered sequentially to parallel the process of designing a software system. It is not very revealing book, however it is still worth to read. It contains 97 articles written by different authors. Some of them are more intersting, some of them less interesting.
In general, it focuses on non-technical aspects of being architect. Not enough content to be useful Like this: How to get a million dollars and not pay taxes? First, get a million dollars. From Steve Martin.
0コメント