1.”不推开痛苦”
2.”唯手熟尔”。。。

No. -
2 Add Two Numbers
17 Letter Combinations of a Phone Number
20 Valid Parentheses
21 Merge Two Sorted Lists
23 Merge k Sorted Lists
24 Swap Nodes in Pairs
26 Remove Duplicates from Sorted Array
27 Remove Element
28 Find the Index of the First Occurrence in a String
46 Permutations
58 Length of Last Word
67 Add Binary
77 Combinations
78 Subsets
79 Word Search
80 Remove Duplicates from Sorted Array II
92 Reverse Linked List II
98 Validate Binary Search Tree
100 Same Tree
101 Symmetric Tree
109 Convert Sorted List to Binary Search Tree
125 Valid Palindrome(…isLetterOrDigit)
129 Sum Root to Leaf Numbers
133 Clone Graph
141 Linked List Cycle
151 Reverse Words in a String
173 Binary Search Tree Iterator, in-order traversal
189 ~~Rotate Array
199 Binary Tree Right Side View
206 Reverse Linked List
392 Is Subsequence
547 Number of Provinces, why the recursive search is slow, think about this…
1020 Number of Enclaves, stuble difference for similar questions… etc

System Design, CAP trade-off???

No. -
0 API gateway… etc.
1 Consistent Hashing
2 News Feeds, solve the pressure for fanout service.
3 Chat System, sender protocol vs. receiver… 1-1, groups, inbox queue, etc… why?
4 Video Platform, like Youtube, etc… scalibility etc.
5 A Web Crawler, avoid redundant request, think about the usage of this…
6 Real-time Gaming Leaderboard, why Redis?
7 Hotel Reservation System
8 Design the data structures for a social network, how to composite a cluster, by yourself, also how to handle metainfo?
9 Ad Click Event Aggregation, high volume stream/big data orientated
10 Key-Value, think about the gossip protocel, and CAP
11 (OO-design) Parking Lot
12 (OO-design) Linkedin

Resources,

Two books, from Alex Xu, I had read them already,

  • System Design Interview – An insider’s guide
  • System Design Interview – An Insider’s Guide: Volume 2

Especially, some classic example in V2, I had never thought about how to design those systems.

Reference papers in books, also good to read,

… etc… // TODO. 1.collect some diagrams to help re-fresh later, 2.the following section, get some classic papers to read,

… 1.
… 2.
… N. it’s not just for interview sessions, but to help me understand what’s going on in systems,

Github repos and websites,

Database scaling solution,

  • Concepts: master-slave replication, master-master replication, federation, sharding, denormalization, and SQL tuning.

APIs and OO Design,

Feedbacks, where is the attention I should put,

  • OO-design, seems this part is which I should put more focus.
  • Some funcions, classes, definition/template, should be more flexible to extend.
  • Speak/think aloud, otherwise others don’t know how to help.
  • from other’s blog, “some of the factors that are considered in your code are: creating different classes for different responsibilities following SRP, creating objects of classes and using object-oriented programming to call the respective methods, having good naming conventions for variables and methods, having proper indentations that make the code readable, etc.”