Commencez à lire 97 Things Every Software Architect Should Know sur votre Kindle dans moins d'une minute. Vous n'avez pas encore de Kindle ? Achetez-le ici Ou commencez à lire dès maintenant avec l'une de nos applications de lecture Kindle gratuites.

Envoyer sur votre Kindle ou un autre appareil

 
 
 

Essai gratuit

Découvrez gratuitement un extrait de ce titre

Envoyer sur votre Kindle ou un autre appareil

Tout le monde peut lire les livres Kindle, même sans un appareil Kindle, grâce à l'appli Kindle GRATUITE pour les smartphones, les tablettes et les ordinateurs.
97 Things Every Software Architect Should Know: Collective Wisdom from the Experts
 
Agrandissez cette image
 

97 Things Every Software Architect Should Know: Collective Wisdom from the Experts [Format Kindle]

Richard Monson-Haefel
3.7 étoiles sur 5  Voir tous les commentaires (3 commentaires client)

Prix conseillé : EUR 21,62 De quoi s'agit-il ?
Prix éditeur - format imprimé : EUR 35,88
Prix Kindle : EUR 15,13 TTC & envoi gratuit via réseau sans fil par Amazon Whispernet
Économisez : EUR 20,75 (58%)

Formats

Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle EUR 15,13  
Broché EUR 35,80  
Broché --  

Auteurs, publiez directement sur Kindle !

KDP
Via notre service de Publication Directe sur Kindle, publiez vous-même vos livres dans la boutique Kindle d'Amazon. C'est rapide, simple et totalement gratuit.
-40%, -50%, -60%... Découvrez les Soldes Amazon jusqu'au 5 août 2014 inclus. Profitez-en !





Les clients ayant acheté cet article ont également acheté


Descriptions du produit

Présentation de l'éditeur

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.


Détails sur le produit


En savoir plus sur l'auteur

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Commentaires en ligne 

5 étoiles
0
2 étoiles
0
1 étoiles
0
3.7 étoiles sur 5
3.7 étoiles sur 5
Commentaires client les plus utiles
3 internautes sur 3 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Retour d'expériences 18 mars 2010
Par Mahdi
Format:Broché|Achat vérifié
Ce livre est un retour d'expérience d'architectes de systèmes d'informations. Sa lecture permet d'avoir une idée sur les choses à faire et les choses à éviter, même si aucune loi ne permet de reconnaître la frontière qu'il y'a entre les deux.
J'ai aimé le côté spontané de ses auteurs.
Avez-vous trouvé ce commentaire utile ?
4.0 étoiles sur 5 le livre à lire absolument 2 février 2014
Par hatem
Format:Broché|Achat vérifié
étant donné architecte moi même, ce livre m'a bien aidé à cadrer et segmenter mon expérience.
il est essentiellement la compilation de plusieurs retours d'expériences de plusieurs architectes 'connus'.

je le conseille vivement.
Avez-vous trouvé ce commentaire utile ?
4.0 étoiles sur 5 Un livre sage sur le développement 1 janvier 2013
Par Pierre
Format:Broché|Achat vérifié
Ce livre contient une mine de conseils, rarement suivis dans les projets de développement en entreprise. Il devrait être plus lu.
Avez-vous trouvé ce commentaire utile ?
Commentaires client les plus utiles sur Amazon.com (beta)
Amazon.com: 3.3 étoiles sur 5  31 commentaires
114 internautes sur 118 ont trouvé ce commentaire utile 
1.0 étoiles sur 5 I want my money back 21 juillet 2009
Par Rao Venugopal - Publié sur Amazon.com
Format:Broché|Achat vérifié
Heavy on keywords and low on actual content / value.

Imagine your Dad rings you up and says, "Be sure to go to work bright and early..." or "The early bird gets the worm" and proceeds to ramble on for 5 minutes about why that is important. We have all been through this kind of lecture. For politeness sake, you bite your tongue and zone out.

Now replace Dad with Bill Gates/ Steve Jobs/ some famous architect. However the advice being doled out is similar. eg. "Be sure to have a decent UI for every component/ blah blah blah".
How would you feel if you had to read 97 articles by famous architects / tech gurus, each 2 pages long and the entire content of the article is in the first introductory line itself. The rest is fluff.
I don't know about you, but when I am paying 20+ dollars for a book, I expect more than simple fluff.

