I've been in the software development industry for over a decade, and one of the things that continues to shock and depress me is the number of developers out there that are stunningly weak on theory.
I got turned on to this book by a presentation at TechEd. According to the speaker, C# is capable of at least five different coding paradigms, only one of which is Object Oriented. In the enterprise development world, OO is viewed as the "right" way to do things, with no understanding of the tradeoffs being made by following the OO approach. Worse, object models are getting created by people that have no idea how to validate the design. What is "right" and "wrong" is decided mostly by gut feel. If you ever hear the phrase, "well, I had to do some refactoring in the classes that were inheriting from mine because the change I made broke some stuff," you know the design was bad.
When I review code, I see developers drifting in and out of the OO style, mixing in bits and pieces of Functional programming, a bit of event-driven/message-based programming, and absolutely no idea of why or how to decide which paradigm to follow in a given situation. Worse, if they know any theory at all, it's only for the OO approach. Not good when trying to use the Functional programming features in C#.
If you just thought to yourself that C# is only an OO language, then you REALLY need to read this book.
I found this book to be an excellent starting point for anyone trying to educate themselves on the appropriate use and selection of a programming paradigm. It has enough theory to get you started, and will build enough of a vocabulary to let you find more focused books.
The computer book market is flooded with how-to guides. This isn't one of them. As developers, we are pretty good at getting things done. However, that still leaves us a far cry from treating our profession as a craft, worthy of deep understanding. I suspect this may be part of the reason why 80% of software development costs occur after a product has gone to production, even in the corporate world.
Yes, this book can be hard. In fact, it can be very hard, especially for an experienced developer that is reading quickly while looking for the "how-to" bits. The book challenges you to go back to first princples, which is hardest for folks that have made a career of getting the job done and slinging code as needed. Read the book like a college text book, and it might help. Read each chapter twice. If you can get your head around it, it's worth the effort.
- 単行本: 291ページ
- 出版社: ピアソンエデュケーション (2001/12)
- 言語: 日本語
- ISBN-10: 4894712989
- ISBN-13: 978-4894712980
- 発売日： 2001/12
- 梱包サイズ: 22.8 x 18 x 2 cm
- おすすめ度： この商品の最初のレビューを書き込んでください。
-
Amazon 売れ筋ランキング:
本 - 285,358位 (本の売れ筋ランキングを見る)
- 486位 ─ 情報学・情報科学全般関連書籍
- 266位 ─ システム管理・監査
- 1454位 ─ ソフトウェア開発・言語
- 目次を見る
