* Page 26: How can I avoid off-by-one errors? * Page 143: Are Trojan Horse attacks for real? * Page 158: Where should I look when my application can't handle its workload? * Page 256: How can I detect memory leaks? * Page 309: How do I target my application to international markets? * Page 394: How should I name my code's identifiers? * Page 441: How can I find and improve the ...
* Page 26: How can I avoid off-by-one errors? * Page 143: Are Trojan Horse attacks for real? * Page 158: Where should I look when my application can't handle its workload? * Page 256: How can I detect memory leaks? * Page 309: How do I target my application to international markets? * Page 394: How should I name my code's identifiers? * Page 441: How can I find and improve the code coverage of my tests? Diomidis Spinellis' first book, Code Reading, showed programmers how to understand and modify key functional properties of software. Code Quality focuses on non-functional properties, demonstrating how to meet such critical requirements as reliability, security, portability, and maintainability, as well as efficiency in time and space. Spinellis draws on hundreds of examples from open source projects--such as the Apache web and application servers, the BSD Unix systems, and the HSQLDB Java database--to illustrate concepts and techniques that every professional software developer will be able to appreciate and apply immediately. Complete files for the open source code illustrated in this book are available online at: http://www.spinellis.gr/codequality/
0 有用 d0ngd0ng 2011-12-31 23:31:02
绝对好书，虽然英文不行，硬着头皮看的，不过收获也不少。
0 有用 d0ngd0ng 2011-12-31 23:31:02
绝对好书，虽然英文不行，硬着头皮看的，不过收获也不少。