……任何语言）- 《企业集成模式》（我在一个企业级 API 团队工作）- 《数据密集型应用系统设计》（DDIA）- 《Camel 实战》适合借阅出去的：- 《凤凰项目》- 《让工作可见》（Making Work Visible）- 《高效 DevOps》- 《程序员修炼之道》- 《REST 实战》
…any language) - Enterprise Integration Patterns (I work on an enterprise APIs team) - Designing Data-Intensive Applications - Camel in Action Good for lending out: - The Phoenix Project - Making Work Visible - Effective DevOps - The Pragmatic Programmer - REST in Practice
如果你喜欢这篇帖子，那么《让工作可见》（Making Work Visible）这本书对此类话题进行了很好的拓展。《让工作可见：暴露时间盗贼以优化工作与流动》（Making Work Visible: Exposing Time Theft to Optimize Work & Flow）https://www.amazon.com/dp/B09L3B9YK1/ref=cm_sw_r_apan_AX66TB...
If you liked this post, the book Making Work Visible is a great expansion on these topics. Making Work Visible: Exposing Time Theft to Optimize Work & Flow https://www.amazon.com/dp/B09L3B9YK1/ref=cm_sw_r_apan_AX66TB...
我最喜欢的一些关于软件项目管理和技术领导力的书：* 《技术管理之路》（The Manager's Path）——读读关于担任 Tech Lead 的那一章 * 《让工作可见》（Making Work Visible）* 《加速》（Accelerate）我的网站上有更多关于这个话题的书评：https://www.briansnotes.io/audience/tech-lead/
Some of my favorite books around managing software projects and technical leadership: * The Manager's Path - read the chapter on being a Tech Lead * Making Work Visible * Accelerate My website has more book reviews on this topic: https://www.briansnotes.io/audience/tech-lead/
……文化是怎样的，这必须在组织层面上予以采纳和尝试。来自基础设施领域的我发现很多 DevOps 和 SRE 的资源在这里非常管用；比如《加速》（Accelerate）、《团队拓扑》（Team Topologies）、《让工作可见》（Making Work Visible）等等……远程办公方面确实存在后勤协同上的问题，但归根结底这关乎信息流，以及摸索如何在团队成员和团队之间建立信任。
…cultures are, and that has to be adopted and tried at an organizational level. Coming from the infrastructure world I find a lot of the DevOps and SRE resources were useful here; Accelerate, Team Toplogies, Making Work Visible, etc... The remote aspect of it has logistical issues, but ultimately it's about information flow and figuring out how to develop trust between team-members and teams.
(also if you want a longer overview a bunch of related concepts are talked about in Dominica DeGrandis’s book Making Work Visible, and the advice on managing by the critical path method comes from a makes-my-eyes-roll-a-little-but-still-pretty-solid business novel by Eli Goldratt called Critical Chain, which applies the reasoning…
This is also where automated code quality checks can shine. You can say something like, if it's more than 5 or 10 lines we expect a ticket ID, otherwise we don't. See DeGrandis’s “Making Work Visible,” the hazard of “link to a ticket if it exists” is that sometimes this causes us to treat tickets as an external process, but we absolutely want to surface tickets that track our cleanup of tech debt…
……任何语言）- 《企业集成模式》（我在一个企业级 API 团队工作）- 《数据密集型应用系统设计》（DDIA）- 《Camel 实战》适合借阅出去的：- 《凤凰项目》- 《让工作可见》（Making Work Visible）- 《高效 DevOps》- 《程序员修炼之道》- 《REST 实战》
…any language) - Enterprise Integration Patterns (I work on an enterprise APIs team) - Designing Data-Intensive Applications - Camel in Action Good for lending out: - The Phoenix Project - Making Work Visible - Effective DevOps - The Pragmatic Programmer - REST in Practice
如果你喜欢这篇帖子，那么《让工作可见》（Making Work Visible）这本书对此类话题进行了很好的拓展。《让工作可见：暴露时间盗贼以优化工作与流动》（Making Work Visible: Exposing Time Theft to Optimize Work & Flow）https://www.amazon.com/dp/B09L3B9YK1/ref=cm_sw_r_apan_AX66TB...
If you liked this post, the book Making Work Visible is a great expansion on these topics. Making Work Visible: Exposing Time Theft to Optimize Work & Flow https://www.amazon.com/dp/B09L3B9YK1/ref=cm_sw_r_apan_AX66TB...
我最喜欢的一些关于软件项目管理和技术领导力的书：* 《技术管理之路》（The Manager's Path）——读读关于担任 Tech Lead 的那一章 * 《让工作可见》（Making Work Visible）* 《加速》（Accelerate）我的网站上有更多关于这个话题的书评：https://www.briansnotes.io/audience/tech-lead/
Some of my favorite books around managing software projects and technical leadership: * The Manager's Path - read the chapter on being a Tech Lead * Making Work Visible * Accelerate My website has more book reviews on this topic: https://www.briansnotes.io/audience/tech-lead/
……文化是怎样的，这必须在组织层面上予以采纳和尝试。来自基础设施领域的我发现很多 DevOps 和 SRE 的资源在这里非常管用；比如《加速》（Accelerate）、《团队拓扑》（Team Topologies）、《让工作可见》（Making Work Visible）等等……远程办公方面确实存在后勤协同上的问题，但归根结底这关乎信息流，以及摸索如何在团队成员和团队之间建立信任。
…cultures are, and that has to be adopted and tried at an organizational level. Coming from the infrastructure world I find a lot of the DevOps and SRE resources were useful here; Accelerate, Team Toplogies, Making Work Visible, etc... The remote aspect of it has logistical issues, but ultimately it's about information flow and figuring out how to develop trust between team-members and teams.
（另外如果你想要更详尽的综述，多米尼卡·德格兰迪斯的《让工作可见》中讨论了一堆相关概念，而关于通过关键路径法进行管理的建议则来自埃利·高德拉特一本虽然让我有点翻白眼但总体还算扎实的商业小说《关键链》，该书将推导……
(also if you want a longer overview a bunch of related concepts are talked about in Dominica DeGrandis’s book Making Work Visible, and the advice on managing by the critical path method comes from a makes-my-eyes-roll-a-little-but-still-pretty-solid business novel by Eli Goldratt called Critical Chain, which applies the reasoning…
这也是自动化代码质量检查大显身手的地方。你可以规定比如，如果超过5行或10行代码，我们就必须填一个 ticket ID，否则就不需要。参见德格兰迪斯的《让工作可见》（Making Work Visible），“如果有 ticket 就关联”的危险在于，有时这会导致我们把 ticket 当成外部流程来应付，但我们绝对希望能把追踪清理技术债的 ticket 给暴露出来……
This is also where automated code quality checks can shine. You can say something like, if it's more than 5 or 10 lines we expect a ticket ID, otherwise we don't. See DeGrandis’s “Making Work Visible,” the hazard of “link to a ticket if it exists” is that sometimes this causes us to treat tickets as an external process, but we absolutely want to surface tickets that track our cleanup of tech debt…