marksutherland reviewed Driving technical change by Terrence Ryan (Pragmatic programmers)
Review of 'Driving technical change' on 'Goodreads'
2 stars
This book outlines a rather adversarial approach to promoting technologies and solutions in a technical workplace. It follows a 'design patterns' format split into three sections: the first outlines various stereotypes that might be encountered (e.g. cynics, the uninformed), the second looks at tactics for advancing your agenda (e.g. doing demos, gaining expertise), and the final outlines a strategy which ties these altogether.
While there are some useful insights, and some value to the patterns that have been identified, there's a complete lack of depth and nothing close to qualitative data. The material is so light that it's a worryingly quick read which is frustrating as their are the seeds of a more useful piece of work scattered throughout the text.
One of the biggest issues with the book is that it makes the assumption that you are right about the solution to your perceived problem. While there is a …
This book outlines a rather adversarial approach to promoting technologies and solutions in a technical workplace. It follows a 'design patterns' format split into three sections: the first outlines various stereotypes that might be encountered (e.g. cynics, the uninformed), the second looks at tactics for advancing your agenda (e.g. doing demos, gaining expertise), and the final outlines a strategy which ties these altogether.
While there are some useful insights, and some value to the patterns that have been identified, there's a complete lack of depth and nothing close to qualitative data. The material is so light that it's a worryingly quick read which is frustrating as their are the seeds of a more useful piece of work scattered throughout the text.
One of the biggest issues with the book is that it makes the assumption that you are right about the solution to your perceived problem. While there is a chapter that encourages the reader to be diligent in their research and to avoid zealotry, the framing of the book is that you are right, and everyone who doesn't immediately agree needs to be dealt with (with the alarming exception of those that are deemed 'irrational' who should simply be ignored). As a result the focus of the book is on tactics for persuading people to take your approach, where the reasons for their opposition are generally dismissed. Occasionally the authors makes allusion to the notion that they may have something valid to contribute, but it is always an afterthought.
This may seem like an odd complaint, that the book focuses too much on helping you achieve the end you have in mind as this seems to main goal of the book. However I can't help but think this book plays too neatly into the myth of the long genius super developer who is just misunderstood and needs to save the dullards who only work the hours they are contracted for from themselves. This is explicitly referred to in at least one place, and there seems to be an assumption that the reader must fit into this mold. As a result, it would seem more prudent to encourage the reader to take a more collaborative approach, listening to their colleagues concerns and critiques and synthesizing the best solution for all. There are concessions in this direction throughout the book, but they always feel like exceptions from the core message of the book.
As a result, this book probably works best as a modern day Machiavelli for the tech industry, with all of the inherent problems that brings. Ultimately it's not the book I hoped it would be, but the one I feared it would. I fear many will read this and find a system that will help them bulldoze their way to the solution that appeals most to their whims. Perhaps it's best read in order to recognize what others may be trying to do.
