floguo's artifacts
floguo.com · 1,842 words · saved by 1 readers
personal website of flora guo
The web feels direct. You click Save, the button changes, and your work is there when you return tomorrow. Underneath that moment is a conversation between computers. The browser turns code into an interface. A server applies the product's rules. A database keeps what should survive after the tab closes. The internet carries messages between them. You do not need to become an engineer to design for this system. You do need a rough map of it. The map helps explain why a screen loads in pieces, why a form can fail after submission, and why a seemingly small feature can require a change to…
saved by
related reading
- Everything I know about good system designseangoedecke.com
- Design Engineeringfloguo.com
- Design with materials, not features | thesephist.comthesephist.com
- Building data-centric apps with a reactive relational databaseriffle.systems
- My website is a shifting house next to a river of knowledge. What could yours be? - The Creative Independentthecreativeindependent.com
- Frank Chimero · The Web’s Grainfrankchimero.com
- Web Architecture 101. The basic architecture concepts I wish… | by Jonathan Fulton | The Storyblocks Tech Blog | Mediummedium.com
- Pure UIrauchg.com
- Say precisely what you mean.index.how
- Why Figma Wins - kwokchainkwokchain.com
- Learning From Terminals to Design the Future of User Interfaces — brandur.orgbrandur.org
- cristobal.arquipelago.org/writing/folk.html#fn2cristobal.arquipelago.org