軟體構築美學：當專案團隊遇上失控程式，最真實的解決方案

by Donald Belcham, Kyle Baley, 蔡煥麟 (Translator)

本書將大部分專案團隊所面臨到的既有、且難以維護及改善的應用程式，稱為棕地應用程式（Brownfield Application），它具有三項特點：既有程式碼；因差勁的實務作法而造成汙染；仍有改善或重複使用的潛力。

如何重構棕地專案？將分別從「開發環境」及「程式碼」兩大部分來探討。關於「開發環境」，將說明版本控制（version control）、持續整合（CI）、自動測試及度量，以及瑕疵追蹤的重要性和作法。而在關於「程式碼」中，則會從技術面及實務面來說明程式所應具備的可維護性、可讀性、可擴展性、可逆性。此外，書中並補充許多真實案例及挑戰既有想法，除了讓你了解現實情況，並顛覆過去已被認為是常規但不正確的程式開發觀點，期待能陪伴開發人員從更多成功與失敗的專案經驗中成長。

Genres: Programming, Coding, Software

500 pages, Paperback

First published July 28, 2009

Reviews

[Vladimir · Rating 5 out of 5]

I liked this book. Seems it's my destiny to work everywhere in brownfield projects :-) When I finished this book I'd wanted to cry: "Why I didn't read it at the start of my career!". The book describes many painful situations that we are faced while dealing with the old applications. I'd say even more, the book explains to us how we should maintain and improve brownfield projects.
Hard to realize that I've obtained it through trial and errors. But we always know important things too late, don't we?
On the whole it's a brilliant book especially for newbies who just started with a brownfield application.

[Craig Vermeer · Rating 5 out of 5]

What I love most about this book is that it paints a coherent picture of a certain style of software development that I very much agree with, and that's one that focuses on maintainable, well-factored code and in as low-friction of an environment as possible.

This is not to say that most developers don't care about writing good code, but many don't have a good picture of what that can look like or *why* they may want to change what they're doing now. I think this book can help in that regard.

[Gleb Sevruk · Rating 5 out of 5]

I've read it in one go in half of a day! It enjoyable and practical.

Some of the concept are known, but I think this is must read for every .Net developer and team player.

If you already read "Dependency Injection in .Net" and "Working Effectively with Legacy Code" and looking for next book - this is the best choice.

Only one thing is not obvious: why it is not so popular?

[Machine Reading · Rating 4 out of 5]

Good book about refactoring and basic design pattern. Donald use 'small-step' approach to fix the software contamination, which cause the software to become 'Brownfield'.

The good part of this book is source code that can download from manning site. because it's show you a 'before-after' code when you use the practice from this book and you can use that code to guide you to the present/next project that you're working.

I recommend this book for every developer (not just .NET developer) because the main part of this book is concept of design and attitude about software development, code is only use for example and teach you some refactoring/layering technique.

[Einar · Rating 3 out of 5]

I find this book hard to review. It's full of good intentions, and I certainly think all .NET developers should be aware of the topics it covers. However, if you have a few years worth of experience and you care a bit about your craft, then you're likely to have stumbled upon these things in books and blogs already. The coverage is fairly shallow, so you won't gain many new insights, I'm afraid. On the other hand, if you're fairly fresh, this book is gold. It's a good book to put on a list of mandatory reads for junior developers.

[Siim Viikman · Rating 4 out of 5]

Good book about refactoring project to a better state, all advice applies also to greenfield projects. Although, it's a good read, it is better suited for people who has less experience in the field.