-V
73 internautes sur 76 ont trouvé ce commentaire utile 
1.0 étoiles sur 5 Not worth the money 6 août 2009
Par Charles D. Sewell - Publié sur Amazon.com
Format:Broché|Achat vérifié
This book is just an accumulation random advice collected for "free" off a blog. You will feel like you have read a bunch of fotune cookies (i.e. "The longest trip begins with a single step") on the topic of architecture. Not a single topic is explored in depth since each topic is only 2 pages in length.

I would not recommend this book.
36 internautes sur 37 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Lack of Detail 5 juillet 2009
Par C. Roeder - Publié sur Amazon.com
Format:Broché
I found many of the contributions interesting, but wished for more detail. Many are not much longer than a page and left me wanting.
25 internautes sur 25 ont trouvé ce commentaire utile 
1.0 étoiles sur 5 incoherent and useless 25 décembre 2009
Par Dr. Gernot Starke - Publié sur Amazon.com
Format:Broché
Why does a famous (and, he has proven it, excellent) technical writer dare to compile
such a useless, incoherent and impractical amount of pseudo-advice?

His other books provided deep technical knowledge and practical help.

This one's not worth its price - there are much better books available...

alternatives: Taylor et al: Software Architecture (Foundations, Theory and Practice): Great read.
Bass et. al: Software Architecture in Practice: Great read.
Buschmann et. al: Pattern-oriented Software Architecture: Great series.
Fowler: Patterns of Enterprise Application Architecture: Great, highly practical...

So - don't bother with this one, go get a good book :-)
11 internautes sur 12 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Not really about software architecture, but pleasant reading nonetheless 7 août 2009
Par brian d foy - Publié sur Amazon.com
Format:Broché
[97 Things Every Software Architect Should Know] is much more broad than most people would expect from its title. It's certainly true to its title, but I expected that it would have be 97 things software architects should know about software architecture. Many of the points, while good advice otherwise, aren't special to software or software architecture. They are points any manager, project leader, or executive could apply. It's really 97 Things Every Project Manager Should Know, although there's already a book for that.

The first thing every software architect should know is what is expected from that job title, and I was hoping someone would at least try to define it. In reality, the title is a dumping ground for the tasks you don't give to the programmers but don't trust to the executives, and the job description varies widely.

My notion that nobody really knows what a software architect should do is reinforced by reading the advice from the many contributing experts, each of which briefly write about what they think is important. Some of that advice conflicts with other contributors, is so general so that the it would suitable in any business book, or merely shows that anyone touching a keyboard might be labelled a "software architect".

I was surprised that a lot of the advice tried to actually force the commoditization of "software architect", as if the actual person doing the job was interchangeable. An architect's experience, vision, and artistry should be at the center of the endevour. Architects are not cogs; they create and enforce the philosophy and design concept. In that regard, I actually only know a handful of software architects. Most people who consider themselves an architect, however, are probably merely applying the design and philosophy that somebody else created.

Setting aside the definition of architect, the advice is good for almost any project leader involved with software development no matter their job title. It's much better advice, however, for the journeyman who wants to be a project leader someday.

As with many management books, anecdotes are rife and facile. They are the sort of things you might mention in an elevator, such as changing the Mach 2.5 requirement of the then-future F-16 fighter plane to "escapes combat quickly", but that anecdote doesn't really help anyone, or at least not in the same way as something holistic and fleshed-out like Skunk Works: A Personal Memoir of My Years of Lockheed. I would have appreciated footnotes or references to complete case-studies.

Given the short format of each contribution, this generality is probably unescapeable. That's mitigated somewhat by the accompanying website for the book where longer discussions might take place. There's no overarching concept or guidance since the contributors are advising in different dimensions, coming from different experiences, and using their own idea of what a software architect should do. Very few contributors talk in terms of the complete software life-cycle; much of the advice in the vein is about requirements research, and even then is mostly about proper mindset rather than useful techniques.
Ces commentaires ont-ils été utiles ?   Dites-le-nous
Rechercher des commentaires
Rechercher uniquement parmi les commentaires portant sur ce produit

Passages les plus surlignés

 (Qu'est-ce que c'est ?)
&quote;
Simplicity through experience rather than generality through guesswork. &quote;
Marqué par 13 utilisateurs Kindle
&quote;
"All architecture is design but not all design is architecture. Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change." &quote;
Marqué par 11 utilisateurs Kindle
&quote;
If you're in any situation where you're talking to more than one person about your guidance, stand up. &quote;
Marqué par 9 utilisateurs Kindle

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Thème:
Première publication:
Aller s'identifier
 

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon
   



Rechercher des articles similaires par rubrique