✳flâneur — a map of the web's best reading

The system design handbook. Take the guesswork out of designing… | by Daniel Kwok | InterviewNoodle

interviewnoodle.com · 1,559 words · saved by 1 readers

Once you’ve been coding long enough, you’ll soon elevate to a point where code syntax, languages, frameworks don’t really bother you as much. You might not know how everything works in detail, yet still confident that you will be able to pick it up in no time. That’s when it’ll be more beneficial to start looking into system design, rather than learning yet another framework again. Instead of asking “What programming language should I use to build this?” System design asks about “What are the core functionalities of this application?” “How does user interact with this system? What are the use case we support?” “What are the database tables, apis, fields, UIs that this application should have, and how do they interact with each other?” Most system design interview will usually be an application that looks this way. This is because, to be frank, most applications are built this way, hence most other developers are trained this way. It’s the quickest way to do a litmus test on the compete

The system design handbook Daniel Kwok 8 min read · Jul 26, 2021 -- 1 Listen Share Take the guesswork out of designing your database tables and APIs When should I learn about system design? Once you’ve been coding long enough, you’ll soon elevate to a point where code syntax, languages, frameworks don’t really bother you as much. You might not know how everything works in detail, yet still confident that you will be able to pick it up in no time. That’s when it’ll be more beneficial to start looking into system design , rather than learning yet another framework again. What is system design? I

Explore this link on the map →

related reading