97 Things Every Software Architect Should Know

97 Things Every Software Architect Should Know

Buch
5.01
Technology, Agile, Software Architecture, Software Engineering, Management

Durch das Verwenden dieser Links unterstützt du READO. Wir erhalten eine Vermittlungsprovision, ohne dass dir zusätzliche Kosten entstehen.

Beschreibung

In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as: * Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) * Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) * Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) * Simplicity Before Generality, Use Before Reuse (Kevlin Henney) * For the End User, the Interface Is the System (Vinayak Hegde) * It's Never Too Early to Think About Performance (Rebecca Parsons) To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.
Haupt-Genre
Fachbücher
Sub-Genre
Informatik
Format
Buch
Seitenzahl
220
Preis
29.90 €

Beiträge

1
Alle
5

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 should be more than one, just with trait-offs.

Beitrag erstellen