[pull] master from amejiarosario:master

book/D-interview-questions-solutions.asc

@@ -47,7 +47,7 @@ include::interview-questions/max-subarray.js[tag=description]
 include::interview-questions/max-subarray.js[tag=solution]
 ----
 
-The runtime is `O(n)` and space complexity of `O(1)`.
+The runtime is `O(n)` and the space complexity of `O(1)`.
 
 
 
@@ -90,11 +90,10 @@ Algorithm:
 
 [source, javascript]
 ----
-include::interview-questions/buy-sell-stock.js[tag=description]
-include::interview-questions/buy-sell-stock.js[tag=solution]
+include::interview-questions/buy-sell-stock.js[tag=description,solution]
 ----
 
-The runtime is `O(n)` and space complexity of `O(1)`.
+The runtime is `O(n)` and the space complexity of `O(1)`.
 
 
 
@@ -126,8 +125,7 @@ Another case to take into consideration is that lists might have different lengt
 
 [source, javascript]
 ----
-include::interview-questions/merge-lists.js[tag=description]
-include::interview-questions/merge-lists.js[tag=solution]
+include::interview-questions/merge-lists.js[tag=description,solution]
 ----
 
 Notice that we used a "dummy" node or "sentinel node" to have some starting point for the final list.
@@ -159,7 +157,7 @@ include::interview-questions/linkedlist-same-data.js[tag=hasSameDataBrute1]
 
 Notice that the problem mentions that lists could be huge (millions of nodes). If the first character on each list is different, we are unnecessarily computing millions of nodes, when a straightforward check will do the job.
 
-A better way to solve this problem is iterating over each character on both lists, and when we found mistmatch, we return `false` immediately. If they are the same, we still have to visit all of them.
+A better way to solve this problem is iterating over each character on both lists, and when we found a mismatch, we return `false` immediately. If they are the same, we still have to visit all of them.
 
 *Algorithm*:
 
@@ -172,12 +170,11 @@ A better way to solve this problem is iterating over each character on both list
 
 [source, javascript]
 ----
-include::interview-questions/linkedlist-same-data.js[tag=description]
-include::interview-questions/linkedlist-same-data.js[tag=solution]
+include::interview-questions/linkedlist-same-data.js[tag=description,solution]
 ----
 
 The function `findNextPointerIndex` is a helper to navigate each character on a linked list.
-Notice, that we increase the index (`i + 1`) on each iteration.
+Notice that we increase the index (`i + 1`) on each iteration.
 If the index overflows, it moves to the next node and reset the index to zero.
 
 
@@ -207,7 +204,7 @@ This is a parsing problem, and usually, stacks are good candidates for them.
 
 *Algorithm*:
 
-- Create a mapping for each opening bracket, to its closing counterpart.
+- Create a mapping for each opening bracket to its closing counterpart.
 - Iterate through the string
     - When we found an opening bracket, insert the corresponding closing bracket into the stack.
     - When we found a closing bracket, pop from the stack and make sure it corresponds to the current character.
@@ -267,6 +264,75 @@ The stack contains the indexes rather than the temperatures themselves.
 
 
 
