……难以理解或过度抽象（带偏了方向）。如果某个东西很容易命名，那它大概率符合[在此填入任何软件开发“最佳实践”]。什么是好名字？我非常喜欢 Zachary Tellman 在《Elements of Clojure》[1]里的说法：> 名字应该精确且一致。一个*精确*的名字能明确排除它无法代表的事物。一个*一致*的名字能被熟悉上下文的人轻松理解……
…understand or overly abstracted (misdirected). If something is easy to name, it likely follows [insert any software development "best practice" here]. What's a good name? I love the phrasing from _Elements of Clojure_ by Zachary Tellman [1] > Names should be narrow and consistent. A *narrow* name clearly excludes things it cannot represent. A *consistent* name is easily understood by someone familiar with the surrounding…
……《极度负责》（Extreme Ownership）：Jocko Willink 和 Leif Babin 著（一旦你硬着头皮熬过前面那些高呼口号的劲儿，其实是本很棒的书）；《系统管理员时间管理》（Time Management for System Administrators）：O'Reilly 出品（对中断驱动型工作极其有用）；《Elements of Clojure》：Zachary Tellman 著（不只是给 Clojure 开发者看的）。
…Extreme Ownership: Jocko Willink and Leif Babin (once you get through the ho-rah stuff it's a fantastic read) - Time Management for System Administrators: O'Reilly (fantastic for interrupt driven work) - Elements of Clojure: Zachary Tellman (not just for Clojure devs)
大家有什么关于“如何以及何时建立合适的抽象”的书籍推荐吗？去年我读了 Zach Tellman 的《Elements of Clojure》，非常喜欢里面涉及抽象主题的部分。
What are people's recommendations on books on how and when to create the right abstractions? Last year I read Zach Tellman's _Elements of Clojure_ and really loved the parts that touched on the subject of abstraction.
……通过通用且设计良好的接口进行通信确实效果拔群。HTTP、Unix 管道、货币、邮件、蜜蜂……整个系统都会变得适应力强且极具包容性。Zachary Tellman 在《Elements of Clojure》的后半部分探讨了这种设计。https://elementsofclojure.com/ 回到那篇文章，我喜欢这本书的地方在于，它清晰地指出了通用性究竟应该落在何处。
…talk over a generic, well designed interface do work well. HTTP, Unix Pipes, currency, mail, bees... the whole becomes adaptive and accommodating. This kind of design is discussed in the latter half of Elements of Clojure by Zachary Tellman. https://elementsofclojure.com/ What I like about this, to come back to the article, is that it gives a clear sense of where generality should reside.
《电子学艺术》（The Art of Electronics）也在我的技术书单上。如果你对 Clojure 感兴趣，你大概率会喜欢 Zachary Tellman 的《Elements of Clojure》。它不是一本教程，更像是在尝试将地道编程实践中那些只可意会不可言传的隐性知识梳理出来。
The Art of Electronics is on my technical reading list as well. If you are into Clojure, you will probably enjoy Elements of Clojure by Zachary Tellman. It is not a tutorial, it's more like an attempt to bring tacit knowledge of idiomatic programming practices into light.
……跟算法毫无关系，完全取决于负责该项目的组织。虽然它的定位是面向新手工程师，但我觉得任何写代码的人都能从中受益。Zach Tellman 的《Elements of Clojure》是一部关于我们如何构建和组合抽象的极佳高层架构哲学书。唯一遗憾的是书名跟 Clojure 编程语言绑在了一起（书中大部分内容……
…have nothing to do with algorithms and everything to do with the organization running the project. It's marketed to new engineers, but I think anyone who writes software would get something out of it. "Elements of Clojure" by Zach Tellman is a fantastic high-level architectural philosophy about how we build and compose abstractions. Only wish that the title wasn't tied to the Clojure programming language (most of the book…
……难以理解或过度抽象（带偏了方向）。如果某个东西很容易命名，那它大概率符合[在此填入任何软件开发“最佳实践”]。什么是好名字？我非常喜欢 Zachary Tellman 在《Elements of Clojure》[1]里的说法：> 名字应该精确且一致。一个*精确*的名字能明确排除它无法代表的事物。一个*一致*的名字能被熟悉上下文的人轻松理解……
…understand or overly abstracted (misdirected). If something is easy to name, it likely follows [insert any software development "best practice" here]. What's a good name? I love the phrasing from _Elements of Clojure_ by Zachary Tellman [1] > Names should be narrow and consistent. A *narrow* name clearly excludes things it cannot represent. A *consistent* name is easily understood by someone familiar with the surrounding…
……《极度负责》（Extreme Ownership）：Jocko Willink 和 Leif Babin 著（一旦你硬着头皮熬过前面那些高呼口号的劲儿，其实是本很棒的书）；《系统管理员时间管理》（Time Management for System Administrators）：O'Reilly 出品（对中断驱动型工作极其有用）；《Elements of Clojure》：Zachary Tellman 著（不只是给 Clojure 开发者看的）。
…Extreme Ownership: Jocko Willink and Leif Babin (once you get through the ho-rah stuff it's a fantastic read) - Time Management for System Administrators: O'Reilly (fantastic for interrupt driven work) - Elements of Clojure: Zachary Tellman (not just for Clojure devs)
大家有什么关于“如何以及何时建立合适的抽象”的书籍推荐吗？去年我读了 Zach Tellman 的《Elements of Clojure》，非常喜欢里面涉及抽象主题的部分。
What are people's recommendations on books on how and when to create the right abstractions? Last year I read Zach Tellman's _Elements of Clojure_ and really loved the parts that touched on the subject of abstraction.
……通过通用且设计良好的接口进行通信确实效果拔群。HTTP、Unix 管道、货币、邮件、蜜蜂……整个系统都会变得适应力强且极具包容性。Zachary Tellman 在《Elements of Clojure》的后半部分探讨了这种设计。https://elementsofclojure.com/ 回到那篇文章，我喜欢这本书的地方在于，它清晰地指出了通用性究竟应该落在何处。
…talk over a generic, well designed interface do work well. HTTP, Unix Pipes, currency, mail, bees... the whole becomes adaptive and accommodating. This kind of design is discussed in the latter half of Elements of Clojure by Zachary Tellman. https://elementsofclojure.com/ What I like about this, to come back to the article, is that it gives a clear sense of where generality should reside.
《电子学艺术》（The Art of Electronics）也在我的技术书单上。如果你对 Clojure 感兴趣，你大概率会喜欢 Zachary Tellman 的《Elements of Clojure》。它不是一本教程，更像是在尝试将地道编程实践中那些只可意会不可言传的隐性知识梳理出来。
The Art of Electronics is on my technical reading list as well. If you are into Clojure, you will probably enjoy Elements of Clojure by Zachary Tellman. It is not a tutorial, it's more like an attempt to bring tacit knowledge of idiomatic programming practices into light.
……跟算法毫无关系，完全取决于负责该项目的组织。虽然它的定位是面向新手工程师，但我觉得任何写代码的人都能从中受益。Zach Tellman 的《Elements of Clojure》是一部关于我们如何构建和组合抽象的极佳高层架构哲学书。唯一遗憾的是书名跟 Clojure 编程语言绑在了一起（书中大部分内容……
…have nothing to do with algorithms and everything to do with the organization running the project. It's marketed to new engineers, but I think anyone who writes software would get something out of it. "Elements of Clojure" by Zach Tellman is a fantastic high-level architectural philosophy about how we build and compose abstractions. Only wish that the title wasn't tied to the Clojure programming language (most of the book…