• Title 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts
• Author(s) Richard Monson-Haefel
• Publisher: O'Reilly Media; eBook (Creative Commons Licensed)
• License(s): Creative Commons License (CC)
• Hardcover 222 pages
• eBook PDF
• Language: English
• ISBN-10: 059652269X
• ISBN-13: 978-0596522698
• Share This:  

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. 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.

• Richard Monson-Haefel , an independent software developer, coauthored all five editions of Enterprise JavaBeans and Java Message Service (all O'Reilly).

• Amazon

• Software Engineering Principles and Practices
• Agile, Scrum, Kanban, Extreme Programming (XP), etc.
• Software Engineering
• Books by O'Reilly®

• 97 Things Every Software Architect Should Know: Collective Wisdom from the Experts
• The Mirror Site (1) - PDF
• The Mirror Site (2) - PDF

• Software Architecture Patterns (Mark Richards)

  This book takes a deep dive into many common software architecture patterns. Each pattern includes a full explanation of how it works, explains the pattern's benefits and considerations, and describes the circumstances and conditions it was designed to.

• 97 Things Every Data Engineer Should Know (Tobias Macey)

  With this in-depth book, current and aspiring engineers will learn powerful real-world best practices for managing data big and small. Experts share their experiences and lessons learned for overcoming a variety of specific and often nagging challenges.

• 97 Things Every Cloud Engineer Should Know: from the Experts

  With this book, professionals from around the world provide valuable insight into today's cloud engineering role. It explore the entire cloud computing experience, including fundamentals, architecture, and migration.

• 97 Things Every Programmer Should Know (Kevlin Henney)

  With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice.

• 97 Things Every Programmer Should Know - Extended

  This books is a collection of additional 68 essays available at the site but doesn't appear in Kevlin's book: 97 Things Every Programmer Should Know. The text in the book is taken from site **as is**.

• O'Reilly® 97 Things Every IT Project Manager Should Know

  This illuminating book contains 97 short and extremely practical tips - whether you're dealing with software or non-IT projects - from some of the world's most experienced project managers and software developers.

• Software Architect (Nigel Leeming)

  This book tells you what top software architects think is important and how they approach a project - it is about how individuals can take the lead in realigning our development efforts to that promise. If you want to enhance your career, this book is essential reading.

• Software Architecture (A. Bijlsma, et al)

  This book is the discipline concerned with model-based description and analysis of software systems with a view to satisfying the (often contradictory) concerns of stakeholders.