具体描述
John Ousterhout is the Bosack Lerner Professor of Computer Science at Stanford University. His current research focuses on new software stack layers to allow datacenter applications to take advantage of communication and storage technologies with microsecond-scale latencies. Ousterhout's prior positions include 14 years in industry, where he founded two companies (Scriptics and Electric Cloud), preceded by 14 years as Professor of Computer Science at U.C. Berkeley. He is the creator of the Tcl scripting language and is also well known for his work in distributed operating systems and storage systems. Ousterhout received a BS degree in Physics from Yale University and a PhD in Computer Science from Carnegie Mellon University. He is a member of the National Academy of Engineering and has received numerous awards, including the ACM Software System Award, the ACM Grace Murray Hopper Award, the National Science Foundation Presidential Young Investigator Award, and the U.C. Berkeley Distinguished Teaching Award.
This book addresses the topic of software design: how to decompose complex software systems into modules (such as classes and methods) that can be implemented relatively independently. The book first introduces the fundamental problem in software design, which is managing complexity. It then discusses philosophical issues about how to approach the software design process, and it presents a collection of design principles to apply during software design. The book also introduces a set of red flags that identify design problems. You can apply the ideas in this book to minimize the complexity of large software systems, so that you can write software more quickly
用户评价
##微观设计层面讲得很全面，define errors out of existence 引人深思。宏观架构层面需要参考 Design Data-Intensive Applications。
评分 评分##前半本有些观点跟我的观点不一致，但却很有启发，值五星。后半本更多的是工程角度，在别的书中见过类似观点。
评分 评分 评分##引用最后一章第一句话：This book is about one thing: complexity。虽然标题里带有"philosophy"，但其实书里介绍的大部分内容还是挺直觉。关于异常和注释的两章反而让我收获最多
评分##在线的中译本，草草的看了一遍，也没有太多code经验，所以体会不够。 1. 架构是迭代的，没有一开始就能完美的架构。 2 复杂性定义=>小的复杂性会累加。复杂性的根源，耦合，依赖？ 3 复杂性针对的是读者而不是作者，读者和使用者和维护者是一回事吗？时间久了，自己也变成了...
相关图书
本站所有内容均为互联网搜索引擎提供的公开搜索信息，本站不存储任何数据与内容，任何内容与数据均与本站无关，如有需要请联系相关搜索引擎包括但不限于百度，google,bing,sogou 等
© 2025 book.idnshop.cc All Rights Reserved. 静思书屋 版权所有