EUR 25,77
  • Tous les prix incluent la TVA.
Il ne reste plus que 1 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon.
Emballage cadeau disponible.
Quantité :1
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir cette image

Journey of the Software Professional: The Sociology of Computer Programming (Anglais) Relié – 7 octobre 1996


Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon Neuf à partir de Occasion à partir de
Relié
"Veuillez réessayer"
EUR 25,77
EUR 25,77 EUR 1,99

Offres spéciales et liens associés


Descriptions du produit

Quatrième de couverture


23661-2

A breakthrough model for understanding software development— and breakthrough techniques for improving it!

You can't improve the way you develop software if you don't understand it. Journey of the Software Professional offers the first complete model of software development—based on the newest research in cognitive psychology and organizational behavior. But that's just the beginning. At its heart, this is a book of practical advice for developers and managers who are serious about enhancing their own effectiveness, and the effectiveness of their teams.

This book transcends the boring, self-evident advice you've heard a thousand times before, with fresh insights into:

  • Choosing the best work environment for your personality and workstyle
  • Building on your personal and management strengths, and avoiding common errors
  • Finding better ways to approach individual and team problem-solving
  • Creating a better team culture
  • Improving communication effectiveness
  • Managing both technological and organizational change

Crammed with advice for both developers and managers, Journey of the Software Professional covers an extraordinary range of topics—and presents them through a coherent Structure-Process-Outcome framework that helps you make sense of your own experience.

You'll discover tools and techniques for building and implementing your own career development plan. You'll learn the concepts underlying well-designed system architectures and how to apply these concepts to create an architecture appropriate for your project. At the same time, you'll learn how to create organizational structures that support this architecture and manage the growth of the team over the life of the project. You'll learn how to develop long-term strategies for improving your organization's software development. And a whole lot more.

No matter what role you play in software development, or where you are in your career, this book represents a breakthrough in understanding what you're doing — and how to do it better!

“In many ways, it opened my eyes. If you are a software professional, I think it will open yours as well.” —Gerald M. Weinberg



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

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 13 commentaires
10 internautes sur 11 ont trouvé ce commentaire utile 
A software manager's "must read" 10 janvier 2001
Par B. Scott Andersen - Publié sur Amazon.com
Format: Relié
Journey of the Software Professional is an impressive work. It begins with a Forward by noted author Gerald Weinberg (The Psychology of Computer Programming, etc.) where Weinberg says "In many ways, it opened my eyes. If you are a software professional, I think it will open yours as well." I couldn't have said it better.

This book should be read by software development managers before their first assignments. Hohmann not only provides software engineering guidance and wisdom in real-world context but also, where possible, backs up his thinking with published works, all carefully annotated.

What separates this work from most software engineering texts is Hohmann's ability to keep the work meaningful and relevant to real-world development environments. Many other texts note that most shops are at an SEI Level I maturity yet those same books delve into COCOMO II or McCabe's cyclomatic complexity--concepts and practices foreign in those same shops. It is easy to fill books with details of these and other software engineering tools and techniques but unless these things are placed in a meaningful context, they are simply tools absent of purpose.

What Hohmann offers is much more: a way to think about the real problem to be solved by engineering management: the maturation of the software development department. It is along these lines that Hohmann shines. For example, in one section discussing conflict, Hohmann asks "How much time, if any should be allocated to the schedule to allow programmers to rework their code?" Refactoring (Fowler) is a new spin on how to accomplish this but acknowledging, at a management level, that such activities go on is not widely discussed in most texts. Hohmann challenges readers to think about problems such as these.

Throughout the book are sections entitled "Advice to Managers" and "Advice to Developers". Most of the advice is rock solid and could apply anywhere for the same reason The Mythical Man Month (Brooks) is still relevant and should be required reading by all software managers: software development is (and always has been) about people! While tools and techniques evolve quickly, people have not.

Because every author wants to bring something new and fresh they'll introduce some spin on their particular approach. Hohmann offers SPO: Structure-Process-Outcome to fulfill this pension. While I think it doesn't add much, neither does it detract. There is plenty in this book to let it stand on its own merit.

