Blogs

Why Design Systems Need APIs - Q&A with Louis Chenais, Chief Evangelist at Specify

Infoq

Design systems exist for their business value: to help organizations reach brand consistency across many platforms like the web, Android, or iOS.

Visit Site

Why Design Systems Need APIs - Q&A with Louis Chenais, Chief Evangelist at Specify
Natural Language Processing with Java - Second Edition: Book Review and InterviewInfoq Why the Dual Operating Model Impedes Enterprise AgilityInfoq How to Spark a Consumer-Grade UX RevolutionInfoq From Compliance-First to Risk-First: Why Companies Need a Culture ShiftInfoq Grab Redesigns Counter Service Storage for 50% Lower P99 LatencyInfoq The Async Multiprocessing Has Sound Foundations in Linux, But Further Testing is NeededInfoq Mintlify Alternatives: What to Consider (and Why There's No True Substitute)Mintlify Q&A with Deepgram’s New CPO, Ed AnuffDeepgram How a marketing agency increased client conversions 35% with Zapier CanvasZapier Workato integrations: What's included and when to use ZapierZapier Puppet’s New Mission: Automating Cloud Native InfrastructureThenewstack Three Key Design Considerations for an Event-Driven ArchitectureThenewstack Cloud Systems: Deploying to Amazon ECSPulumi Unpacking sandbox startup latency: why started ≠ readyModal Anthropic integration with Modal brings scalable compute to Claude ScienceModal Scaling Organizations Should Consider Building a Website Backed by a CRM PlatformCss Tricks Analyze JSON Data Using SQL and DuckDBMotherduck Do AI Agents Need a Semantic Layer?Motherduck Building a Remote MCP Server: OAuth, Tool Design & Lessons from 4,000+ AI Queries | MotherDuckMotherduck Cerebras Systems Announces Filing of Registration Statement for Proposed Initial Public OfferingCerebras