Contributors 217
programming to undergraduate students for nine years and is a coauthor of the
textbook Python for Rookies (Cengage Learning Business Press).
“Take Advantage of Code Analysis Tools,” page 158Scott Meyers
Scott Meyers is an author, trainer, speaker, and consultant with
over three decades of experience in software development prac-
tice and research. He’s authored dozens of journal and magazine
articles, as well as the books Effective C++, More Effective C++,
and Effective STL (all Addison-Wesley Professional). He also designed and
oversaw their electronic publication in HTML and PDF forms. Scott is con-
sulting editor for Addison-Wesley’s Effective Software Development series and
was an inaugural member of the advisory board for the online journal, The
C++ Source (http://www.artima.com/cppsource). He received his PhD in com-
puter science from Brown University. His website is http://www.aristeia.com/.
“Make Interfaces Easy to Use Correctly and Hard to Use Incorrectly,” page 110Seb Rose
Seb Rose is a principal software engineer working on the Rational
DOORS team in Edinburgh. He first worked as a programmer in
1980 writing applications for estate agents and solicitors in com-
piled BASIC on an Apple IIe. Upon graduating from Edinburgh
University in 1987, he worked on the REKURSIV project before becoming a
freelance contractor. Today, his primary software interests are agile practices
and the resuscitation of legacy code.
“Act with Prudence,” page 2Steve Berczuk
Steve Berczuk is a software engineer at Humedica, where he
develops business intelligence solutions for the healthcare indus-
try. He has been developing software applications for over 20
years, and is the author of Software Configuration Management
Patterns: Effective Teamwork, Practical Integration (Addison-Wesley Profes-
sional). In addition to developing software, he enjoys helping teams deliver more
effectively through the use of agile methods and software configuration manage-
ment. His website is http://www.berczuk.com.
“Deploy Early and Often,” page 40
“Own (and Refactor) the Build,” page 126