按年被提到
20212022 · 15 次2026
开源书›软件工程·No.74·简称 SWE Book

Software Engineering at Google

Google 软件工程
Titus Winters, Tom Manshreck, Hyrum Wright

Google 总结的软件工程原则:文化、流程与工具

免费阅读 ↗
被推荐 · 39 人首次 2021-04-23 · 最近 2026-07-03许可证 CC BY-NC-ND 4.0
39不同的人
28活跃月份
10有推荐的月份
41讨论串

由 Google 的工程师撰写,讲一家大公司怎样让软件项目在很长时间里保持可维护:分为文化、流程和工具三部分,涉及测试、代码审查、依赖管理、大规模变更、弃用等主题。内容以原则和实践说明为主,不是技术教程。和一般的工程方法书相比,它的特点是来自超大规模代码库的实际经验,不一定适合小团队照搬。

HN 为什么推荐它

HN 上的人在讨论测试、弃用、大规模变更、代码审查和复杂度时常引用它,称其中的原则和第一章很有启发;一些人指出书偏大公司情境,非技术性较强。

难度 3 / 5约 20 小时开放许可
适合谁

做长期项目的工程师和技术负责人

读之前最好知道
1团队开发经验
2版本控制与代码审查基础

怎么读

由 Claude 根据这本书和 HN 上的说法整理,可能有错
  1. 1先读第一章,了解全书对时间和规模的基本看法
  2. 2按自己遇到的问题挑章节读,比如测试或大规模变更
  3. 3读时区分哪些适合自己团队的规模,不要照搬
  4. 4与自己所在团队的流程对照着读

HN 书评

推荐在前,同类按时间 · 每本最多保留 20 条,统计用全部提及 · 作者本人贴的不算
推荐zuj · 2021-12

“SWE book puts it really well. Software Engineering at Google”

说这本书把聪明代码为何是负担讲得很好
Writing maintainable code is a communication skill原评论 ↗
推荐credit_guy · 2022-01

“read the chapter on deprecation (15) in the book Software Engineering at Google [1]”

推荐读第 15 章 deprecation
Chesterton’s Fence (2020)原评论 ↗
推荐jupp0r · 2022-02

““Software Engineering at Google” has been eye opening for me. It hits what you are looking for in its first chapter and then goes into details of different aspects in later chapters.”

称它让人大开眼界,首章切题,后面展开各方面细节
Ask HN: Best books on managing software complexity?原评论 ↗
推荐qbasic_forever · 2022-04

“you can glean a ton of info about how Google services work internally from its software processes: Software Engineering at Google”

称从 Google 的软件流程能看出内部服务如何运作
Ask HN: Where can I see many examples of real companies' software architecture?原评论 ↗
推荐tremguy · 2022-11

“See "Software Engineering at Google" Software Engineering at Google, the definition of a "small test".”

引书中对 small test 的定义
Multiple assertions are fine in a unit test原评论 ↗
推荐tonto · 2022-12

“"Software engineering at Google" (O'Reilley) has a lot of "team focused" advice also, it's overall pretty non-technical but generally a good read. Free to read online too Software Engineering at Google”

推荐,称含不少面向团队的建议,偏非技术,可免费在线读
Ask HN: Reading material on how to be a better software engineer?原评论 ↗
看全部 20 条 →
推荐kaczordon · 2023-02

“See this book from software engineers at Google, it talks about various test doubles: Software Engineering at Google”

推荐它讲各种 test double
Testing Without Mocks原评论 ↗
推荐cbhl · 2023-06

“If they find the appeal to authority useful, I'd grab them a copy of _Software Engineering at Google_ and leave them a bookmark in "Help Me Hide My Code".”

建议送一本,并在“Help Me Hide My Code”处夹书签
Speed matters: Why working quickly is more important than it seems原评论 ↗
推荐seanwilson · 2025-02

“Software Engineering at Google is probably relevant for large projects: Software Engineering at Google”

认为它可能适用于大型项目
Clean Code vs. A Philosophy Of Software Design原评论 ↗
推荐svat · 2025-12

“you may want to read the chapter on “Large-Scale Changes” in the “Software Engineering at Google” book: Software Engineering at Google”

建议读“Large-Scale Changes”一章
Patterns for Defensive Programming in Rust原评论 ↗
引用vitus · 2021-06

“I've read through about... half of it; at least from my perspective (as a current software engineer at Google with experience with most of the systems / processes outlined in the book), a lot of it is philosophical about the "why" of software engineering.”

说读了约一半,认为很多内容是软件工程“为什么”的哲学
Ask HN: Good books/courses to learn networking essentials for web developers?原评论 ↗
引用allanrbo · 2022-01

“Exactly this approach is discussed in the Hyrum's Law chapter near the beginning of the SWE book:-)”

指出书开头 Hyrum's Law 一章讨论过这种做法
Hyrum's Law原评论 ↗
引用geofft · 2022-01

“Forgot the reference! [1] Software Engineering at Google Software Engineering At Google: Lessons Learned from Programming Over Time”

补上出处,引这本书
Worst practices should be hard (2016)原评论 ↗
引用Nzen · 2022-05

“In the last three hours [0], they removed it from their git repository, and replaced it with separate html pages [1].”

说书的内容刚从 git 仓库移除,改成单独的 HTML 页面
Software Engineering at Google (2020) [pdf]原评论 ↗
引用mtlynch · 2022-06

“The best code review tool I've ever used was a tool at Google called Critique.[0]”

说 Google 的 Critique 是用过最好的 code review 工具
Show HN: Crocodile - Better code review for GitHub原评论 ↗
引用troelsSteegin · 2022-09

“This is from the "Software Engineering at Google" book, Software Engineering at Google”

指出某内容出自这本书
Selecting Meaningful Metrics with Goals and Signals原评论 ↗
引用marcyb5st · 2022-10

“After using Critique [1] internally at Google all the other tools/implementations/UIs feel very confusing.”

说用过 Google 内部的 Critique 后,其他工具都显得混乱
Code Review Handbook原评论 ↗
引用phyrex · 2022-12

“Well in the book that actually has that content (and very nearly that title: Software Engineering at Google) they explain that they set themselves up to follow the best practices”

说书里解释了他们如何遵循最佳实践
The rise and fall of peer review原评论 ↗
引用gravypod · 2023-06

“[1] - Software Engineering at Google”

把它列为脚注里的参考来源
Ask HN: What are some of the most elegant codebases in your favorite language?原评论 ↗
引用lapcat · 2023-08

“It's just a separator page. Each of the parts is like that: Software Engineering at Google”

说它的各部分都是这样的分隔页
Software Engineering at Google原评论 ↗