新品:
￥13,616 税込
ポイント: 408pt  (3%)
無料お届け日: 5月2日 - 13日
発送元: Robinストア
販売者: Robinストア
ポイント: 408pt  (3%)  詳細はこちら
無料配送 5月2日-13日にお届け
詳細を見る
残り10点 ご注文はお早めに 在庫状況について
￥￥13,616 () 選択したオプションを含めます。 最初の月の支払いと選択されたオプションが含まれています。 詳細
価格
小計
￥￥13,616
小計
初期支払いの内訳
レジで表示される配送料、配送日、注文合計 (税込)。
出荷元
Robinストア
出荷元
Robinストア
販売元
Robinストア
（28件の評価）
販売元
Robinストア
（28件の評価）
支払い方法
お客様情報を保護しています
お客様情報を保護しています
Amazonはお客様のセキュリティとプライバシーの保護に全力で取り組んでいます。Amazonの支払いセキュリティシステムは、送信中にお客様の情報を暗号化します。お客様のクレジットカード情報を出品者と共有することはありません。また、お客様の情報を他者に販売することはありません。 詳細はこちら
支払い方法
お客様情報を保護しています
Amazonはお客様のセキュリティとプライバシーの保護に全力で取り組んでいます。Amazonの支払いセキュリティシステムは、送信中にお客様の情報を暗号化します。お客様のクレジットカード情報を出品者と共有することはありません。また、お客様の情報を他者に販売することはありません。 詳細はこちら
配送料 ¥240 4月24日-26日にお届け（21 時間 57 分以内にご注文の場合）
詳細を見る
中古商品: 非常に良い | 詳細
発売元 バリューブックス　　　【防水梱包で、丁寧に発送します】
コンディション: 中古商品: 非常に良い
コメント: ◆◆◆非常にきれいな状態です。中古商品のため使用感等ある場合がございますが、品質には十分注意して発送いたします。 【毎日発送】
新品＆中古品 (18)件の出品：
￥2,712  + ￥350 配送料
Kindleアプリのロゴ画像

無料のKindleアプリをダウンロードして、スマートフォン、タブレット、またはコンピューターで今すぐKindle本を読むことができます。Kindleデバイスは必要ありません。

ウェブ版Kindleなら、お使いのブラウザですぐにお読みいただけます。

携帯電話のカメラを使用する - 以下のコードをスキャンし、Kindleアプリをダウンロードしてください。

KindleアプリをダウンロードするためのQRコード

著者をフォローする

すべてを表示
平澤 章
フォロー
ケント・ベック
フォロー
何か問題が発生しました。後で再度リクエストしてください。

Refactoring: Improving the Design of Existing Code (Addison-wesley Object Technology Series) ハードカバー – 1999/6/28

4.6 5つ星のうち4.6 366個の評価
すべての形式と版を表示

この商品には新版があります:

