CompSci and My Day Job
summary
Builds an Elixir + Redis example and shows why the right Redis type matters: lists behave like stacks/queues (LPUSH/LPOP semantics), sets force full deserialization if you need single-item updates, and hashes give order one per-SKU lookups so cart updates are constant time. Demonstrates Postgres b‑tree indexes as a log N win (log2(1000) ≈ 10), warns how naive nested loops become N^2 or exponential (Fibonacci spikes to hundreds of seconds by n≈48), and describes caching results weekly to avoid deadly combinatorial work.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:03DATA STRUCTURES
- 11:19LET'S TRY A SET
- 27:47EFFICIENCY GAIN?
- 28:24CONSTANT TIME
- 29:44IN THE REAL WORLD
- 30:48EMBARRASSMENT
- 38:31EXPONENTIAL PAIN
- 44:57HANSELMAN'S FINGERS
- 47:06SIGNATURE PROBLEMS
- 49:26BRUTE FORCE
related talks
50mCompSci and My Day Job
53mStaying Ahead of the Curve
43mJust for Fun: Rediscovering Coding as a Hobby
28mBeyond the code: Rediscovering the timeless skills of software engineering in the AI era
31mCode to Joy
19mPanel: Elixir Adoption
26mBeyond the code: Rediscovering the timeless skills of software engineering in the AI era
01h 01mDown the Rabbit Hole: An Exploration of Stack Overflow Questions
