Herding Cats: A Primer for Programmers Who Lead Programmers und über 1 Million weitere Bücher verfügbar für Amazon Kindle . Erfahren Sie mehr


oder
Loggen Sie sich ein, um 1-Click® einzuschalten.
oder
Mit kostenloser Probeteilnahme bei Amazon Prime. Melden Sie sich während des Bestellvorgangs an. Erfahren Sie mehr
Alle Angebote
Möchten Sie verkaufen? Hier verkaufen
Herding Cats: A Primer for Programmers Who Lead Programmers
 
 
Beginnen Sie mit dem Lesen von Herding Cats: A Primer for Programmers Who Lead Programmers auf Ihrem Kindle in weniger als einer Minute.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Herding Cats: A Primer for Programmers Who Lead Programmers [Englisch] [Taschenbuch]

J. Hank Rainwater , Hank Rainwater

Preis: EUR 29,99 kostenlose Lieferung. Siehe Details.
  Alle Preisangaben inkl. MwSt.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Auf Lager.
Verkauf und Versand durch Amazon.de. Geschenkverpackung verfügbar.
Lieferung bis Samstag, 2. Juni: Wählen Sie an der Kasse Morning-Express. Siehe Details.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 20,13  
Taschenbuch EUR 29,99  

Kunden, die diesen Artikel angesehen haben, haben auch angesehen


Produktinformation


Produktbeschreibungen

Amazon.co.uk

Geared to the software developer newly promoted to manage other developers, Herding Cats: A Primer for Programmers Who Lead Programmers distils the author's several decades of project management experience into a worthwhile tour of some best practices for those making the transition.

Written in a lively style that doesn't pull any punches when it comes to the hard realities of leading technical teams, this book offers plenty of practical advice and will be worth it for any IT manager who wants a veteran's perspective on the battle to create great software on-budget and on-time.

While many titles on software engineering and management lean toward the theoretical, this book’s candid and practical focus help distinguish it from the crowd. It also helps that he's a good writer, and mixes quotes from a variety of sources (including Jack Welch and Andy Grove). This is one of the few titles to concentrate on the all too common problem of good programmers promoted to project leads, where management and people skills will often determine success, rather than raw programming chops.

Early sections outline the basic personality types that the author has encountered in software. Ranging from the gifted "architects" and "constructionists" to "magicians" and "slobs" and "salad chefs", this taxonomy is as good as any, and any reader will recognise many types encountered in any career in IT. Basic tips include mixing team personality types effectively and getting started with managing programmers from philosophical ideas about what constitutes leadership, to practical suggestions for hiring and firing, running meetings, and working as manager to improve your company's bottom line.

Noteworthy sections here on design philosophy outline the importance of thinking about architecture and re-use as you build software. Techniques like adhering to programming standards throughout your shop and designing objects with good cohesion and loose coupling are advocated here. A section on anti-patterns in management outlines the management styles that lead to trouble. (Tips for overcoming micro-management, do-it-all/know-it-all managers, and improving communication will help you defeat these tendencies, both in yourself and others).

Later sections survey the basics of software engineering and software process including the Microsoft Solution Frameworks and Extreme Programming (XP) as ideas to check out. Final sections look at the author's own software for managing projects (the executable and code are downloadable). An annotated bibliography of books can provide a start for any new manager's shelf. In all, this title can be a source of comfort and advice for those taking on new leadership positions on technical teams with its wide-ranging perspective on what it takes to lead other programmers successfully. --Richard Dragan

