HackerTube.live
Books / Design

THE READING ROOM / BOOK GUIDE

Creative Selection

Ken Kocienda

A software engineer who worked on the iPhone keyboard and Safari describes how Apple turned rough prototypes into products, and what that process asked of the people inside it.

About the book

Ken Kocienda writes as a participant in the development of the iPhone and its keyboard, not as a historian of Apple. His account follows small teams as they proposed designs, built demos, and argued over details until someone made a decision. The organizing idea is that good products come from repeated cycles of making something concrete and judging it honestly, a process he calls creative selection.

Steve Jobs appears as a demanding presence in product reviews, and the book stays close to the daily mechanics of design and engineering: how a demo earns attention, how feedback gets absorbed, and how a team settles on one approach among several. Readers looking for a memoir of a single project will find that here, along with reflections on craft and collaboration.

How to read it

Treat the book as a practitioner's narrative rather than a management manual. Kocienda builds his arguments from specific episodes, so the value lies in following the examples closely and noticing what the team tried, discarded, and kept. The prose is plain, which makes the technical material accessible to readers outside software engineering.

Watch the distinction between generating options and choosing among them. That tension runs through the account and gives it more substance than a simple celebration of intuition. The book is short enough to read in a few sittings, though the density of detail rewards slower attention to the design decisions.

Who it suits

This book suits product designers, engineers, and managers who want a grounded view of how software gets made inside a large company. Readers curious about the iPhone's development will find firsthand description of the work behind a familiar device. Those interested in how teams evaluate competing ideas, rather than in Apple lore alone, will get the most from it.

Reading considerations

The perspective is one engineer's, focused on his own projects and immediate colleagues, so it should not be read as a complete account of Apple's design culture or of the iPhone's creation. The book's central claim is worth testing against your own experience: selection depends on judgment, and judgment depends on who is in the room.

Follow the HN conversation

27 different recommenders are recorded in the upstream dataset. These are AI-classified source counts, not an independent rating.

Search HN comments about this book ↗

Explore videos on the same subject ↗

Book notes prepared with DeepSeek, using catalogue records and Open Library subject information. They are reading guidance, not a personal review or a verified chapter-by-chapter account. Book details can vary by edition. HN data methodology · Book metadata and covers.