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
##模塊劃分是一門藝術。這不是一本講述瞭嚴格規則的書,每個人看過之後可能都會有所得,但能拿走多少就看個人悟性。你可以不同意這本書的很多理念,但不能否認它的啓發性。
評分 評分##神書,開發人員必讀書籍,尤其是前半本,字字珠璣。9.5 Read on my blog: [https://linghao.io/notes/a-philosophy-of-software-design] [A Philosophy of Software Design] is a short yet to-the-point book on high level ideas on how to design a software system with less complexity. It’s a book I would recommend to eve...
評分##1. complexity is incremental:you have to sweat the small stuff 2. working code isn’t enough 3. make continual small investments to improve system design 4. interfaces should be designed to make the most common usage as soon as possible 5.module should be d...
評分寫好代碼的最佳標準就是降低復雜性。解決復雜性的時候需要引入一些投資理念,很多看起來提高復雜性的方法長遠來看反而降低瞭復雜性。比如作者推崇閤理的代碼注釋,甚至先寫注釋再寫代碼,這樣可以更閤理地設計整個項目的瞭邏輯,降低總體風險。
評分 評分 評分本站所有內容均為互聯網搜尋引擎提供的公開搜索信息,本站不存儲任何數據與內容,任何內容與數據均與本站無關,如有需要請聯繫相關搜索引擎包括但不限於百度,google,bing,sogou 等
© 2025 book.coffeedeals.club All Rights Reserved. 靜流書站 版權所有