+:leveloffset: +1
+
+=== Solutions for Queue Questions
+(((Interview Questions Solutions, Queue)))
+
+:leveloffset: -1
+
+
+[#queue-q-recent-counter]
+include::content/part02/queue.asc[tag=queue-q-recent-counter]
+
+We are asked to keep track of the request's count only within a given time window. A queue is a perfect application for this. We can add any new request to the	 Queue. Also, we need to check if the oldest element is outside the time window. If so, we remove it from the queue.
+
+*Algorithm*:
+
+- Enqueue new requests.
+- Take a `peek` at the oldest request in the queue.
+- While `current timestamp - oldest timestamp`, dequeue the oldest.
+- Return the length of the queue.
+
+*Implementation*:
+
+[source, javascript]
+----
+include::interview-questions/recent-counter.js[tag=description,solution]
+----
+
+Notice that we enqueue every request, and then we check all the ones that have "expire" and remove them from the queue.
+
+*Complexity Analysis*:
+
+- Time: `O(n)`, where `n` is the number of requests. One Enqueue/Dequeue operation is O(1). However, we might run into a worst-case where all requests have to be dequeued.
+- Space: `O(W)`, where `W` is the time window. We can have at most W requests in the queue since they are in increasing order without duplicates.
+
+
+[#queue-q-design-snake-game]
+include::content/part02/queue.asc[tag=queue-q-design-snake-game]
+
+This game is perfect to practice working with Queues. There are at least two opportunities to use a Queue. You can enqueue the food location, and also you can keep the snake's body parts on a Queue. We insert a new position into the snake's queue on every move and dequeue the last location to indicate the snake moved. Every time the snake eats food, it grows one more unit. The food gets dequeue, and we place the next food location (if any).
+
+*Algorithm*:
+
+- Based on the snake's head current position, calculate the next location based on the given move `direction`.
+- If the new position is outside the boundaries, it's game over (return -1).
+- If the new location has food, remove that eaten food from its queue and place the next food on the map (if any).
+- If the new position doesn't have food, remove the tail of the snake since it moved.
+- If the snake new position hits itself, game over (return -1). To make this check, we have 2 options:
+    - Queue: we can visit all the elements on the snake's queue (body) and check if a new position collides. That's `O(n)`
+    - Set: we can maintain a `set` with all the snake locations, so the check is `O(1)`.
+- Move the snake's head to a new location (enqueue)
+- Return the score (snake's length - 1);
+
+*Implementation*:
+
+[source, javascript]
+----
+include::interview-questions/design-snake-game.js[tag=description,solution]
+----
+
+As you can see, we opted for using a set to trade speed for memory.
+
+*Complexity Analysis*:
+
+- Time: `O(1)`. Insert/Remove from Queue is constant time. Check for body collisions is `O(1)` when using a set. If instead of a set, you traversed the snake's queue to find a collision, it would be `O(n)`.  Here`n` is the snake's max length, which is the size of the screen (height x width).
+- Space: `O(n + m)`. `m` is the number of food items, and `n` is the snake's maximum size (height x width).
+
+
+
+
 // [#linkedlist-q-FILENAME]
 // include::content/part02/linked-list.asc[tag=linkedlist-q-FILENAME]
 
@@ -293,4 +359,3 @@ The stack contains the indexes rather than the temperatures themselves.
 
 // - Time: `O(?)`. WHY?
 // - Space: `O(?)`. WHY?
-

book/content/part02/array.asc

@@ -276,13 +276,24 @@ To sum up, the time complexity of an array is:
 |===
 //end::table
 
-==== Interview Questions
+==== Practice Questions
 (((Interview Questions, Arrays)))
 
 // tag::array-q-max-subarray[]
 ===== Max Subarray
 
 *AR-1*) _Given an array of integers, find the maximum sum of consecutive elements (subarray)._
+
+Examples:
+
+[source, javascript]
+----
+maxSubArray([1, -3, 10, -5]); // 10 (taking only 10)
+maxSubArray([-3, 4,-1, 2, 1, -5]); // 6 (sum [4,-1, 2, 1])
+maxSubArray([-2, 1, -3, 4, -1, 3, 1]); // 7 (sum [4,-1, 3, 1])
+----
+
+_Seen in interviews at: Amazon, Apple, Google, Microsoft, Facebook_
 // end::array-q-max-subarray[]
 
 [source, javascript]
@@ -298,6 +309,18 @@ _Solution: <>_
 ===== Best Time to Buy and Sell an Stock
 
 *AR-2*) _You are given an array of integers. Each value represents the closing value of the stock on that day. You are only given one chance to buy and then sell. What's the maximum profit you can obtain? (Note: you have to buy first and then sell)_
+
+Examples:
+
+[source, javascript]
+----
+maxProfit([1, 2, 3]) // 2 (buying at 1 and selling at 3)
+maxProfit([3, 2, 1]) // 2 (no buys)
+maxProfit([5, 10, 5, 10]) // 5 (buying at 5 and selling at 10)
+
+----
+
+_Seen in interviews at: Amazon, Facebook, Bloomberg_
 // end::array-q-buy-sell-stock[]
 
 [source, javascript]

book/content/part02/linked-list.asc

@@ -286,16 +286,22 @@ Use a doubly linked list when:
 
 For the next two linear data structures <> and <>, we are going to use a doubly-linked list to implement them. We could use an array as well, but since inserting/deleting from the start performs better with linked-lists, we will use that.
 
-==== Interview Questions
-(((Interview Questions, Arrays)))
-
-
-
+==== Practice Questions
+(((Interview Questions, Linked Lists)))
 
 // tag::linkedlist-q-merge-lists[]
 ===== Merge Linked Lists into One
 
 *LL-1*) _Merge two sorted lists into one (and keep them sorted)_
