CARVIEW |


97 Things Every Software Architect Should Know
By:
Publisher: O'Reilly Media, Inc.
Pub. Date: February 5, 2009
Print ISBN-13: 978-0-596-52269-8
Pages in Print Edition: 224
Subscriber Rating:
[3 Ratings] Subscriber Reviews
Overview

Patterns of Enterprise Application Architecture
by Martin Fowler; David Rice; Matthew Foemmel; Edward Hieatt; Robert Mee; Randy Stafford

Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
by Gregor Hohpe; Bobby Woolf
Top Sellers in this Category

Code Complete, Second Edition
by Steve McConnell

The Pragmatic Programmer: From Journeyman to Master
by Andrew Hunt; David Thomas

Designing with the Mind in Mind: Simple Guide to Understanding User Interface Design Rules
by Jeff Johnson

Beautiful Visualization
by Julie Steele; Noah Iliinsky

Head First Software Development
by Dan Pilone; Russ Miles
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.
Subscriber Reviews
Average Rating: Based on 3 Ratings
"you MUST read this book" - by Anonymous on 24-SEP-2010
Reviewer Rating:
I first thought that with such a title "...every software architect should know.." it was again a marketing hack.
I must admit that this book, if read by a mojority of software architect, will be a fantastic advancement.
It nice to know patterns and practices but if read this book and understand it you will be a fantastic software engeneer/architect.
As a one time reading or a bedside book it's not "should read" it's MUST read.
Report as Inappropriate
Browse Similar Topics
Top Level Categories:
Information Technology & Software Development
Sub-Categories:
Information Technology & Software Development > Software Engineering & Development
Some information on this page was provided using data from Amazon.com®. View at Amazon >
Table of Contents
Extras
The publisher has provided additional content related to this title.
Description | Content |
---|---|
Visit the catalog page for 97 Things Every Software Architect Should Know | |
Visit the errata page for 97 Things Every Software Architect Should Know |
About Safari Books Online •
Terms of Service •
Gift Subscriptions •
Privacy Policy •
Contact Us •
Corporate Licenses •
Help •
Accessibility |
Copyright 2011Safari Books Online. All rights reserved.