✳︎ design engineer/ui wizard → @ponder 
✳︎ humanist • petrolhead/gearhead
✳︎ React+SwiftUI
✳︎ bento.me/matthew

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

in case of Next.js it’s a problem created by its design: hide cache behind cache behind cache and never, ever ever, let the developer be in full control of invalidation, and what little control is left, make it painful