• A Case For Use Cases
• People read on the web
• Why we use progressive enhancement to build GOV.UK
• Building a resilient frontend using progressive enhancement
• I Want To Confirm a Prompt That We Stay Alert
• Browsers and Representation
• Google vs. the web
• Back to the Bad Old Days of the Web
• The Mythical Document Web
• Breaking the web forward
• Back to the Future with RSS
• Client-Side Architecture Basics
• Organizing App Logic with the Clean Architecture
• Implementing DTOs, Mappers & the Repository Pattern
• Screaming Architecture
• Better Software Design with Application Layer Use Cases
• Anemic Domain Model
• Value Objects - DDD w/ TypeScript
• iOS 15, Humane
• Don't overabstract your components
• Meta Theme Color and Trickery
• Imagining native skip links
• Rails design patterns - The big picture
• Before You memo()
• Implement a Skip Link for Navigation-Heavy Sites
• Meaningful Motion with Action-Driven Animation
• An Interactive Guide to CSS Transitions
• Preload: What Is It Good For?
• The unreasonable effectiveness of simple HTML
• Open Peeps
• System Design 101
• A primer on investing for designers and developers
• In Critical Defense of Frontend Develop
• Be Wary of Nesting Roles
• Accessible SVGs
• dotCSS 2019 - Sarah Dayan - In Defense of Utility-First CSS
• Alt-texts: The Ultimate Guide
• Polymorphic React Components in TypeScript
• CSS and Scalability
• The UI & UX Tips Collection: Volume One.
• Practical React Query
• Don't design for mobile
• Stop Using “Drop-down”
• Decoupling, Architecture and Teams
• The Lava Layer Anti-Pattern
• UI as an afterthought
• In 2020, what is "frontend" 🤨
• How React Query gives you almost everything you thought you needed GraphQL for
• Wormhole state management
• Todo el software está roto
• What is the Value of Browser Diversity?
• Margins and Composability in CSS
• Nailing Your First (Info-Product) Launch
• Defining Component APIs in React
• The Modern Front-End Design System Stack
• Building the New facebook.com with React, GraphQL and Relay
• Architecting UIs for Change
• When frontend means full stack
• Building a Button Part 2: Hover Interactions
• Building a Button Part 1: Press Events
• About HTML semantics and front-end architecture
• "Semantic" CSS
• CSS Utility Classes and "Separation of Concerns"
• Second-guessing the modern web
• A clean start for the web
• Writing Type-Safe Polymorphic React Components (Without Crashing TypeScript)
• Using SwiftUI's Spacer to Create Complex Layouts
• Most tech content is bullshit
• The Art of UI Skeletons
• How to Design a Web Application: Software Architecture 101
• Shared Hook State with SWR
• Testing in the Frontend World
• The Real Dark Web
• The Elements of UI Engineering
• frontend design, react, and a bridge over the great divide
• The Great Divide
• We have a problem with promises
• Taming the asynchronous beast with ES7
• 7 Principles of Rich Web Applications
• The Fault in Our Tolerance: Accounting for Failures in React
• 🌱 My blog is a digital garden, not a blog
• Shape Up: Stop Running in Circles and Ship Work that Matters
• How the Blog Broke the Web
• Turning the database inside-out with Apache Samza
• Design Systems and Front-End Architecture by Stuart Robson
• How to Section Your HTML
• write on your own website
• Going Indie. Step 2: Reclaiming Content
• Just write
• The Documentation Compendium
• Why Text Buttons Hurt Mobile Usability
• How Technology Hijacks People’s Minds — from a Magician and Google’s Design Ethicist
• HTTP Frameworks Must Die
• Bulletproof node.js project architecture 🛡️
• The Power of Sensible Defaults
• HTML Reference
• CSS Reference
• The God Login
• Your Body Text Is Too Small
• Architecture as a burden