|
|
Writing Scientific Software: A Guide to Good Style

|
List Price:
$39.99
Buy Softwares Price:
$29.63
Your Savings: $ 10.36 ( 26% )
Subject To Change Without Notice
Availability: Usually ships in 24 hours
Manufacturer: Cambridge University Press
|
Average Customer Rating:     

|
|
Binding: Paperback Dewey Decimal Number: 005.3 EAN: 9780521675956 ISBN: 0521675952 Label: Cambridge University Press Manufacturer: Cambridge University Press Number Of Items: 1 Number Of Pages: 316 Publication Date: 2006-09-18 Publisher: Cambridge University Press Studio: Cambridge University Press
|
|
|
|
|
|
Editorial Reviews:
|
The core of scientific computing is designing, writing, testing, debugging and modifying numerical software for application to a vast range of areas: from graphics, meteorology and chemistry to engineering, biology and finance. Scientists, engineers and computer scientists need to write good code, for speed, clarity, flexibility and ease of re-use. Oliveira and Stewart's style guide for numerical software points out good practices to follow, and pitfalls to avoid. By following their advice, readers will learn how to write efficient software, and how to test it for bugs, accuracy and performance. Techniques are explained with a variety of programming languages, and illustrated with two extensive design examples, one in Fortran 90 and one in C++: other examples in C, C++, Fortran 90 and Java are scattered throughout the book. This manual of scientific computing style will be an essential addition to the bookshelf and lab of everyone who writes numerical software.
|
|
|
Spotlight customer reviews:
|
Customer Rating:      Summary: not bad for an introduction Comment: I think this book is a good introduction to writing good/better scientific programs. It seems so very much is left out of courses, and people are left to their own devices in terms of learning how to write good, robust, and fast programs. This book is a mix of numerical analysis, programming techniques, and an explanation of hardware from the programmer's standpoint- all three things are necessary for writing good (and fast) scientific programs. I know how deep the rabbit hole goes in each of these areas, so I can strongly recommend this book as a good introduction into each for engineers/chemists/physicists that are learning how to write scientific programs. For more about hardware, try the 'write great code' series Write Great Code: Volume 1: Understanding the Machine. For more on numerical analysis, there are many good books, such as Scientific Computing.
This isn't a cookbook for writing the best scientific programs. Sure, there are a few examples, but the underlying principles are what to take away. Despite all my experience, I learned a few tips. I have to say, this book would be better if the authors 1) didn't plug their program at every turn, 2) sat down and narrowed the scope of the book/chapters and critically asked themselves what a given example brings to the discussion, and 3) didn't try to be experts on programming languages. Don't read too deeply into the example implementations. C is my language of choice- I can call them out on many things. I know enough fortran to raise eyebrows at some of the content. The proofreader and technical editor need to be shot- typos and blatant errors are rampant throughout the book (seriously- run spell checker before you hit the "print" button).
Customer Rating:      Summary: A top pick for college libraries. Comment: Writing Scientific Software: A Guide to Good Style provides college-level audiences studying computer technical writing with a clear guide to writing numerical software. Tips are geared to real-world challenges and scenarios and include plenty of examples, so students learn how to write efficient, workable software, test it for bugs and performance, and more. Examples are provided in Fortran 90, C++ and Java throughout and offer plenty of detail on common scenarios, pitfalls, and the elements of sold scientific software production. A top pick for college libraries.
Diane C. Donovan
California Bookwatch
|
|
|
|
|
|
|