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.

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

Translation to Korean in progress #119

Merged
merged 46 commits into from
Jan 11, 2017
Merged
Changes from 2 commits
Commits
Show all changes
46 commits
Select commit Hold shift + click to select a range
cd15af1
README-ko.md added
Jan 5, 2017
2e6f91d
'What is it?' and part of 'Table of Contents' translated
Jan 5, 2017
5e24a64
Fix minor typos
Jan 5, 2017
9a55f9a
translate more of 'Table of Contents'
Jan 5, 2017
6bae129
translate more of 'Table of Contents'
Jan 5, 2017
97cee5c
translate more of 'Tabe of Contents', except for terminologies vague …
Jan 5, 2017
894ef95
'Table of Contents' is almost translated, except for some ambiguous t…
Jan 5, 2017
02b0cfd
Why use it translated, except the title itself
Jan 6, 2017
bbad6aa
'How use it', 'Get in a Googley Mood' translated
Jan 6, 2017
ff1963c
'Translations' translated
Jan 6, 2017
d739851
'Book List' translated
spartzames Jan 6, 2017
af3fdf2
Merge pull request #3 from spartz90/master
Jan 6, 2017
a33f468
'Coding Question Practice' translated
Jan 6, 2017
7b00169
translate Don't feel you aren't smart enough
hoonhoonhoon Jan 6, 2017
0e12c2c
Merge pull request #4 from singcodes/master
Jan 6, 2017
02a70a1
Update README-ko.md
daegwang Jan 6, 2017
c7d3af6
Update README-ko.md
daegwang Jan 6, 2017
9998691
translate "About Google"
mjpark03 Jan 6, 2017
e0d9ee0
Translate some part of 'Before you get started'
kwangin Jan 8, 2017
ccf7432
README-ko.md added
Jan 5, 2017
fac6954
'What is it?' and part of 'Table of Contents' translated
Jan 5, 2017
cb7e2bb
Fix minor typos
Jan 5, 2017
0176094
translate more of 'Table of Contents'
Jan 5, 2017
34fb631
translate more of 'Table of Contents'
Jan 5, 2017
04d20cb
translate more of 'Tabe of Contents', except for terminologies vague …
Jan 5, 2017
50ba383
'Table of Contents' is almost translated, except for some ambiguous t…
Jan 5, 2017
fe3a3b7
Why use it translated, except the title itself
Jan 6, 2017
e638d62
'How use it', 'Get in a Googley Mood' translated
Jan 6, 2017
0827555
'Translations' translated
Jan 6, 2017
91a2f34
'Book List' translated
spartzames Jan 6, 2017
0d16354
'Coding Question Practice' translated
Jan 6, 2017
cf5305e
translate some annotation
Hanney-Ryu Jan 9, 2017
eea8282
'The Daily Plan' translated
daveleee Jan 9, 2017
d087865
quick start to partake of GIU translation to Korean project
Jan 9, 2017
a93eab8
Merge pull request #10 from daveleee/master
Jan 9, 2017
40cf65a
Merge pull request #11 from johannalee/readme-ko
Jan 9, 2017
83e0427
Merge branch 'master' into master
Jan 9, 2017
f8482af
Merge pull request #12 from mjpark03/master
Jan 9, 2017
654be51
Merge branch 'master' into master
kination Jan 9, 2017
3eb5634
Merge pull request #13 from djKooks/master
Jan 9, 2017
2ce8096
'Prerequisite Knowledge' translated
daveleee Jan 10, 2017
d8c3169
Merge pull request #15 from daveleee/master
Jan 10, 2017
63c4749
translated some parts
Hanney-Ryu Jan 10, 2017
0d66237
Merge branch 'master' into master
Jan 10, 2017
286f89d
Merge pull request #17 from DaeGwang/master
Jan 10, 2017
39fb4ef
Merge pull request #18 from Hanney-Ryu/master
Jan 10, 2017
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
65 changes: 29 additions & 36 deletions translations/README-ko.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,22 +216,21 @@ I'm in the queue right now. Hope to interview soon.

