“it has recently been very nicely documented [1]”
Software Engineering at Google
梳理 Google 软件工程关键实践的简短清单
对 Google 的关键软件工程实践做了编目和描述。输入中仅有这一句摘要,评论提到的内容包括:绝大部分代码存放在单一的统一仓库、所有开发者可访问;在主干上开发;多数软件每隔几年就会被重写(第 2.11 节),以及设计文档等做法。
评论者把它当作 Google 单一代码仓库、主干开发等工程实践的权威出处,尤其反复引用其中大部分软件每隔几年就会重写这一点来讨论大公司工程方式能否照搬。
HN 书评
推荐在前,同类按时间 · 每篇最多保留 20 条,统计用全部提及“which is a great article that goes into the monorepo argument as well as a lot of other cool practices.”
“For a brief overview of how software engineering is done at Google, see my paper”
“Most software at Google gets rewritten every few years.”
“also they do all the development in one branch / in the trunk Software Engineering at Google”
“Also, "Software Engineering at Google"”
看全部 12 条 →
“Most of Google's code is stored in a single unified source-code repository, and is accessible to all software engineers at Google”
“This only works at Google because most of the code is rewritten every few years [1].”
“From the bottom of page 11: Most software at Google gets rewritten every few years”
“Most software at Google gets rewritten every few years.”
“Note that Google's "Frequent rewrites" practice -- see section 2.11 of Software Engineering at Google -- substantially reduces the severity of this problem (though it requires a good higher-level architecture).”
“Google rewrites a lot of their software components from scratch every few years, at least according to section 2.11 of this paper”
- Software Engineering at Google ↗asnt · 2017-02-10 · 442 分
- Software Engineering at Google (2017) ↗weinzierl · 2019-01-03 · 685 分
- Software Engineering at Google ↗pavanyara · 2020-11-09 · 4 分
- Software Engineering at Google [pdf] ↗dhairya · 2021-05-06 · 6 分