+
+Examples:
+
+----
+mergeTwoLists(2->3->4, 1->2); // 1->2->2->3->4
+mergeTwoLists(2->3->4,null); // 2->3->4
+----
+
+_Seen in interviews at: Amazon, Adobe, Microsoft, Google_
 // end::linkedlist-q-merge-lists[]
 
 [source, javascript]
@@ -313,7 +319,17 @@ _Solution: <>_
 // tag::linkedlist-q-linkedlist-same-data[]
 ===== Check if two strings lists are the same
 
-*LL-2*) _Given two linked lists with strings, check if are the same_
+*LL-2*) _Given two linked lists with strings, check if the data is equivalent._
+
+Examples:
+
+----
+hasSameData(he->ll->o, hel->lo); // true
+hasSameData(hello, hel->lo); // true
+hasSameData(he->ll->o, h->i); // false
+----
+
+_Seen in interviews at: Facebook_
 // end::linkedlist-q-linkedlist-same-data[]
 
 [source, javascript]

book/content/part02/queue.asc

@@ -14,11 +14,11 @@ A queue is a linear data structure where the data flows in a *First-In-First-Out
 .Queue data structure is like a line of people: the First-in, is the First-out
 image::image30.png[image,width=528,height=171]
 
-A queue is like a line of people at the bank; the person that arrived first is the first to go out as well.
+A queue is like a line of people at the bank; the person who arrived first is the first to go out.
 
 Similar to the stack, we only have two operations (insert and remove). In a Queue, we add elements to the back of the list and remove it from the front.
 
-We could use an array or a linked list to implement a Queue. However, it is recommended only to use a linked list. Why? An array has a linear runtime _O(n)_ to remove an element from the start while a linked list has constant time _O(1)_.
+We could use an array or a linked list to implement a Queue. However, it is recommended only to use a linked list. Why? An array has a linear runtime _O(n)_ to remove an element from the start, while a linked list has constant time _O(1)_.
 
 .Queue's constructor
 [source, javascript]
@@ -56,15 +56,15 @@ As discussed, this operation has a constant runtime.
 
 ==== Implementation usage
 
-We can use our Queue class like follows:
+We can use our Queue class as follows:
 
 .Queue usage example
 [source, javascript]
 ----
 include::{codedir}/data-structures/queues/queue.js[tag=snippet, indent=0]
 ----
 
-You can see that the items are dequeued in the same order they were added, FIFO (first-in, first out).
+You can see that the items are dequeued in the same order they were added, FIFO (first-in, first-out).
 
 ==== Queue Complexity
 
@@ -81,3 +81,66 @@ As an experiment, we can see in the following table that if we had implemented t
 |===
 // end::table[]
 indexterm:[Runtime, Linear]
