Title: Professional Software Development

Review Date, Jan 2004
Author: Steve McConnell
Pub: Addison Wesley
ISBN: 0-321-19367-9
COST: - 29.99 USD
DISK/CD N/A
Cover: soft
Pages :240
Keywords: software development, professional development, systems, process
Recommendation: Recommended for US readers only
Source: - ACCU

I looked at this book with some enthusiasm as I had just written a piece on similar lines for an Embedded Systems Engineering magazine. (see the ESE columns on the ESE web site or my own www.phaedsys.org). This book looks at what makes a software engineer, personality types, the way we work, and the authors own “pilgrims progress” of how he moved from being a interested in programming though to wanting licensed software professionals. It is fascinating and raises many points.

 

Rather than a book on project management or code development, which is does mention in passing, this looks at the philosophy, ethics and practicalities of being a software engineer. It looks at working practices, including stock options, overtime and free t-shirts. Engineering, art, bridge building and software are all linked with contrasts in their professions and discipline. All thought provoking stuff.

 

A large part of the book, perhaps half, looks at licensing professional engineer and sets out how this could be done in the US. It covers qualifications, experience, training and industry exams in fact virtually everything that BCS or IEE membership and Chartered Engineer requires. The author mentions every US body but chose not to mention the IEE, BCS or the C.Eng in the book although he does know about them and looked at the prior to writing this book.

 

Whilst the book is well done and well thought out it’s total US centric view that re-invents the wheel and ignores all the current systems in Europe makes it highly recommended for US readers but of little use for any one else. In fact it could be misleading for European readers who may not realise that there is already a UK and European wide professional Engineer (and Professional Software Engineer) system that has been running for some decades. This is a pity as I fully support the reasoning and the thrust of the book.

 

So I can only recommend this book for US readers. In fact I would suggest that it is essential for all US programmers or software Engineers. UK/European based programmers can get the same information by joining the IEE or BCS.