나의 이야기: [내가 구글 인터뷰를 풀 타임으로 8 개월 동안 공부한 이유](https://www.vobour.com/book/view/fiRGQMcmRkaw7pgpL) (원문 : [Why I Studied Full-Time for 8 Months for a Google Interview](https://medium.com/@googleyasheck/why-i-studied-full-time-for-8-months-for-a-google-interview-cc662ce9bb13))

I'm on the journey, too. Follow along:

- **Blog**: [GoogleyAsHeck.com](https://googleyasheck.com/)
저의 구글로 향하는 여행 함께 해주세요!
- **블로그**: [GoogleyAsHeck.com](https://googleyasheck.com/)
- Twitter: [@googleyasheck](https://twitter.com/googleyasheck)
- Twitter: [@StartupNextDoor](https://twitter.com/StartupNextDoor)
- Google+: [+Googleyasheck](https://plus.google.com/+Googleyasheck)
- LinkedIn: [johnawasham](https://www.linkedin.com/in/johnawasham)

![John Washam - Google Interview University](https://dng5l3qzreal6.cloudfront.net/2016/Aug/book_stack_photo_resized_18_1469302751157-1472661280368.png)

## Don't feel you aren't smart enough
- Google engineers are smart, but many have an insecurity that they aren't smart enough, even though they work at Google.
- [The myth of the Genius Programmer](https://www.youtube.com/watch?v=0SARbwvhupQ)
- [It's Dangerous to Go Alone: Battling the Invisible Monsters in Tech](https://www.youtube.com/watch?v=1i8ylq4j_EY)
## 당신은 충분히 똑똑합니다
- 구글 엔지니어들은 똑똑합니다. 하지만 그들 조차도 자신들의 지적 능력면에 대해서 불안감을 갖기 일쑤입니다.
- [천재 프로그래머의 미스터리](https://www.youtube.com/watch?v=0SARbwvhupQ)
- [위험한 홀로서기: 테크 산업의 보이지 않는 괴물들의 전쟁](https://www.youtube.com/watch?v=1i8ylq4j_EY)

## About Google
## 구글에 대해

- [ ] For students - [Google Careers: Technical Development Guide](https://www.google.com/about/careers/students/guide-to-technical-development.html)
- [ ] How Search Works:
Expand All @@ -248,36 +247,34 @@ I'm on the journey, too. Follow along:
- [ ] [Book: How Google Works](https://www.amazon.com/How-Google-Works-Eric-Schmidt/dp/1455582344)
- [ ] [Made by Google announcement - Oct 2016 (video)](https://www.youtube.com/watch?v=q4y0KOeXViI)

## About Video Resources
## 비디오 자료

Some videos are available only by enrolling in a Coursera, EdX, or Lynda.com class. These are called MOOCs.
Sometimes the classes are not in session so you have to wait a couple of months, so you have no access. Lynda.com courses are not free.
어떤 비디오 자료들은 Coursera, EdX, 또는 Lynda.com과 같은 온라인 교육 사이트들에서 시청이 가능합니다. 이러한 사이트들을 흔히 온라인 대중 공개 강좌(Massive Open Online Course) 라고 합니다. 어떤 강좌들은 개강하지 않아 몇달 정도를 기다리고 수강을 해야하는 것들도 있습니다. Lynda.com 은 유료 사이트 입니다.

I'd appreciate your help to add free and always-available public sources, such as YouTube videos to accompany the online course videos.
I like using university lectures.
만약에 무료 강좌나 YouTube와 같은 온라인 공개 소스들을 알고 계시면 나눠주세요. 저는 대학강의들을 보는 것을 좋아합니다.


## Interview Process & General Interview Prep
## 인터뷰 과정 & 전반적인 인터뷰 준비 과정

- [ ] Videos:
- [ ] 비디오:
- [ ] [How to Work at Google: Prepare for an Engineering Interview (video)](https://www.youtube.com/watch?v=ko-KkSmp-Lk)
- [ ] [How to Work at Google: Example Coding/Engineering Interview (video)](https://www.youtube.com/watch?v=XKu_SEDAykw)
- [ ] [How to Work at Google - Candidate Coaching Session (video)](https://www.youtube.com/watch?v=oWbUtlUhwa8&feature=youtu.be)
- [ ] [Google Recruiters Share Technical Interview Tips (video)](https://www.youtube.com/watch?v=qc1owf2-220&feature=youtu.be)
- [ ] [How to Work at Google: Tech Resume Preparation (video)](https://www.youtube.com/watch?v=8npJLXkcmu8)

- [ ] Articles:
- [ ] 읽을 거리들:
- [ ] [Becoming a Googler in Three Steps](http:https://www.google.com/about/careers/lifeatgoogle/hiringprocess/)
- [ ] [Get That Job at Google](http:https://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html)
- all the things he mentions that you need to know are listed below
- [ ] _(very dated)_ [How To Get A Job At Google, Interview Questions, Hiring Process](http:https://dondodge.typepad.com/the_next_big_thing/2010/09/how-to-get-a-job-at-google-interview-questions-hiring-process.html)
- [ ] [Phone Screen Questions](http:https://sites.google.com/site/steveyegge2/five-essential-phone-screen-questions)

- [ ] Prep Courses:
- [ ] 준비 코스:
- [ ] [Software Engineer Interview Unleashed (paid course)](https://www.udemy.com/software-engineer-interview-unleashed):
- Learn how to make yourself ready for software engineer interviews from a former Google interviewer.

- [ ] Additional (not suggested by Google but I added):
- [ ] 부가물 (구글이 추천하지않은 내가 더한 것들):
- [ ] [ABC: Always Be Coding](https://medium.com/always-be-coding/abc-always-be-coding-d5f8051afce2#.4heg8zvm4)
- [ ] [Four Steps To Google Without A Degree](https://medium.com/always-be-coding/four-steps-to-google-without-a-degree-8f381aa6bd5e#.asalo1vfx)
- [ ] [Whiteboarding](https://medium.com/@dpup/whiteboarding-4df873dbba2e#.hf6jn45g1)
Expand All @@ -290,37 +287,35 @@ Sometimes the classes are not in session so you have to wait a couple of months,
- [ ] ['How to Get a Job at the Big 4 - Amazon, Facebook, Google & Microsoft' (video)](https://www.youtube.com/watch?v=YJZCUhxNCv8)
- [ ] [Failing at Google Interviews](http:https://alexbowe.com/failing-at-google-interviews/)

## Pick One Language for the Interview

I wrote this short article about it: [Important: Pick One Language for the Google Interview](https://googleyasheck.com/important-pick-one-language-for-the-google-interview/)
## 인터뷰를 위한 언어 고르기

You can use a language you are comfortable in to do the coding part of the interview, but for Google, these are solid choices:
인터뷰때 사용할 언어 고르는 법에 대해 짧은 글을 하나 썼습니다: [구글 인터뷰를 위한 언어 고르기](https://googleyasheck.com/important-pick-one-language-for-the-google-interview/)

인터뷰때에 당신이 쓰기에 편한 언어를 선택해도 되지만, 구글 인터뷰에 선호되는 언어들은 다음과 같습니다.
- C++
- Java
- Python

You could also use these, but read around first. There may be caveats:

다음과 같은 언어들도 사용해도 괜찮지만, 이 언어들은 위험부담이 따를수도 있습니다.
- JavaScript
- Ruby

You need to be very comfortable in the language and be knowledgeable.
당신은 당신의 언어에 익숙하고 그 언어에 대해 잘 알아야 합니다.

Read more about choices:
언어 선택을 도와줄 만한 읽을 거리들
- http:https://www.byte-by-byte.com/choose-the-right-language-for-your-coding-interview/
- http:https://blog.codingforinterviews.com/best-programming-language-jobs/
- https://www.quora.com/What-is-the-best-language-to-program-in-for-an-in-person-Google-interview

[See language resources here](programming-language-resources.md)
[프로그래밍 언어 참고목록](programming-language-resources.md)

You'll see some C, C++, and Python learning included below, because I'm learning. There are a few books involved, see the bottom.
제가 배우고 있는 C, C++ 그리고 Python의 학습 자료과 그것들의 참고서를 아래에 기재했습니다.

## 도서 목록

아래의 목록은 내가 공부했던 책들보다는 적다. 당신의 시간을 절약하기 위해 몇몇 책들은 생략하였다.

### Interview Prep (인터뷰 준비를 위해서)
### 인터뷰 준비를 위해서

- [ ] [Programming Interviews Exposed: Secrets to Landing Your Next Job, 2nd Edition](http:https://www.wiley.com/WileyCDA/WileyTitle/productCd-047012167X.html)
- C++ 과 JAVA 문제의 답변을 위해서
Expand All @@ -338,10 +333,9 @@ You'll see some C, C++, and Python learning included below, because I'm learning
- 모든 코드가 C++로 되어있다, 만일 당신의 인터뷰에서 C++를 사용하길 고려한다면 정말 좋은 책이다.
- 일반적인 문제들을 해결하기 위해 좋은 책이다.

### Computer Architecture

If short on time:
### 컴퓨터 구조

준비기간이 짧을 때,
- [ ] [Write Great Code: Volume 1: Understanding the Machine](https://www.amazon.com/Write-Great-Code-Understanding-Machine/dp/1593270038)
- The book was published in 2004, and is somewhat outdated, but it's a terrific resource for understanding a computer in brief.
- The author invented HLA, so take mentions and examples in HLA with a grain of salt. Not widely used, but decent examples of what assembly looks like.
Expand All @@ -356,14 +350,13 @@ If short on time:
- Chapter 10 - Instruction Set Architecture
- Chapter 11 - Memory Architecture and Organization

If you have more time (I want this book):

만약에 시간적 여유가 좀 더 있다면 아래 서적을 읽어보는 것을 권유합니다.
- [ ] [Computer Architecture, Fifth Edition: A Quantitative Approach](https://www.amazon.com/dp/012383872X/)
- For a richer, more up-to-date (2011), but longer treatment

### Language Specific
### 언어 구체적

**You need to choose a language for the interview (see above).** Here are my recommendations by language. I don't have resources for all languages. I welcome additions.
**인터뷰를 위해 당신의 언어를 선택하여야 합니다 (윗글 참조)** 아래는 제가 추천하는 언어들입니다. 이 언어들중에 부연설명이나 부가 자료들이 있다면 나눠 주세요.

If you read though one of these, you should have all the data structures and algorithms knowledge you'll need to start doing coding problems.
**You can skip all the video lectures in this project**, unless you'd like a review.
Expand Down