Hard Code (2nd Edition) cover

Hard Code (2nd Edition)

No rating yet
Chapters
1
Series
A rare book: it does not describe "software engineering as it should be" but the pitfalls that real organizations keep stumbling into. The author spent years in development and development management at Microsoft, distilling the most controversial and most practical views from his internal column into this book: why development schedules are always absurdly optimistic, why specifications often go unfinished and unused, how quality reviews can avoid becoming mere formality, and how a strong technical contributor transitioning into management can avoid becoming "the embodiment of evil." It is divided into 10 chapters by theme, each with a brief introduction; the pieces are short and can be read as needed rather than from cover to cover. The Chinese edition, translated by Lin Feng, retains the original's teasing tone and Microsoft internal terminology and adds background notes, so readers unfamiliar with Microsoft culture can follow it. For developers, testers, project leads, or those new to managing a team, its value lies in providing a "problem checklist" to compare against and discuss—many issues you cannot raise in a meeting are already articulated in the book. If you have read Code Complete and liked its solid engineering perspective, this book can be seen as the other half of the same lineage, more focused on people and organizations.
ISBN
9787111416821

Tags

Summary

This book is a collection of the "Hard Code" column written inside Microsoft by senior development manager Eric Brechner under the pen name I. M. Wright. The Chinese edition is translated from the 2011 second English edition and is billed as a companion volume to Code Complete. It contains 91 columns organized into 10 thematic chapters, summarizing more than 90 problems that recur across software projects—often overlooked or left unfixed for long periods—from perspectives including software development process, technical methods, project management, team management, and interpersonal communication, with cause analysis and improvement suggestions for each. Chapter 1 discusses how to ensure on-time delivery by managing risk, scope, and communication; Chapter 2 introduces methods and techniques for process improvement and explains why such methods rarely work; Chapter 3 discusses strategies for eliminating inefficiency, such as specifications, meetings, and idle headcount; Chapter 4 focuses on the relationship between developers and other roles such as testing and project management; Chapter 5 focuses on software quality issues and review practices; Chapter 6 analyzes the fundamentals and complexity of software design; Chapter 7 discusses career planning and performance review; Chapter 8 analyzes communication breakdowns and corrective measures; Chapter 9 discusses how to manage well—how technical managers should behave; Chapter 10 analyzes challenges facing the software business and organizational culture. Each column opens with a concrete scenario, then dissects the root of the problem, and finally offers actionable advice; the author's language is witty and often borrows song lyrics, movie titles, and slang for headings. The book does not preach abstract theory and is suitable for readers facing real-project dilemmas such as schedule slippage, quality loss, and poor communication, as well as for team discussion.

Editor's review

这本书的难得之处,在于它不写“理想中的软件工程”,而是写真实组织里那些反复踩到的坑。作者在微软多年从事开发与开发管理,把内部专栏里最有争议、也最实用的观点整理成书:开发时间表为什么总是乐观得离谱,规范书为什么常常写不完也用不上,质量审查怎样才能不流于形式,技术骨干转型做管理者又该怎样避免变成“邪恶的化身”。 它按主题分成 10 章,每章前面有简短的导言,各篇篇幅不长,可以按需翻读,不必从头读到尾。中文版由林锋翻译,保留了原文的调侃语气和微软内部用语,并补注了背景,因此不熟悉微软文化的读者也能看懂。对于做开发、做测试、带项目或刚带团队的人来说,它的价值在于提供了一套可以拿来对照和讨论的“问题清单”——很多议题你在会上说不出口,书里已经替你说清楚了。若你读过《代码大全》并喜欢其中扎实的工程视角,这本书可以看作同一脉路上更偏“人与组织”的那一半。

Who it's for

A good fit for

  • 有 3 年以上经验、希望提升工程判断力的软件工程师
  • 刚转型或即将转型为技术管理者、项目负责人的读者
  • 软件测试、项目经理、产品等与开发密切协作的岗位
  • 喜欢用真实案例讨论团队文化与流程改进的技术团队

Not a good fit for

  • 完全没有开发经验、想系统学习编程入门知识的读者
  • 希望获得具体编程语言、框架或算法教程的人
  • 期待成体系的软件工程教材、需要严格理论框架的师生

Reading tips

  1. 可先读第 1 章与第 3 章,看看自己项目里的进度与效率问题对应哪几条。
  2. 按当前角色选读:开发者读第 4—6 章,管理者读第 8—10 章,职业困惑读第 7 章。
  3. 每读完一篇,用一句话记下自己团队里对应的现象,再与同事讨论可落地的一条改动。
  4. 书中涉及微软内部用语,遇到不熟的术语可查书末术语表,不必拘泥于原文语境。

About the publisher

China Machine Press China · Founded in 1950

In addition to science and technology and professional publishing, the books in our catalog from China Machine Press also reflect a sustained focus on psychology, computing, management, finance and economics, and social sciences. In psychology, the catalog includes works by C. G. Jung and introductions to analytical psychology, as well as applied topics such as stress and health, and addiction and healing. In computing, it features Structure and Interpretation of Computer Programs (JavaScript Edition). Management and finance titles include Administrative Behavior (4th Edition), The Price of Inequality (Collector's Edition), and This Time Is Different: Eight Centuries of Financial Folly (Commemorative Edition). In the philosophy and history of science, there is The Worldview: The Third Edition. Relevant authors include C. G. Jung, William McGuire, Sonu Shamdasani, and Gabor Maté. Public information is limited; the above summarizes the publisher's profile based solely on the books in our catalog.

Contents

  1. HZ Books Programmer's Library

FAQ

这本书讲的是编程技术还是管理?
两者都涉及,但重心在开发流程、项目与团队管理。它不教具体语言或算法,而是讨论时间表、规范书、代码审查、质量把控、沟通与绩效等工程实践问题,因此开发者和管理者都能读。
没有微软工作背景能读懂吗?
能。作者写作时已对微软内部术语做了注解和修改,中文版也保留了这些注释,并附有术语表;书中很多问题在各类软件团队中普遍存在,不依赖微软背景即可理解。
和《代码大全》是什么关系?
中文版宣传上称其为《代码大全》的姊妹篇,两者同属软件工程实践类经典。但本书不涉及编码细节,内容来自作者在微软内部撰写的专栏结集,风格更随笔化,可按篇选读。
需要按顺序从头读到尾吗?
不需要。全书 10 章按主题划分,每篇相对独立,篇幅也不长。建议按自己当下遇到的问题选读,或把每章导言先看一遍,再挑感兴趣的篇目深入。

Comments

Find this book

This site is an index: you start “Search all sources” in your browser, and the entries it lists all point to third-party sites; please judge their availability yourself.

Top rated in the same category