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
37 changes: 19 additions & 18 deletions translations/README-ko.md
Original file line number Diff line number Diff line change
Expand Up @@ -508,35 +508,36 @@ technologies but were not mentioned in those notes:
- Javascript
- HTML, CSS, and other front-end technologies

## The Daily Plan
## 하루 하루의 계획

Some subjects take one day, and some will take multiple days. Some are just learning with nothing to implement.
어떤 주제들은 하루가 걸리고, 어떤 것들은 며칠이 걸릴 것이다.
또 어떤것은 구현할 것들이 없이 그냥 배우는 것들이다.

Each day I take one subject from the list below, watch videos about that subject, and write an implementation in:
- C - using structs and functions that take a struct * and something else as args.
- C++ - without using built-in types
- C++ - using built-in types, like STL's std::list for a linked list
- Python - using built-in types (to keep practicing Python)
- and write tests to ensure I'm doing it right, sometimes just using simple assert() statements
- You may do Java or something else, this is just my thing.
아래 리스트에 있는 것에서 매일 하나의 주제를 택했고, 그 주제에 대한 강의를 보고, 구현을 했다:
- C - 인자를 가지는 구조체와 함수 사용
- C++ - 빌트인 타입 사용하지 않음
- C++ - 링크리스트를 위한 STL's std::list 같은 빌트인 타입 사용
- Python - 빌트인 타입 사용 (파이선 연습을 계속 하려고)
- 제대로 하고 있는지 테스트를 했고 가끔은 간단한 assert() 사용
- 당신은 아마 자바나 그 어떤 언어를 이용하겠지만 이것은 그냥 내 것들이다.

You don't need all these. You need only [one language for the interview](#pick-one-language-for-the-interview).
당신은 이것을 다 할 필요는 없다. 단지 [인터뷰를 위한 하나의 언어를 할 것.](#인터뷰를 위한 언어를 하나 골라 두어라).

Why code in all of these?
- Practice, practice, practice, until I'm sick of it, and can do it with no problem (some have many edge cases and bookkeeping details to remember)
- Work within the raw constraints (allocating/freeing memory without help of garbage collection (except Python))
- Make use of built-in types so I have experience using the built-in tools for real-world use (not going to write my own linked list implementation in production)
왜 이 모든것을 코딩해야 하는가?
- 나는 이것에 미칠때까지 연습하고 또 연습했고, 아무런 문제 없이 할 수 있게 되었다 (어떤 것들은 다양한 케이스가 있고 이것을 기억하기 위해 기록을 보관했다.)
- 있는 그대로의 제한 속에서 연습 (garbage collection의 도움없이 메모리 할당과 해지 (파이선 빼고))
- 빌트인 타입을 사용하여 나는 빌트인 도구에 대한 경험이 있게 되었다. (내 프로젝트의 링크 리스트 구현은 쓰지 않을 예정)

I may not have time to do all of these for every subject, but I'll try.
모든 주제에 대한 모든 것을 할 수 없지만 나는 노력했다.

You can see my code here:
나의 코드를 여기서 확인하세요:
- [C] (https://github.com/jwasham/practice-c)
- [C++] (https://github.com/jwasham/practice-cpp)
- [Python] (https://github.com/jwasham/practice-python)

You don't need to memorize the guts of every algorithm.
당신은 모든 알고리즘에 대해서 기억할 필요는 없다.

Write code on a whiteboard or paper, not a computer. Test with some sample inputs. Then test it out on a computer.
컴퓨터에 코딩하지 말고 와이트보드나 종이에 적어보아라. 인풋 값으로 샘플 테스트를 해 보아라. 그리고 컴퓨터로 테스트해 보아라.

## Prerequisite Knowledge

Expand Down