購入オプション

紙の本の価格：	￥2,399
割引:	￥ 1,303 (54%)

Kindle 価格:	￥1,096 (税込)
獲得ポイント:	11ポイント (1%)

ご購入時にプロモーションが適用されます

プロモーションコードまたはギフトカードを入力してください

[John Ousterhout]のA Philosophy of Software Design (English Edition)

著者をフォロー

John K. Ousterhout

A Philosophy of Software Design (English Edition) Kindle版

英語版 John Ousterhout (著) 形式: Kindle版

485個の評価

すべての形式と版を表示

価格

新品

中古品

Kindle版 (電子書籍)

"もう一度試してください。"

￥1,096

—

ペーパーバック

"もう一度試してください。"

￥2,399

￥1,952

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 and cheaply.

本の長さ

192ページ
言語

英語
発売日

2019/1/22
ファイルサイズ

1312 KB
Page Flip

有効
Word Wise

有効にされていません
タイプセッティングの改善

有効
すべての詳細を表示

販売： Amazon Services International, Inc.

【買取サービス】 Amazonアカウントを使用して簡単お申し込み。売りたいと思った時に、宅配買取もしくは出張買取を選択してご利用いただけます。今すぐチェック。

この商品を見た後に買っているのは？

ページ: 1 / 1 最初に戻るページ: 1 / 1

Nicole Forsgren Ph.D.
29
Kindle版
￥2,772
28pt (1%)

登録情報

ASIN ‏ : ‎ B07N1XLQ7D
出版社 ‏ : ‎ Yaknyam Press, Palo Alto, CA; 第1版 (2019/1/22)
発売日 ‏ : ‎ 2019/1/22
言語 ‏ : ‎ 英語
ファイルサイズ ‏ : ‎ 1312 KB
Text-to-Speech（テキスト読み上げ機能） ‏ : ‎ 有効
X-Ray ‏ : ‎ 有効にされていません
Word Wise ‏ : ‎ 有効にされていません
本の長さ ‏ : ‎ 192ページ

Amazon 売れ筋ランキング: - 9,561位洋書 (の売れ筋ランキングを見る洋書)
- - 76位Programming (Kindleストア)
- - 171位Computer Programming

カスタマーレビュー:
485個の評価

この商品をチェックした人はこんな商品もチェックしています

ページ: 1 / 1 最初に戻るページ: 1 / 1

カスタマーレビュー

星5つ		67%
星4つ		20%
星3つ		8%
星2つ		2%
星1つ		3%

評価はどのように計算されますか?

この商品をレビュー

カスタマーレビューを書く

他の国からのトップレビュー

すべてのレビューを日本語に翻訳

Bruno

Excellent guide for the seasoned developer or architect.

2018年8月13日に英国でレビュー済み

Amazonで購入

The author is not afraid to go against the common idioms of "good design" and he defines a new way to look at problem decomposition and abstractions. The way developers get thought to design systems in conjunction with software development trends too often leads to creating over-complicated software. Any software which is too complex to maintain will eventually be rewritten. The author explains a different approach on how to decompose problems and he defines a methodology to achieve optimal results over time. It also provides a list of red flags which, when found in a software project, enables the developer to timely recognize and correct design issues before they go out of hands.
I'd recommend this book to the seasoned developer or software architect who has already seen a number of projects and designed a few systems. Which such experience the reader will quickly recognize many of the bad ways to design a system and the type of problems which bad design leads to.

13人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

johnavon

How to design good software

2019年3月5日に英国でレビュー済み

Amazonで購入

This is an excellent book by an author who clearly understands software design.

He gives an excellent set of principles for software design. He carefully explains how he's come to this conclusion after many years of software development, and he gives alternative approaches explaining the trade-off between different approaches.

The actual software examples he gives come from operating systems. I have not worked on operating systems myself, so the examples were not entirely relevant to me. However the principles he is describing make a lot of sense and are very useful.

5人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

CMacleod

Short and to-the-point

2018年9月19日に英国でレビュー済み

Amazonで購入

As an experienced software engineer, I liked this book a lot. It's short, fairly general and high-level, much of the content seems like common sense, but it's still very helpful to have it clearly set down. The author emphasises the benefits of trying to stay in Technical Credit rather than Technical Debt (without using those terms). There is also a refreshing absence of fashionable methodologies.

10人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

Faris

Finally a clean code book that justifies itself.

2021年6月9日に英国でレビュー済み

Amazonで購入

A book that falls in the same category as "clean code", except it gives better advice with actual justifications.

Unlike "clean code", this book actually tells you why a certain way is better rather than just stating it as some biblical truth. It also presents overarching theory that all the concepts sit on and with which you can take to make actually day to day decisions that aren't based on hard rules. The main concept presented is the idea of complexity, reducing the complexity that is exposed to developers by abstracting it away into parts that can be used as a black box and is seen by few.

The book is good for both junior and senior engineers and will make you rethink how you and your team work, in particular constantly improving the code base rather than just looking to address tech debt at some future point in time. At the very least you will come out with a different opinion on some topics, refreshed some good practices, and learn good terminology to describe difficult concepts.

People who complain that this book encourages long functions and classes really miss the point. The point is that functions and classes should do one thing in isolation. That's the goal, not to make it short. A lot of the time functions are shorter as a result of following that objective, but you are optimizing for things doing one thing not shortness within itself. Separating functions out into blocks that do nott stand alone as independent units just makes things harder to understand and read as you have to jump about in the file, or into other files. If you look at some of the before and after examples that do this in clean code, they are actually worse a lot of the time after. If you have this opinion, when you read this book be open to changing your mind. If your argument is "functions should be 20 lines long at most because that's what I read in clean code and anything else is wrong" you are really limiting yourself and hurting the people who read your code.

It was also very refreshing to finally hear a counter argument to the dogmatic application of TDD.

To conclude, if you would like to learn how to write clean code with actual generalisable theory over using hard rules such as never comment, a function should be x lines long, and classes should be y lines long, then this is the book for you.

1人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

DK3250

You cannot disagree!

2018年11月14日に英国でレビュー済み

Amazonで購入

All in this book is right, most is said before, you cannot disagree.
However, the book is not particular specific as to how to obtain software design with low complexity. It is high level guidance; it is left to the reader to make it into practical work. Too much theory, too few examples.

7人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

すべてのレビューを参照します

Amazon Advertising 商品の露出でお客様の関心と反応を引き出す	Audible（オーディブル）本は、聴こう。最初の1冊は無料	アマゾンウェブサービス（AWS）クラウドコンピューティングサービス	Amazonアウトレット訳あり商品をお手頃価格で販売	Amazonビジネス（法人購買）請求書払い法人価格・数量割引

AmazonGlobal 65か国/地域以上への海外配送がより簡単に	Book Depository 送料無料で世界中にお届け	Shopbop 世界中の厳選されたファッションアイテム	Amazon Second Chance 譲ったり、下取りに出したりして有効活用。

購入オプション

著者をフォロー

おすすめの著者

A Philosophy of Software Design (English Edition) Kindle版

この商品を見た後に買っているのは？

登録情報

この商品をチェックした人はこんな商品もチェックしています

カスタマーレビュー

この商品をレビュー

上位レビュー、対象国：日本

他の国からのトップレビュー

購入オプション

著者をフォロー

おすすめの著者

A Philosophy of Software Design (English Edition) Kindle版

この商品を見た後に買っているのは？

登録情報

この商品をチェックした人はこんな商品もチェックしています

カスタマーレビュー

この商品をレビュー

上位レビュー、対象国： 日本

他の国からのトップレビュー

上位レビュー、対象国：日本