Topics covered: Management techniques for programmers promoted to leadership positions, assessing your level of technical "cool", positive and negative programmer personalities (including architects, constructionists, speed demons, magicians, minimalists, analogists); trouble types (including slobs, amateurs, salad chefs), tips for new managers (including adapting to changes), dealing with project feature creep, dealing with ineffective programmers, tips for hiring and firing, promotions, organising for success (using paper and e-mail effectively), the author's custom Administrative Director program (for organising project tasks), corporate goals, product and project management, managing change throughout the project lifecycle, tips for running staff, design and other meetings, effective technical leadership (designing with architecture and re-use in mind), design hints (programming standards, strong object cohesion and low coupling between objects), reviewing code, anti-patterns in management (including micromanagers, unfocused management, and misapplied genius), hints for overcoming bad management styles, leadership principles (fostering effective communication, delegating, and participating), techniques for mentoring and rewarding employees, fostering employee loyalty, leadership for different generations, case studies of several tech leaders (Andy Grove and Bill Gates), how to work with your boss (communicating deadlines and limits, overcoming inertia), techniques for managing a distributed workforce, multicultural factors in management, intro. to software engineering and process (overview of the Microsoft Solutions Framework, Extreme Programming, XP, and Agile Development), craftsmanship in software, dealing with technology change and economic downturn, appendices for the author's Administrative Director software (including a code review), case studies of effective and ineffective management techniques from the field.

Amazon.com

Geared to the software developer newly promoted to manage other developers, Herding Cats: A Primer for Programmers Who Lead Programmers distills the author's several decades of project management experience into a worthwhile tour of some best practices for those making the transition. Written in a lively style that doesn't pull any punches when it comes to the hard realities of leading technical teams, this book offers plenty of practical advice and will be worth it for any IT manager who wants a veteran's perspective on the battle to create great software on-budget and on-time.

While many titles on software engineering and management lean toward the theoretical, this book’s candid and practical focus help distinguish it from the crowd. It also helps that the author is a good writer and mixes quotes from a variety of sources (including Jack Welch and Andy Grove). This is one of the few titles to concentrate on the all-too-common problem of good programmers promoted to project leads, where management and people skills, rather than raw programming chops, will often determine success.

Early sections outline the basic personality types that the author has encountered in software. Ranging from the gifted "architects" and "constructionists" to "magicians" and "slobs" and "salad chefs," this taxonomy is as good as any, and any reader will recognize many types encountered in any career in IT. Basic tips include mixing team personality types effectively and getting started with managing programmers, from philosophical ideas about what constitutes leadership to practical suggestions for hiring and firing, running meetings, and working as manager to improve your company's bottom line.

Noteworthy sections here on design philosophy outline the importance of thinking about architecture and reuse as you build software. Techniques like adhering to programming standards throughout your shop and designing objects with good cohesion and loose coupling are advocated here. A section on anti-patterns in management outlines the management styles that lead to trouble. (Tips for overcoming micromanagement, do-it-all/know-it-all managing, and improving communication will help you defeat these tendencies, both in yourself and others.)

Later sections survey the basics of software engineering and software process, including the Microsoft Solution Frameworks and Extreme Programming (XP) as ideas to check out. Final sections look at the author's own software for managing projects (the executable and code are downloadable). An annotated bibliography of books can provide a start for any new manager's shelf. In all, this title can be a source of comfort and advice for those taking on new leadership positions on technical teams with its wide-ranging perspective on what it takes to lead other programmers successfully. --Richard Dragan

Topics covered: Management techniques for programmers promoted to leadership positions, assessing your level of technical "cool," positive and negative programmer personalities (including architects, constructionists, speed demons, magicians, minimalists, analogists), trouble types (including slobs, amateurs, salad chefs), tips for new managers (including adapting to changes), dealing with project feature creep, dealing with ineffective programmers, tips for hiring and firing, promotions, organizing for success (using paper and e-mail effectively), the author's custom Administrative Director program (for organizing project tasks), corporate goals, product and project management, managing change throughout the project lifecycle, tips for running staff, design, and other meetings, effective technical leadership (designing with architecture and reuse in mind), design hints (programming standards, strong object cohesion and low coupling between objects), reviewing code, anti-patterns in management (including micromanagement, unfocused management, and misapplied genius), hints for overcoming bad management styles, leadership principles (fostering effective communication, delegating, and participating), techniques for mentoring and rewarding employees, fostering employee loyalty, leadership for different generations, case studies of several tech leaders (Andy Grove and Bill Gates), how to work with your boss (communicating deadlines and limits, overcoming inertia), techniques for managing a distributed workforce, multicultural factors in management, intro to software engineering and process (overview of the Microsoft Solutions Framework, Extreme Programming--XP--and Agile Development), craftsmanship in software, dealing with technology change and economic downturn, appendices for the author's Administrative Director software (including a code review), case studies of effective and ineffective management techniques from the field.


