Micro Sessions
Aug 15, 2025
1.”不推开痛苦”
2.”唯手熟尔”。。。
No. | - |
---|---|
2 | |
17 | |
20 | |
21 | |
23 | |
24 | Swap Nodes in Pairs |
26 | |
27 | |
28 | |
46 | |
58 | |
67 | |
77 | |
78 | |
79 | |
80 | |
92 | |
98 | |
100 | |
101 | |
109 | |
125 | |
129 | |
133 | |
141 | |
151 | |
173 | |
189 | ~~Rotate Array |
199 | |
206 | |
392 | |
547 | |
1020 |
System Design, CAP trade-off???
No. | - |
---|---|
0 | API gateway… etc. |
1 | |
2 | |
3 | |
4 | Video Platform, like Youtube, etc… scalibility etc. |
5 | |
6 | |
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 | |
10 | Key-Value, think about the gossip protocel, and CAP |
Resources,
Two books, from Alex Xu, I had read them already,
System Design Interview – An insider’s guideSystem 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,
https://highscalability.com/https://github.com/donnemartin/system-design-primer/tree/master- https://github.com/Jeevan-kumar-Raj/Grokking-System-Design
Database scaling solution,
- Concepts:
master-slave replication, master-master replication, federation, sharding, denormalization, and SQL tuning.
APIs and OO Design,
- https://github.com/tssovi/grokking-the-object-oriented-design-interview
- https://github.com/ashishps1/awesome-low-level-design
- https://github.com/ByteByteGoHq/ood-interview
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.”