+
+
+==== Practice Questions
+(((Interview Questions, Queue)))
+
+
+// tag::queue-q-recent-counter[]
+===== Recent Counter
+
+*QU-1*) _Design a class that counts the most recent requests within a time window._
+
+Example:
+
+[source, javascript]
+----
+const counter = new RecentCounter(10); // The time window is 10 ms.
+counter.request(1000); // 1 (first request, it always counts)
+counter.request(3000); // 1 (last requests was 2000 ms ago, > 10ms, so doesn't count)
+counter.request(3100); // 1 (last requests was 100 ms ago, > 10ms, so doesn't count)
+counter.request(3105); // 2 (last requests was 5 ms ago, <= 10ms, so it counts)
+----
+
+_Seen in interviews at: Google, Bloomberg, Yandex_
+// end::queue-q-recent-counter[]
+
+
+[source, javascript]
+----
+include::../../interview-questions/recent-counter.js[tag=description]
+  // write you code here
+}
+----
+
+_Solution: <>_
+
+
+// tag::queue-q-design-snake-game[]
+===== Design Snake Game
+
+*QU-2*) _Design the `move` function for the snake game. The move function returns an integer representing the current score. If the snake goes out of the given height and width or hit itself the game is over and return `-1`._
+
+Example:
+
+[source, javascript]
+----
+const snakeGame = new SnakeGame(4, 2, [[1, 2], [0, 1]]);
+expect(snakeGame.move('R')).toEqual(0); //  0
+expect(snakeGame.move('D')).toEqual(0); //  0
+expect(snakeGame.move('R')).toEqual(1); //  1 (ate food1)
+expect(snakeGame.move('U')).toEqual(1); //  1
+expect(snakeGame.move('L')).toEqual(2); //  2 (ate food2)
+expect(snakeGame.move('U')).toEqual(-1); // -1 (hit wall)
+----
+
+_Seen in interviews at: Amazon, Bloomberg, Apple_
+// end::queue-q-design-snake-game[]
+
+[source, javascript]
+----
+include::../../interview-questions/design-snake-game.js[tag=description]
+----
+
+_Solution: <>_

book/content/part02/stack.asc

@@ -87,17 +87,26 @@ Implementing the stack with an array and linked list would lead to the same time
 It's not very common to search for values on a stack (other Data Structures are better suited for this). Stacks are especially useful for implementing <>.
 
 
-==== Interview Questions
-(((Interview Questions, Arrays)))
-
-
-
-
+==== Practice Questions
+(((Interview Questions, Stack)))
 
 // tag::stack-q-valid-parentheses[]
 ===== Validate Parentheses / Braces / Brackets
 
 *ST-1*) _Given an string with 3 types of brakets: `()`, `{}`, and `[]`. Validate they are properly closed and opened._
+
+Examples:
+
+[source, javascript]
+----
+isParenthesesValid('(){}[]'); // true
+isParenthesesValid('('); // false (closing parentheses is missing)
+isParenthesesValid('([{}])'); // true
+isParenthesesValid('[{]}'); // false (brakets are not closed in the right order)
+isParenthesesValid('([{)}]'); // false (closing is out of order)
+----
+
+_Seen in interviews at: Amazon, Bloomberg, Facebook, Citadel_
 // end::stack-q-valid-parentheses[]
 
 [source, javascript]
@@ -117,6 +126,16 @@ _Solution: <>_
 ===== Daily Temperaturs
 
 *ST-2*) _Given an array of integers from 30 to 100 (daily temperatures), return another array that for each day in the input, tells you how many days you would have to wait until a warmer temperature. If no warmer temperature is possible then return `0` for that element._
+
+Examples:
+
+[source, javascript]
+----
+dailyTemperatures([30, 28, 50, 40, 30]); // [2 (to 50), 1 (to 28), 0, 0, 0]
+dailyTemperatures([73, 69, 72, 76, 73, 100]); // [3, 1, 1, 0, 1, 100]
+----
+
+_Seen in interviews at: Amazon, Adobe, Cisco_
 // end::stack-q-daily-temperatures[]
 
 [source, javascript]