告别失控：软件开发团队管理必读 ( etc.)（Z-Library）

【One-Line Pitch】 A practical field guide to managing software people and teams, built on nearly 70 years of combined engineering-management experience. Best for newly promoted programming managers, engineers eyeing a management path, and anyone who has to make unpredictable developers deliver predictable software. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core problem — software teams feel unmanageable because programming is closer to a craft than a strict engineering discipline, and because programmers differ enormously as individuals. Introduces the book's central thesis: manage the people, and the process problems follow. - **Early (~10%–30%)**: Builds the foundation of understanding programmers — job categories (client, server, database, Web/scripting), programmer archetypes (architects, systems and application programmers), domain knowledge, employment arrangements, generational and personality differences. Ends by arguing that outstanding programmers are disciplined "craftsmen," not just talented coders. - **Early–Middle (~30%–45%)**: Moves into the hiring pipeline — deciding what kind of programmer you need, writing job descriptions, continuous recruiting, résumé screening, interviewing, making the offer, and getting the new hire productively onboarded from day one. - **Middle (~45%–65%)**: The management core: downward management (earning technical respect, strengthening the team, coaching, protecting, performance review, org design), then upward, outward, and self-management (managing your boss, peers, other departments, your own time, priorities, and style). - **Late (~65%–85%)**: The two "soft" levers that make management succeed — motivation (Maslow, McGregor, Herzberg, plus programmer-specific motivators like changing the world, learning, tools, recognition) and culture (respect, innovation, standards, delivery, communication, fairness, empowerment, passion, customer focus). - **Ending (~85%–100%)**: Returns to delivery — defining the project, bottom-up estimating, planning and executing, design reviews, milestones, the endgame, shipping, celebrating, and retrospecting. Closes with downloadable tools: checklists, templates, and reports. 【Key Takeaways】 - **Programmers are individuals first, categories second** (Early): the book's taxonomy of roles and personality types exists to enable differentiated management, not labeling. Treating all programmers alike is described as a serious, common mistake. - **Programming is a craft, not a pure engineering discipline** (Early): because new code often starts from a blank page and formal certification is weak, progress is hard to observe. Managers must judge status through experience, tools, and close observation rather than trusting estimates alone. - **Hiring is a continuous process, not an event** (Early): the recruitment chapter covers job descriptions, budgets, referrals, résumé screening, interviews, offers, and follow-up — with the explicit claim that this chapter can be used standalone as a working manual. - **Onboarding determines whether hiring pays off** (Early): the authors stress that the manager's recruiting role does not end at "offer accepted"; the first day and early integration are where new hires are won or lost. - **Management has four directions** (Middle): downward (your team), upward (your boss and beyond), outward (peers, other departments, external partners), and self-management. Neglecting any one of them undermines the others. - **Motivation and hygiene factors are not the same thing** (Late): drawing on Herzberg, the book separates dissatisfaction-avoiders (respect, fair policy, working conditions) from true motivators (impact, growth, tools, recognition) — and notes there is no universal motivational trick. - **Culture is a manager's deliberate creation** (Late): even inside a poor corporate culture, a manager can build a successful development subculture around respect, standards, delivery, communication, fairness, and customer focus. - **Delivery is the final test of management** (Ending): the closing chapter reframes the manager's role in shipping — clear requirements, team-driven estimation, agreed milestones, a defined "done," and a disciplined endgame — as distinct from generic project management. 【Reading Tips】 - If you are hiring now, read Chapter 3 (recruiting) and Chapter 4 (onboarding) first — the authors designed them to be usable independently, and the accompanying tools are downloadable. - Deep-read Chapters 5–8 if you are already managing: this is where the book's real value lies, especially the motivation and culture material that technical managers typically underweight. - Skim the programmer taxonomy in Chapters 1–2 if you already know your team well; return to it when you need to diagnose a mismatch between a person and a task. - Treat the shaded "rules of thumb and quotations" sections as a reference to revisit before difficult conversations — the authors intend them as language you can borrow. - Keep the tools appendix (checklists, job descriptions, review templates) open while reading; the book is meant to be used, not just read. 【Coverage Limits】 This guide is based on stratified excerpts covering the table of contents, front matter, translator's preface, author preface, and portions of the early and middle chapters. Later chapters (especially the detailed delivery practices in Chapter 9 and the full tool set) are only summarized at the level of their headings, so specific techniques, examples, and templates from those sections are not covered here.