What David Crawshaw thinks about design
Software engineer; co-founder and former CTO of Tailscale, previously on the Go team at Google.
David Crawshaw did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
Filter design · Newest first
Only David Crawshaw on design. See everyone on design
7 dated positions, 2021 to 2026, in their own words. Our reading of what David Crawshaw has said — not written or endorsed by them.
-
Our readingVMs are the wrong cloud abstraction because they bundle CPU and memory into fixed-size units.
Their wordsVMs are the wrong shape because they are tied to CPU/memory resources.
-
Their wordsYou cannot solve the fundamental problems with cloud abstractions by building new abstractions on top.
- 2 months earlier
-
Our readingMost current software and ways of solving problems are structured the wrong way for the agent era.
Their wordsMost software is the wrong shape now. Most of the ways we try to solve problems are the wrong shape.
↗Eight more months of agentscrawshaw.io 2nd of 3 in this piece
-
Their wordsthe best software for an agent is whatever is best for a programmer.
↗Eight more months of agentscrawshaw.io 3rd of 3 in this piece
- 2 years earlier
-
Our readingProgramming is fundamentally the practice of making tradeoffs about what matters and what doesn't.
Their wordsProgramming is the art of tradeoffs. You have to decide what matters and what does not.
↗jsonfile: a quick hack for tinkeringcrawshaw.io 2nd of 3 in this piece
- 2 years earlier
-
Their wordsa good software project tries to break downstream as little as possible, and when we do break downstream, we should do our best to make the breakage obvious and easy to fix.
↗log4j: between a rock and a hard placecrawshaw.io 1st of 3 in this piece
-
Their wordsWe as a profession misunderstand and misuse the concept of backwards compatibility, both upstream and downstream, by focusing on narrow legalistic definitions instead of outcomes.
↗log4j: between a rock and a hard placecrawshaw.io 3rd of 3 in this piece