“SWE book puts it really well. Software Engineering at Google”
Software Engineering at Google
Google 总结的软件工程原则:文化、流程与工具
由 Google 的工程师撰写,讲一家大公司怎样让软件项目在很长时间里保持可维护:分为文化、流程和工具三部分,涉及测试、代码审查、依赖管理、大规模变更、弃用等主题。内容以原则和实践说明为主,不是技术教程。和一般的工程方法书相比,它的特点是来自超大规模代码库的实际经验,不一定适合小团队照搬。
HN 上的人在讨论测试、弃用、大规模变更、代码审查和复杂度时常引用它,称其中的原则和第一章很有启发;一些人指出书偏大公司情境,非技术性较强。
做长期项目的工程师和技术负责人
怎么读
由 Claude 根据这本书和 HN 上的说法整理,可能有错- 1先读第一章,了解全书对时间和规模的基本看法
- 2按自己遇到的问题挑章节读,比如测试或大规模变更
- 3读时区分哪些适合自己团队的规模,不要照搬
- 4与自己所在团队的流程对照着读
HN 书评
推荐在前,同类按时间 · 每本最多保留 20 条,统计用全部提及 · 作者本人贴的不算“read the chapter on deprecation (15) in the book Software Engineering at Google [1]”
““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.”
“you can glean a ton of info about how Google services work internally from its software processes: Software Engineering at Google”
“See "Software Engineering at Google" Software Engineering at Google, the definition of a "small test".”
“"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”
看全部 20 条 →
“See this book from software engineers at Google, it talks about various test doubles: Software Engineering at Google”
“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".”
“Software Engineering at Google is probably relevant for large projects: Software Engineering at Google”
“you may want to read the chapter on “Large-Scale Changes” in the “Software Engineering at Google” book: Software Engineering at Google”
“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.”
“Exactly this approach is discussed in the Hyrum's Law chapter near the beginning of the SWE book:-)”
“Forgot the reference! [1] Software Engineering at Google Software Engineering At Google: Lessons Learned from Programming Over Time”
“In the last three hours [0], they removed it from their git repository, and replaced it with separate html pages [1].”
“The best code review tool I've ever used was a tool at Google called Critique.[0]”
“This is from the "Software Engineering at Google" book, Software Engineering at Google”
“After using Critique [1] internally at Google all the other tools/implementations/UIs feel very confusing.”
“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”
“[1] - Software Engineering at Google”
“It's just a separator page. Each of the parts is like that: Software Engineering at Google”