In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Tags

 (Was ist das?)
Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte.
 

Kundenrezensionen

Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:  11 Rezensionen
19 von 19 Kunden fanden die folgende Rezension hilfreich
Worth taking a look at 13. April 2003
Von J. Fristrom - Veröffentlicht auf Amazon.com
Format:Taschenbuch
So I got this book: Herding Cats: A Primer For Programmers Who Lead Programmers, by J. Hank Rainwater. When the programmers I manage came into my office they'd see it and they'd say, "We're cats?!" "Better than being sheep," I answered.

Although I was put off by the author's photos in the introduction, and he quotes Steven Covey, it actually turned out to be quite good: it crystallized my thoughts in some areas and gave me brand new thoughts in others. And when you mostly agree with someone, maybe you should give those items you don't agree with, or rarely think about, another look.

The points I agreed with: avoid unnecessary meetings; leads can't be programmers anymore, but leads have to still code; hiring people you can't communicate with is no good, even if they're superstars; keep track of the tasks people are working on (duh); software development is more like gardening than construction (watching Greenfingers the other night I discovered that gardeners go through a design phase too); micromanagement is bad; geniuses shouldn't be made managers; borrow from software methodologies, don't accept one as a whole package.

And the points I realized where I had room for improvement: delegate, inspect, organize, and manage meetings. Since I read the book, about a year ago, I've tried to follow some of his advice in these areas. Some of it has worked, some hasn't, but I don't regret experimenting with any of it.

If you're like me, and you read almost every software management book you can get your hands on, this should be in your collection too.

20 von 22 Kunden fanden die folgende Rezension hilfreich
For all us programmers forced to lead our own breed... 25. März 2002
Von Martin S. Stoller - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Actually, I bought this book as a gift for my boss, but as I'm often called upon to mentor small groups myself (being the dinosaur of our department), I decided to read Rainwater's work over the weekend (being careful not to ear-mark it). As the book's introduction says, the first three chapters themselves are worth the money. Of course, this book isn't really for those lucky enough to have studied management (though even those would profit from the programmer "type" descriptions). But for all the other programmers destined to lead programmers, this is exactly what we need; the chapter about managing oneself is especially insightful. All common sense stuff, really, but sometimes a good spec (and this book can be seen as such) is needed even for things we already know, but don't practice. Rainwater's English is a joy to read, though I guess some of the in-jokes (given only as footnotes, so as not to disturb the flow of the otherwise serious text) are only understandable the "old" school programmers (yes, such as myself...).
12 von 13 Kunden fanden die folgende Rezension hilfreich
Too little substance and too many clichés.... 15. Januar 2003
Von cristof - Veröffentlicht auf Amazon.com
Format:Taschenbuch
I really wanted to like this book. The first half of the book is well-written, and brings up good points. But the second half of the book is very light on substance and uses clichés everywhere one can see. I was also embarassed to read about the cross-national case study, as it hinted at xenophobia.

The one rather good aspect of the book is its bibliography, since it provides narratives along with the books.


Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 


Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   
Ähnliche Foren


Lieblingslisten


Ähnliche Artikel finden


Anhand des Sachgebietes nach ähnlichen Produkten suchen:


Ihr Kommentar


Datenschutzerklärung von Amazon.de Versandbedingungen von Amazon.de Umtausch- & Rücknahme bei Amazon.de