Contributors 203
Filip van Laenen
Filip van Laenen is a chief engineer at the Norwegian software com-
pany Computas AS, which supplies IT solutions to the public and the
private sector in Norway. He has over 10 years of experience in the
software industry, from being a developer in both small and large
teams to being the lead developer and compentency leader for security and soft-
ware engineering for the whole company. In his professional career, he has used a
number of programming languages, including Smalltalk, Java, Perl, Ruby, and PL/
SQL. He has a special interest in computer security and cryptography, and held the
position of chief security officer at Computas for a number of years.
Filip holds an MSc in electronics and an MSc in computer science from the
KULeuven. He comes originally from Flanders, but moved to Norway in 1997
and now lives with his family in Kolsås, near Oslo.
“Automate Your Coding Standard,” page 8Gerard Meszaros
Gerard Meszaros is an independent software development con-
sultant, coach, and trainer with 25 years’ experience building
software and nearly a decade of experience applying agile meth-
ods such as Scrum, eXtreme Programming, and Lean. He speaks
regularly at software development and testing conferences such as OOPSLA,
Agile200x, and STAR. He is the author of xUnit Test Patterns: Refactoring Test
Code (Addison-Wesley) and runs the website http://xunitpatterns.com.
“Write Tests for People,” page 190Giles Colborne
Giles Colborne has been working in usability for two decades at
British Aerospace, Institute of Physics Publishing, and Euro RSCG
group. In that time, he has spent hundreds of hours watching users
in the lab and in the field. In 2004, he cofounded cxpartners, a user-
centered design company that researches user behavior and designs user experi-
ences for clients all over the world, including Nokia, Marriott, and eBay.
He was president of the UK Usability Professionals’ Association from 2003 to
2007, and has worked with the British Standards Institute in developing stan-
dards and guidance on accessibility.
“Ask ‘What Would the User Do?’ (You Are Not the User),” page 6
“Prevent Errors,” page 132