# Karri Saarinen - Design Is Search (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/57015875) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Karri Saarinen]] **Full Title**:: Design Is Search **Category**:: #tweets #readwise/tweets **Category Icon**:: 🐦 **URL**:: [x.com](https://x.com/karrisaarinen/status/1999730838280503775/?rw_tt_thread=True) **Host**:: [[x.com]] **Highlighted**:: [[2025-12-22]] **Created**:: [[2025-12-27]] ## Highlights - The mistake is letting those constraints define the space before you have found a direction worth committing to. Then they start shaping your imagination. ([View Highlight](https://read.readwise.io/read/01kd33ner6ekqh5pvrqg86310v)) ^968797378 - Some tools are great for exploration. They help you stay expressive and uncommitted. Others are great for construction. They reward structure, consistency, and correctness. Both are useful. The mistake is collapsing the entire act of design into a medium that is optimized for commitment. ([View Highlight](https://read.readwise.io/read/01kd33sjqta7cw7ck7g0ftzyh0)) ^968797613 - The thing I want to preserve is a phase of thinking, and not pretend it is not worth our time. Early design needs freedom. Later design needs reality. When those phases get collapsed, you can still ship, often faster than ever. But you might also trade the search for the shortest path. ([View Highlight](https://read.readwise.io/read/01kd33tvjs6dk02shrrkaxg099)) ^968797968 - Protect exploration from premature constraint. Invite constraints when you are ready to learn from them. Use code as feedback, not as a cage. ([View Highlight](https://read.readwise.io/read/01kd33vd19bn20hszwb16rfx9q)) ^968797985