Загрузка видео...
Не удалось загрузить видео
Understanding system design helps you build better apps, even when vibe coding. Better architecture decisions. Better AI prompts. Fewer surprises when your app grows. So I built an interactive app to learn system design visually.
325,305 просмотров • 1 день назад •via X (Twitter)
Комментарии: 34

As always, if there are any lessons you'd like me to add or other learning apps you'd like to see, let me know! I'll keep adding more lessons and features to these apps. I'm also planning to build another app covering MCPs and other AI-related architecture concepts. Here are some other learning apps I've built recently.

Fair take on how this plays out wvVWJX

This is fun to learn. Thank you for building this.

Thanks for making this.

Banger website

knowing the vocabulary is most of the prompt win. "put a queue between upload and processing" gets a very different answer than "make it scale"

You make really great visualizations! Thank you!

設計の前提が見えると、AIに任せる範囲や確認点も決めやすくなりますね。特にアプリが育った後の変更まで想像できると、最初の試作を長く使える土台にできそうです。

the biggest payoff of system design while vibe coding is knowing what to forbid in the prompt. 'no new service, reuse the existing queue' saves more rework than any feature description.

hell yeah, nice!

agents get me working code fast. what they don't give me is the picture of how it all hangs together. this is the right gap to fill

You willing to sell me the source code for this? I'd like to explore building interactive apps like this but for my own solutions (as a way to communicate with colleagues and customers).

Looks very fun to play around with

This is really useful, thanks!

Build via Fable 5.2 or 4 carbon?

what helps me with ai coding is limits. one line in the prompt, like single module and no new libraries, keeps the change small and easy to review.

Even just knowing to say "put a queue in front of it" instead of "make it scale" changes what the agent builds.

might actually use this before the next build

need this before “just add a database” becomes the most expensive sentence in my project.

Great way to learn system design. One idea for a future module: Preventing AI-driven attacks e.g. via authorization at the API layer. The FBI just named APIs missing authentication as a common entry point in AI-driven attacks.

Those three wins are exactly what vibe coding needs most.

Thanks for the app ,long awaited for this.very helpful content.

Thank you Do you have a homepage where all these apps are listed?

Cool. Nice job

the agent will pick a new architecture every session if you let it 😅 love this

Do you have these apps open sourced or no ? Couldn't find them in your github

Good call. From the design side, vibe-coded apps usually hit state problems before scale problems: empty, loading, error, offline. Does the app cover where UI state should live vs. server state? That's where my prototypes fall apart first.

that's so cool , was needed this. does it also has the Popular platforms architecture concepts too ? will try it out for sure

How are you doing this? I'm so impressed! I want to make some for myself :)

love these videos. do you have a breakdown on how you did this and what you used to make them (aside from prompting claude)?

System design deserves a life beyond interview prep. Giving people a visual way to get curious about it is a lovely thing to build ❤️

system design is the ikea manual vibe coders throw away

Congrats on the launch, the minimal footprint and response time look super clean!

A useful visual lesson would let learners break the architecture: slow one dependency, fill a queue, then watch retries amplify the load. That teaches why a design works, rather than just which boxes belong in the diagram.



