-19% ¥4,147¥4,147 税込
ポイント: 41pt
(1%)
配送料 ¥257 6月9日-20日にお届け
発送元: SuperBookDeals_ 販売者: SuperBookDeals_
¥1,837¥1,837 税込
発送元: Amazon 販売者: 古本専門SDRアマゾン店
無料のKindleアプリをダウンロードして、スマートフォン、タブレット、またはコンピューターで今すぐKindle本を読むことができます。Kindleデバイスは必要ありません。
ウェブ版Kindleなら、お使いのブラウザですぐにお読みいただけます。
携帯電話のカメラを使用する - 以下のコードをスキャンし、Kindleアプリをダウンロードしてください。
OK
Ship it!: A Practical Guide to Successful Software Projects (Pragmatic Programmers) ペーパーバック – 2005/6/11
購入オプションとあわせ買い
Ship It! is a collection of tips that show the tools andtechniques a successful project team has to use, and how to use themwell. You'll get quick, easy-to-follow advice on modernpractices: which to use, and when they should be applied. This bookavoids current fashion trends and marketing hype; instead, readersfind page after page of solid advice, all tried and tested in thereal world.
Aimed at beginning to intermediate programmers, Ship It! will show you:
- Which tools help, and which don't
- How to keep a project moving
- Approaches to scheduling that work
- How to build developers as well as product
- What's normal on a project, and what's not
- How to manage managers, end-users and sponsors
- Danger signs and how to fix them
Few of the ideas presented here are controversial or extreme; most experiencedprogrammers will agree that this stuff works. Yet 50 to 70 percent of allproject teams in the U.S. aren't able to use even these simple, well-acceptedpractices effectively. This book will help you get started.
Ship It! begins by introducing the common technicalinfrastructure that every project needs to get the job done. Readerscan choose from a variety of recommended technologies according totheir skills and budgets. The next sections outline the necessarysteps to get software out the door reliably, using well-accepted,easy-to-adopt, best-of-breed practices that really work.
Finally, and most importantly, Ship It! presents commonproblems that teams face, then offers real-world advice on how tosolve them.
- 本の長さ208ページ
- 言語英語
- 出版社Pragmatic Bookshelf
- 発売日2005/6/11
- 寸法19.05 x 2.11 x 23.5 cm
- ISBN-109780974514048
- ISBN-13978-0974514048
商品の説明
レビュー
""It's rare to have this much fun reading a book about software. The ideas are smart, relevant, and fundamental. I can be a better programmer today because of the things I read today.""--Joe, Fair Developer
""A great book! The authors have done a great job in presenting the subject in a neutral way and avoiding any methodology-oriented traps.""--Roberto Gianassi, IT Consultant
""This is fantastic stuff. As I started reading, I almost fell out of my seat because the project I'm on right now is going through exactly the hurt you describe and would benefit greatly from material just like this.""--Matthew Bass, Software Engineer
著者について
登録情報
- ASIN : 0974514047
- 出版社 : Pragmatic Bookshelf; 第1版 (2005/6/11)
- 発売日 : 2005/6/11
- 言語 : 英語
- ペーパーバック : 208ページ
- ISBN-10 : 9780974514048
- ISBN-13 : 978-0974514048
- 寸法 : 19.05 x 2.11 x 23.5 cm
- カスタマーレビュー:
著者について
著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう
他の国からのトップレビュー
The list of critical practices are well defined and each one is simple enough to implement. It makes you feel like maybe you could do it. Most important, it explains why you should do it - in compelling terms so that even if you are skeptical of "continuous integration" or "pair programming" or "unit tests", well, you won't be after you read this book.
"Tracer Bullet" development isn't another methodology, but a way of incrementally developing a project so that the status is more clear to the customer and so that you can quickly turn abstract ideas that the team has into something more concrete to react to. In doing so, you maintain an integrated view of the product you are working on and help people understand their ideas more quickly. It is priceless for any non-trival software. Most of us probably have learned to do this anyway, but now there is a name for it and a guide to understand why we do what we learned through trial and error.
Had it been one of my first project management books I would have rated it higher.
If you are a student or just a beginner trying to understand how real-world software is made, you should read it.
For me, it was just a waste of time and 20 bucks.
If you and your team already are using source management, doing code reviews, and writing tests that you frequently use (chances are you probably follow most if not all of the best practices in the book) and if you have read more generic time/project management books many of the management tips probably will not be new either. If your development process is not a well oiled automated machine or perhaps struggle with team communication you will find the book very helpful and enjoyable readable.
Despite being familiar with most of the items put forth in the book, I especially enjoyed the trace bullet development chapter. That method of development struck a good balance between planning out the software and completing it in stages concurrently rather than focusing a teams effort only on one interface/module at a time.
While I was familiar with most of the content and practices of the book I would still highly recommend it for both developers and managers (actually anyone who works at a software company could probably benefit from reading it).