Sign in with Facebook
“As you work in requirements meetings to design software, pretend that your customer is not your customer. It turns out that this is a very easy thing to do, because it is true. Your customer is not your customer. Your customer‘s customer is your customer. If your customer's customer wins, your customer wins. Which means you win.”
― 97 Things Every Software Architect Should Know
― 97 Things Every Software Architect Should Know
“Design is a discovery process, as we implement we discover new information, often impossible to know up front. By accepting that design is an ongoing and empirical process in a forever changing world, we learn that the design process must be flexible and ongoing too. Clinging onto your original designs and trying to force them through is only going to end up with one result so you need to learn to understand that it will never look like that.”
― 97 Things Every Software Architect Should Know
― 97 Things Every Software Architect Should Know
“True success in medicine is not easy. It requires will, attention to detail, and creativity. But the lesson I took from India was that it is possible anywhere and by anyone. I can imagine few places with more difficult conditions. Yet astonishing success could be found ... what I saw was: Better is possible. It does not take genius. It takes diligence. It takes moral clarity. It takes ingenuity. And above all, it takes a willingness to try.”
― 97 Things Every Software Architect Should Know
― 97 Things Every Software Architect Should Know
“Most projects are built by people, and those people are the foundation for success and failure. So, it pays to think about what it takes to help make those people successful.”
― 97 Things Every Software Architect Should Know
― 97 Things Every Software Architect Should Know
“To justify the risk involved with selecting new technology its benefits should be a quantum leap forward. Many new technologies claim such advancement but few deliver it. It‘s easy to look at new technology and see technical advantages but those benefits are often difficult to sell to stakeholders. Before you decide to blaze a trail with new technology, ask yourself how the business will benefit from this decision. If the best outcome from a business perspective is that no one will notice, rethink your decision.”
― 97 Things Every Software Architect Should Know
― 97 Things Every Software Architect Should Know
Serg’s 2025 Year in Books
Take a look at Serg’s Year in Books, including some fun facts about their reading.
11 books
|
109 friends
1,291 books
|
113 friends
300 books
|
202 friends
190 books
|
194 friends
189 books
|
106 friends
302 books
|
71 friends
483 books
|
43 friends
382 books
|
149 friends
More friends…
Favorite Genres
Polls voted on by Serg
Lists liked by Serg