I didn't agree with everything in this book. There are few books I can give blanket and unreserved approval to, in fact. But this book did do what Weinberg promised in his Forward: it made me THINK. The book's subtitle is "A Sociology of Software Development" and that description fits well. It is not a substitute for a solid book on software engineering techniques. But, I believe this book would greatly supplement anyone's library whose quest is to better understand the discipline.
5 internautes sur 6 ont trouvé ce commentaire utile 
Interesting perspective. 3 avril 2000
Par Un client - Publié sur Amazon.com
Format: Relié
This book has an interesting outlook on software development. Beware it is 'the sociology of computer programming' as it says in the title - only read it if this is of interest to you. For this reason it delves into the reasons why people build software the way they do and provides the framework into which all the engineering methods and methodologies fit.
However, it's too tedious in places and contains too many hollow platitiudes despite parts being built on what appears to be a sound academically researched foundation. Pick it up if you have room for a book to round out your engineering expertise but don't expect the kind of experience as in reading 'Design Patterns' for the first time, for example.
4 internautes sur 5 ont trouvé ce commentaire utile 
Plenty of goodies, but also some aridities 7 juin 1999
Par SeanFurl - Publié sur Amazon.com
Format: Relié
I found it crowded with good advice and ideas. I also found myself skipping and jumping around in it after a while, and putting it down altogether, because it was getting a bit tedious. But I would leave it lying in a visible place and pick it up again some evenings later. And every time I picked it up I found good and valuable advice in it. There are headings and subheadings on just about every page and the text under them is more or less self-contained: so it's amenable to browsing (chapter 1 excepted). And believe me, it has a huge amount of content. One of the things I like is its stated intention to make you a happier developer, not just a better developer. The causes of developer suffering and confusion are predominantly management and human issues, needless to say, since the machine and machine tools continue to be on their best behavior. The book has helped me avoid some suffering and confusion. It is not B.S.
1 internautes sur 1 ont trouvé ce commentaire utile 
Touchie-feelie techie? 23 mars 2006
Par wiredweird - Publié sur Amazon.com
Format: Relié
"The integrated framwork provides a complete theory of human problem solving." (p.41)

There's a lot of good in this book. For example, back in `97, Hohmann was already exhorting managers to allow refactoring (called reworking back then), in anticipation of current eXtreme/agile practice (p.73). There's a lot of conditional good here too: "[having] determined your coding values, use them consistently..." (p.93) In other words, figure out what matters in your code, outside of getting the nominal job done: performance, maintainability, portability, or whatever. Something about a foolish consistency springs to mind, though. In any complex program, one part might be critical to performance, another might be memory-limited, reliability might be an absolute demand in another section, and so on, requiring a flexible attitude that doesn't fit well with dogmatic dicta. Hohmann has also chosen a presentation format, with explicit asides to both managers and developers, that summarizes his advice clearly, without descending to sound bites - at least, not descending all the way.

Things like that quote I started with bother me, though. Yes, I appreciate self-assurance and enthusiasm, but not when they turn into hype and hyperbole. That must be the cheerleader part of the aerobics instructor in him coming through. (He's very proud of that achievement, and reminds us of it repeatedly - as if this will impress an uber-geek.) Then there's the tired trotting out of pop-psych standards: personality quizzes, the Johari window, and the rest.

There are some nuggets here. They're wrapped up in so much fluff that they're hard to find, though. Maybe this book will help someone, especially a techie being turned into a manger, but that reader will have to wade through feel-good fuzzies and partial truths to find that help.

//wiredweird
1 internautes sur 1 ont trouvé ce commentaire utile 
Nice instight hidden in the pages 25 janvier 1999
Par Un client - Publié sur Amazon.com
Format: Relié
The book is not bad. The most valuable sections of this book include topics of Structure-Process-Outcome (sometimes), cognitive learning, values, culture, goals, working with tools, and communication. The diagrams and tables in this book are almost not helpful at all; sometimes you wonder if diagrams like figure 1-3 on page 23 is downright necessary to have there. I felt like parts four and five of the book really dragged on unnecessarily, especially the chapter on organizational engineering. It seemed as if the book completely broke down and lost it after page 300. I think that Hoemann had a lot of potential in this book when I first saw it, and I was let down. Another nice thing would be for him to drop the plethora of coined-terms. Overall, there is some really nice thoughts in here, but there is a lot of unnecessary things that you have to thumb through.
Ces commentaires ont-ils été utiles ? Dites-le-nous


Commentaires

Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?