Refactoring: Improving the Design of Existing Code (Addison-Wesley Signature Series (Fowler))
Refactoring: Improving the Design of Existing Code (Addison-Wesley Signature Series (Fowler))
￥9,133
(997)
通常2～3日以内に発送します。
{"desktop_buybox_group_1":[{"displayPrice":"￥13,616","priceAmount":13616.00,"currencySymbol":"￥","integerValue":"13,616","decimalSeparator":null,"fractionalValue":null,"symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"ioZSlJQ1ay5jkLMjuae0L03MuTZSKMTjGehsVIZDSt3KgBrwIiF4mLfEysEXYYtD08wu4BqsgiCOLFfIbdUYuAjchT0ISjNCNFgQiLX4fw%2BnVmDH0rwkQF%2F4eXVG4Nl5UInn6v1O9zNDWd5YK8q3YFyIkuH8Ng3mhlWaKmUEMKMSnewr0QRDHCcF9E9dK%2FBW","locale":"ja-JP","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}, {"displayPrice":"￥2,822","priceAmount":2822.00,"currencySymbol":"￥","integerValue":"2,822","decimalSeparator":null,"fractionalValue":null,"symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"ioZSlJQ1ay5jkLMjuae0L03MuTZSKMTjXtk450CVOj%2Bq1iH%2Fs%2BBRuzim%2FGXmYlXg4rMMntH067rMBq%2F8%2BW6hbLZJChM2GdXrurgIlmpJ6WercSqW9Xg2RN18x18JQ%2BFlJ4tFVWbhhNkss%2F1x9hNhUpp9pAkaP5dRYNvRkUllNjtRnUm6fDM3FQ%3D%3D","locale":"ja-JP","buyingOptionType":"USED","aapiBuyingOptionIndex":1}]}

購入オプションとあわせ買い

As the application of object technology--particularly the Java programming language--has become commonplace, a new problem has emerged to confront the software development community. Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, non-optimal applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as refactoring, these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use. . .until now. In Refactoring: Improving the Design of Existing Software, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process. With proper training a skilled system designe
Previous page
  1. 本の長さ
    464ページ
  2. 言語
    英語
  3. 出版社
    Addison-Wesley Professional
  4. 発売日
    1999/6/28
  5. 寸法
    2.54 x 19.05 x 23.5 cm
  6. ISBN-10
    0201485672
  7. ISBN-13
    978-0201485677
  8. すべての詳細を表示
Next page

商品の説明

著者について

Martin Fowler is the Chief Scientist of ThoughtWorks, an enterprise-application development and delivery company. He's been applying object-oriented techniques to enterprise software development for over a decade. He is notorious for his work on patterns, the UML, refactoring, and agile methods. Martin lives in Melrose, Massachusetts, with his wife, Cindy, and a very strange cat. His homepage is http://martinfowler.com.

Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.

John Brant and Don Roberts are the authors of the Refactoring Browser for Smalltalk, which is found at http://st-www.cs.uiuc.edu/~brant/RefactoringBrowser/. They are also consultants who have studied both the practical and theoretical aspects of refactoring for six years.

William Opdyke's doctoral research on refactoring object-oriented frameworks at the University of Illinois led to the first major publication on this topic. He is currently a Distinguished Member of Technical Staff at Lucent Technologies/Bell Laboratories.

John Brant and Don Roberts are the authors of the Refactoring Browser for Smalltalk, which is found at http://st-www.cs.uiuc.edu/~brant/RefactoringBrowser/. They are also consultants who have studied both the practical and theoretical aspects of refactoring for six years.



登録情報

  • 出版社 ‏ : ‎ Addison-Wesley Professional; 第1版 (1999/6/28)
  • 発売日 ‏ : ‎ 1999/6/28
  • 言語 ‏ : ‎ 英語
  • ハードカバー ‏ : ‎ 464ページ
  • ISBN-10 ‏ : ‎ 0201485672
  • ISBN-13 ‏ : ‎ 978-0201485677
  • 寸法 ‏ : ‎ 2.54 x 19.05 x 23.5 cm
  • カスタマーレビュー:
    4.6 5つ星のうち4.6 366個の評価

著者について

著者をフォローして、新作のアップデートや改善されたおすすめを入手してください。
前のページ
  1. 平澤 章

    平澤 章

    Brief content visible, double tap to read full content.
    Full content visible, double tap to read brief content.

    著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう

    著者ページでもっと見る
  2. ケント・ベック

    ケント・ベック

    Brief content visible, double tap to read full content.
    Full content visible, double tap to read brief content.

    著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう

    著者ページでもっと見る
  3. マーチン・ファウラー

    マーチン・ファウラー

    Brief content visible, double tap to read full content.
    Full content visible, double tap to read brief content.

    著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう

    著者ページでもっと見る
次のページ

カスタマーレビュー

星5つ中4.6つ
5つのうち4.6つ
366グローバルレーティング

この商品をレビュー

他のお客様にも意見を伝えましょう
カスタマーレビューを書く

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

Amazon Customer
5つ星のうち3.0 a must read for any software developer
2014年4月8日に日本でレビュー済み
Amazonで購入
A great book about refactoring, an absolute classic.

However, I must remove two stars because my kindle paperwhite freezed at least 10 times while reading this book. Also, why the code sample is not available for download on the author's page?!
2人のお客様がこれが役に立ったと考えています
役に立った
 レポート

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

すべてのレビューを日本語に翻訳
Lia Ghita
5つ星のうち5.0 Good quality. Extremely fast delivery
2021年11月25日にドイツでレビュー済み
Amazonで購入
The book is in very good condition. The delivery was extremely fast and via courier.
レポート
Bruno Santos de Lima
5つ星のうち5.0 Muito bom!
2018年9月4日にブラジルでレビュー済み
Amazonで購入
Livro muito bom, indico para qualquer desenvolvedor ou pesquisador que trabalhe com refatoração.
1人のお客様がこれが役に立ったと考えています
 レポート
TREX
5つ星のうち5.0 Very Readable And Highly Insightful
2019年12月22日に英国でレビュー済み
Amazonで購入
I should have read this a few years ago. Ideally just after I'd first learned Java.
Till I read this I'd always refactored on the basis of performance, reflecting a prior career in hard engineering. So if I used a block of code more than once then I extracted that block as a method. Or if I used a computed value more than once in a code unit then I used a temp variable to store that value and save repeated computation. Otherwise I usually left the code as it was.
After reading the very lucid (and honestly written) first 3 chapters I will never be so simplistic again. Fowler advises refactoring even if only to improve readability of the code. But refactoring ought to also be done with object-oriented design advantages in mind, e.g. maintainability and extendability. So long lists of class attributes or method parameters are discouraged in favour of grouping in an array or agglomerates; interface differentiation preferred to sibling class creation and so on.

Fowler explains how refactoring itself does not address performance issues - in fact the refactoring process may reduce performance a bit. Neither will refactoring eliminate performance drag due to bad system architecture: system design always remains the primary way to achieve performance. But refactoring does prepare code for final optimisation in that it breaks it into its sort of natural components which can then be analysed individually. Performance issues, like so many other effects, follow a Pareto distribution: 80-90% of the drag is attributable to 10-20% of the code components. So refactoring provides a means of getting the maximum gain in system speed with the minimum of code or algorithm changes - as well as the primary benefit of readable and reusable code.

The organisation of this book is itself commendable. After easily read intro chapters, he has catalogued all minor refactorings in several subsequent chapters using UML diagrams as well as explanations. Major refactorings are presented after this. Then some actual case studies with commercial systems are covered, software tools for refactoring are discussed and a final summing-up chapter with last tips. Inside the front cover we have a convenient index of the refactorings. And inside the back cover we have an index of code smells (code items that just seem intuitively obtuse) opposite their recommended refactoring.

Many previous reviewers of this book said this stuff is already in Gang Of Four or Josh Bloch's Effective Java. Some even opine that the book is puffed out and could use some refactoring itself. This is the just the kind of response you get from dumb people after they see a solution presented to them: it sublimely ignores the fact that those same people didn't even recognise the original problem - let alone its solution. I take my hat off to Fowler for this work. Despite its age and the primitive Java version used, the essence of this work still holds true nearly 20 years on. That alone makes it a software classic.
2人のお客様がこれが役に立ったと考えています
 レポート
Kamran Bigdely
5つ星のうち5.0 The language of this book is funny and I loved the way author(s) talks with the ...
2017年5月15日にカナダでレビュー済み
Amazonで購入
Some people say this book is not relevant anymore. To me, its obvious that it's completely relevant as of 2017. This book changed my attitude toward programming. I used to spend lots of time to design the software architecture and was too obsessed with my coding style. This approach caused me to become very unproductive and slow. Then I started reading this book and was noticed that my approach was wrong (read it to see why it is wrong to be obsessed with planning your software architecture before writing code). This book answers many of questions that I had but couldn't find the answers even on stackoverflow. The language of this book is funny and I loved the way author(s) talks with the reader. I highly recommend it especially for intermediate and advanced programmers.
1人のお客様がこれが役に立ったと考えています
 レポート
Daniel Vera Morales
5つ星のうち5.0 Una lectura obligatoria
2016年11月22日にメキシコでレビュー済み
Amazonで購入
Definitivamente muchos otros libros se inspiran en este libro para hablar de la refactorización. Sin mencionar que de este libro nació uno de los principios de los principios SOLID.
レポート