I ‘pick the brains’ of expert software developers to understand what makes them expert. I’ve spent decades studying how professional software developers reason and communicate about design and problem solving. Informed by the seminal books I’ve highlighted (among many others), my research is grounded in empirical studies of professionals in industry and draws on cognitive and social theory. Observing, talking to, and working with hundreds of professional software developers in organisations ranging from start-ups to the world’s major software companies has exposed actionable insights into the thinking that distinguishes high-performing teams.
Petroski is an eminent engineer and reflective author who provides powerful insights into engineering design.
I chose this book (among his many excellent books):
a) because it embodies a key theme that resonates throughout my own research – that success often emerges from engaging with failure; and
b) because the examples are beautifully organised and labelled, and each narrative reveals ‘the what and the why’.
Petroski writes beautifully, and he maps the connections between designerly, scientific, and engineering ideals – and the messy realities of real life.
How did a simple design error cause one of the great disasters of the 1980s - the collapse of the walkways at the Kansas City Hyatt Regency Hotel? What made the graceful and innovative Tacoma Narrows Bridge twist apart in a mild wind in 1940? How did an oversized waterlily inspire the magnificent Crystal Palace, the crowning achievement of Victorian architecture and engineering? These are some of the failures and successes that Henry Petroski, author of the acclaimed The Pencil, examines in this engaging, wonderfully literate book. More than a series of fascinating case studies, To Engineer is Human is…
In terms of conveying how to convey information (not just data) visually, Tufte is the undoubted master.
This book is full of pithy examples, with clear insights about what works, what doesn’t, and why. I came across it when I was trying to understand why I was disgruntled with so many graphical representations – and Tufte provided useful clarity about my niggles.
(N.B. I had to pick just one of his titles for this list – but I’d recommend his other books as well.)
The classic book on statistical graphics, charts, tables. Theory and practice in the design of data graphics, 250 illustrations of the best (and a few of the worst) statistical graphics, with detailed analysis of how to display data for precise, effective, quick analysis. Design of the high-resolution displays, small multiples. Editing and improving graphics. The data-ink ratio. Time-series, relational graphics, data maps, multivariate designs. Detection of graphical deception: design variation vs. data variation. Sources of deception. Aesthetics and data graphical displays. This is the second edition of The Visual Display of Quantitative Information. This edition provides excellent color reproductions of…
Nigel Cross was one of the first design researchers to express the notion of ‘designerly’ ways of thinking and knowing – “the application of scientific and other organised knowledge to practical tasks…” – as means of addressing ill-defined and ill-structured problems.
The attention to ‘messy’ problems, and to the iterative and fluid nature of the design process, is what first drew me to his work; what kept me coming back was a combination of Cross’s clarity of thought, and the way he grounds his perspectives in studies of outstanding designers and real-world examples.
In this compilation of key lectures and essays, he reflects on the nature of design and discusses what sorts of cognitive skills, strategies, and abilities effective designers bring to bear.
A revised and edited collection of key parts of Professor Cross's published work, this book offers a timeline of scholarship and research over the course of 25 years, and a resource for understanding how designers think and work. Coverage includes the nature and nurture of design ability; creative cognition in design; the natural intelligence of design; design discipline versus design science; and expertise in design.
This book is a delightful example of what happens when someone engages eyes and mind: it provides important insights into the cussedness of things people design, by looking thoughtfully at simple, ‘everyday things’.
In doing so, Norman both illustrates the constructive application of cognitive science in understanding design, and provides a compelling argument for user-centred design.
Even the smartest among us can feel inept as we fail to figure our which light switch or oven burner to turn on, or whether to push, pull, or slide a door. The fault, argues this fascinating, ingenious,even liberating,book, lies not in ourselves, but in product design that ignores the needs of users and the principles of cognitive psychology.The problems range from ambiguous and hidden controls to arbitrary relationships between controls and functions, coupled with a lack of feedback or other assistance and unreasonable demands on memorization. The book presents examples aplenty,among them, the VCR, computer, and office telephone, all…
This is the seminal book on reflection in problem-solving and design.
For me, the dominant theme is that effective design involves dynamics. One is the interplay between disciplines of knowledge and thought, and improvisation informed by experience. Another is the interplay between actions and reflection on those actions – and their results.
Schön characterises ‘reflection in action’ and conveys its importance in creative design and problem-solving. Every time I return to this book, I find something more to inform my thinking.
A leading M.I.T. social scientist and consultant examines five professions,engineering, architecture, management, psychotherapy, and town planning,to show how professionals really go about solving problems.The best professionals, Donald Schoen maintains, know more than they can put into words. To meet the challenges of their work, they rely less on formulas learned in graduate school than on the kind of improvisation learned in practice. This unarticulated, largely unexamined process is the subject of Schoen's provocatively original book, an effort to show precisely how "reflection-in-action" works and how this vital creativity might be fostered in future professionals.
What makes an expert software designer? It is more than experience or innate ability. Expert software designers have specific habits, learned practices, and observed principles that they apply deliberately during their design work. This book offers sixty-six insights, distilled from years of studying experts at work, that capture what successful software designers actually do to create great software.
I come by my interest in history and the years before, during, and after the Second World War honestly. For one thing, both my father and my father-in-law served as pilots in the war, my father a P-38 pilot in North Africa and my father-in-law a B-17 bomber pilot in England. Their histories connect me with a period I think we can still almost reach with our fingertips and one that has had a momentous impact on our lives today. I have taken that interest and passion to discover and write true life stories of the war—focusing on the untold and unheard stories often of the “Average Joe.”
October 24, 1944, is not a day of national remembrance. Yet, more Americans serving in World War II perished on that day than on any other single day of the war.
The narrative of No Average Day proceeds hour by hour and incident by incident while focusing its attention on ordinary individuals—clerks, radio operators, cooks, sailors, machinist mates, riflemen, and pilots and their air crews. All were men who chose to serve their country and soon found themselves in a terrifying and otherworldly place.
No Average Day reveals the vastness of the war as it reaches past the beaches in…
October 24, 1944, is not a day of national remembrance. Yet, more Americans serving in World War II perished on that day than on December 7, 1941, when the Japanese attacked Pearl Harbor, or on June 6, 1944, when the Allies stormed the beaches of Normandy, or on any other single day of the war. In its telling of the events of October 24, No Average Day proceeds hour by hour and incident by incident. The book begins with Army Private First-Class Paul Miller's pre-dawn demise in the Sendai #6B Japanese prisoner of war camp. It concludes with the death…
