CreateDesignSystem @CreateNewDS

Have you heard of the 12-Factor App? The "12 Factor App" offers a set of best practices for building modern software applications. Following these 12 principles can help developers and teams in building reliable, scalable, and manageable applications. Here's a brief overview of each principle: 1. Codebase: Have one place to keep all your code, and manage it using version control like Git. 2. Dependencies: List all the things your app needs to work properly, and make sure they're easy to install. 3. Config: Keep important settings like database credentials separate from your code, so you can change them without rewriting code. 4. Backing Services: Use other services (like databases or payment processors) as separate components that your app connects to. 5. Build, Release, Run: Make a clear distinction between preparing your app, releasing it, and running it in production. 6. Processes: Design your app so that each part doesn't rely on a specific computer or memory. It's like making LEGO blocks that fit together. 7. Port Binding: Let your app be accessible through a network port, and make sure it doesn't store critical information on a single computer. 8. Concurrency: Make your app able to handle more work by adding more copies of the same thing, like hiring more workers for a busy restaurant. 9. Disposability: Your app should start quickly and shut down gracefully, like turning off a light switch instead of yanking out the power cord. 10. Dev/Prod Parity: Ensure that what you use for developing your app is very similar to what you use in production, to avoid surprises. 11. Logs: Keep a record of what happens in your app so you can understand and fix issues, like a diary for your software. 12. Admin Processes: Run special tasks separately from your app, like doing maintenance work in a workshop instead of on the factory floor. Over to you: Where do you think these principles can have the most impact in improving software development practices? -- Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/3KCnWXq

My recommended materials for cracking your next technical interview: Coding - Leetcode - Cracking the coding interview book - Neetcode System Design Interview - System Design Interview book 1, 2 by Alex Xu - Grokking the system design by Design Guru - Design Data-intensive Application book Behavioral interview - Tech Interview Handbook (Github repo) - A Life Engineered (YT) - STAR method (general method) OOD Interview - Interviewready - OOD by educative - Head First Design Patterns Book Mock interviews - Interviewingio - Pramp - Meetapro Apply for Jobs - Linkedin - Monster - Indeed Over to you: What is your favorite interview prep material? – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/3KCnWXq

Your next design system is… Markdown. We wrote about how 𝙳𝙴𝚂𝙸𝙶𝙽.𝚖𝚍 is helping solve the hardest problem in AI today: slop. And how you can truly, finally scale design taste within a large organization.

Vercel @vercel

a month ago

Our agents use 𝚟𝚎𝚛𝚌𝚎𝚕​.𝚌𝚘𝚖/𝚍𝚎𝚜𝚒𝚐𝚗​.𝚖𝚍 to build on-brand pages. ▪︎ One file encodes decisions and guidance ▪︎ Output is shaped through our eval harness ▪︎ Production feedback is fed back into the loop vercel.com/blog/how-our-a…

62 121 2K 701K 3K

With AI acting as the translation layer, we move beyond simple token pipelines. AI can interpret design intent from code updates, catch contrast failures before deployment, and maintain documentation seamlessly.

Imagine an ecosystem where an update on any single axis automatically propagates across the other two. When code changes, Figma updates. When accessibility standards evolve, design tokens adapt automatically. #designtokens

The future of design system architecture is bi-directional synchronisation across three axes: Figma components, the production codebase, and live documentation—with built-in WCAG compliance and AI orchestration. #UXDesign #designsystem #AI

#Designsystem, #UXDesign, #Design, #system

CreateDesignSystem @CreateNewDS

a month ago

UX Managers: How do you justify the cost of your DS to stakeholders? I created a calculator to help streamline that conversation. Would love to get some feedback from the community on whether this makes sense for your workflow. Check it out here: lnkd.in/e6xQjsq9

0 1 0 15 0

UX Managers: How do you justify the cost of your DS to stakeholders? I created a calculator to help streamline that conversation. Would love to get some feedback from the community on whether this makes sense for your workflow. Check it out here: lnkd.in/e6xQjsq9

@nathanacurtis Interesting @nathanacurtis I am working something similar but different I am working on a system, which creates, maintains the DS in Figma, code and documentation. All connected in both directions check it out. its in POC phase createdesignsystem.com

Today we’re releasing an early preview of the /design command in Claude Code! from CC Desktop or CLI, try something like "/design a few options for {feature}" before you build — pick your fave artboard, edit it and implement.

@henry_daggett Completely agree. We built all this plumbing for AI tokens, but skipped the actual bottleneck: interface generation where teams spend 80% of their time.

UX Managers: How do you justify the cost of your Design System to stakeholders? 📊I created a calculator to help streamline that conversation. Feedback whether this makes sense for your workflow. Check this: createdesignsystem.com/pricing #DesignSystem #UXDesign #DesignManagement