Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cs76 should be cs75 (assuming this is the same cs75 referred to above) #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

cs76 should be cs75 (assuming this is the same cs75 referred to above) #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -219,7 +219,7 @@ Depending on where you are interviewing, go through the company blog. VERY USEFU

**I would HIGHLY recommend you do not take a shortcut unless you have a week or so for an interview. System design is best learnt by practising, shortcuts might help you in the short term, but would recommend coming back to this link for an in-depth understanding after the interview**

* a) Go through cs76 and Udacity's links given above for scaling systems.
* a) Go through cs75 and Udacity's links given above for scaling systems.
* b) Go through the engineering blog of the company you are interviewing in (or if its a startup go through the link of the company closest to yours)
* c) See this talk: http://www.hiredintech.com/system-design/the-system-design-process/ and develop a process for how to answer such questions.
* d) Remember these terms, just roll over them in your interview in your mind, and if relevant mention it in the interview
Expand Down