Merge branch 'master' of https://github.com/jwasham/google-interview-university
This commit is contained in:
commit
9b377ed960
1677
README-hn.md
Normal file
1677
README-hn.md
Normal file
File diff suppressed because it is too large
Load Diff
17
README.md
17
README.md
@ -3,8 +3,8 @@
|
||||
Translations:
|
||||
- [中文版本](README-cn.md)
|
||||
- [Español (in progress)](README-es.md) [Issue #80](https://github.com/jwasham/google-interview-university/issues/80)
|
||||
- हिन्दी (in progress) [Issue #81](https://github.com/jwasham/google-interview-university/issues/81)
|
||||
- [עברית (in progress)](README-he.md) [Issue #82] (https://github.com/jwasham/google-interview-university/issues/82)
|
||||
- [हिन्दी (in progress)](README-hn.md) [Issue #81](https://github.com/jwasham/google-interview-university/issues/81)
|
||||
- [עברית (in progress)](README-he.md) [Issue #82](https://github.com/jwasham/google-interview-university/issues/82)
|
||||
|
||||
|
||||
## What is it?
|
||||
@ -178,7 +178,7 @@ Everything below is an outline, and you should tackle the items in order from to
|
||||
|
||||
I'm using Github's special markdown flavor, including tasks lists to check progress.
|
||||
|
||||
- [x] Create a new branch so you can check items like this, just put an x in the brackets: [x]
|
||||
**Create a new branch so you can check items like this, just put an x in the brackets: [x]**
|
||||
|
||||
|
||||
Fork a branch and follow the commands below
|
||||
@ -476,7 +476,10 @@ I made a mobile-first website so I could review on my phone and tablet, wherever
|
||||
Make your own for free:
|
||||
|
||||
- [Flashcards site repo](https://github.com/jwasham/computer-science-flash-cards)
|
||||
- [My flash cards database](https://github.com/jwasham/computer-science-flash-cards/blob/master/cards-jwasham.db): Keep in mind I went overboard and have cards covering everything from assembly language and Python trivia to machine learning and statistics. It's way too much for what's required by Google.
|
||||
- [My flash cards database (old - 1200 cards)](https://github.com/jwasham/computer-science-flash-cards/blob/master/cards-jwasham.db):
|
||||
- [My flash cards database (new - 1800 cards)](https://github.com/jwasham/computer-science-flash-cards/blob/master/cards-jwasham-extreme.db):
|
||||
|
||||
Keep in mind I went overboard and have cards covering everything from assembly language and Python trivia to machine learning and statistics. It's way too much for what's required by Google.
|
||||
|
||||
**Note on flashcards:** The first time you recognize you know the answer, don't mark it as known. You have to see the
|
||||
same card and answer it several times correctly before you really know it. Repetition will put that knowledge deeper in
|
||||
@ -1104,7 +1107,12 @@ You'll get more graph practice in Skiena's book (see Books section below) and th
|
||||
- replaced by Colossus in 2012
|
||||
- [ ] [2004: MapReduce: Simplified Data Processing on Large Clusters]( http://static.googleusercontent.com/media/research.google.com/en//archive/mapreduce-osdi04.pdf)
|
||||
- mostly replaced by Cloud Dataflow?
|
||||
- [ ] [2006: Bigtable: A Distributed Storage System for Structured Data](https://static.googleusercontent.com/media/research.google.com/en//archive/bigtable-osdi06.pdf)
|
||||
- [An Inside Look at Google BigQuery](https://cloud.google.com/files/BigQueryTechnicalWP.pdf)
|
||||
- [ ] [2006: The Chubby Lock Service for Loosely-Coupled Distributed Systems](https://research.google.com/archive/chubby-osdi06.pdf)
|
||||
- [ ] [2007: What Every Programmer Should Know About Memory (very long, and the author encourages skipping of some sections)](https://www.akkadia.org/drepper/cpumemory.pdf)
|
||||
- [ ] [2010: Dapper, a Large-Scale Distributed Systems Tracing Infrastructure](https://research.google.com/pubs/archive/36356.pdf)
|
||||
- [ ] [2010: Dremel: Interactive Analysis of Web-Scale Datasets](https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/36632.pdf)
|
||||
- [ ] [2012: Google's Colossus](https://www.wired.com/2012/07/google-colossus/)
|
||||
- paper not available
|
||||
- [ ] 2012: AddressSanitizer: A Fast Address Sanity Checker:
|
||||
@ -1280,7 +1288,6 @@ You'll get more graph practice in Skiena's book (see Books section below) and th
|
||||
- [Design a random unique ID generation system](https://blog.twitter.com/2010/announcing-snowflake)
|
||||
- [Design an online multiplayer card game](http://www.indieflashblog.com/how-to-create-an-asynchronous-multiplayer-game.html)
|
||||
- [Design a key-value database](http://www.slideshare.net/dvirsky/introduction-to-redis)
|
||||
- [Design a function to return the top k requests during past time interval]( https://icmi.cs.ucsb.edu/research/tech_reports/reports/2005-23.pdf)
|
||||
- [Design a picture sharing system](http://highscalability.com/blog/2011/12/6/instagram-architecture-14-million-users-terabytes-of-photos.html)
|
||||
- [Design a recommendation system](http://ijcai13.org/files/tutorial_slides/td3.pdf)
|
||||
- [Design a URL-shortener system: copied from above](http://www.hiredintech.com/system-design/the-system-design-process/)
|
||||
|
12
discussions/how-to.md
Normal file
12
discussions/how-to.md
Normal file
@ -0,0 +1,12 @@
|
||||
To start a new discussion, make a new file, and if necessary, a directory:
|
||||
|
||||
examples:
|
||||
|
||||
- interviews/google-interviews.md
|
||||
- interviews/amazon-interviews.md
|
||||
|
||||
**Please do not discuss interview questions.**
|
||||
That's not fair to the employees who invest many hours into
|
||||
preparing, creating, improving, and calibrating their questions
|
||||
in order to make good hiring decisions. (even if you didn't sign an NDA)
|
||||
Discussing topics covered (BSTs, heaps, etc) is ok.
|
11
discussions/interviews/google-interviews.md
Normal file
11
discussions/interviews/google-interviews.md
Normal file
@ -0,0 +1,11 @@
|
||||
# Google Interview Experiences
|
||||
|
||||
**Please do not discuss interview questions.**
|
||||
That's not fair to the employees who invest many hours into
|
||||
preparing, creating, improving, and calibrating their questions
|
||||
in order to make good hiring decisions. (even if you didn't sign an NDA)
|
||||
Discussing topics covered (BSTs, heaps, etc) is ok.
|
||||
|
||||
|
||||
@jwasham: Hi everyone!
|
||||
|
11
translations/how-to.md
Normal file
11
translations/how-to.md
Normal file
@ -0,0 +1,11 @@
|
||||
Please put new translation README files here.
|
||||
|
||||
I'll migrate the existing translations when they are ready.
|
||||
|
||||
To start a new translation, please:
|
||||
|
||||
1. Make an issue (for collaboration with other translators)
|
||||
2. Make a pull request to collaborate and commit to.
|
||||
3. Let me know when it's ready to pull.
|
||||
|
||||
Thank you!
|
Loading…
x
Reference in New Issue
Block a user