From 268bcc1ff37ca6c8c8cdd9db5ee662975986b5a1 Mon Sep 17 00:00:00 2001 From: John Washam Date: Tue, 13 Dec 2016 16:06:24 -0800 Subject: [PATCH] Fixed typo, and added note about languages. --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index edd1d31..7f0f47c 100644 --- a/README.md +++ b/README.md @@ -362,7 +362,7 @@ If you have more time (I want this book): **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 algoritms knowledge you'll need to start doing coding problems. +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. [Additional language-specific resources here.](programming-language-resources.md) @@ -514,6 +514,8 @@ Each day I take one subject from the list below, watch videos about that subject - 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. +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))