Big O And Complexity Analysis
Asymptotic analysis — time/space complexity, amortized analysis, the skill underlying every other folder here.
Why we need this / what value this brings
Without this, 'which data structure/algorithm' is guesswork instead of reasoned tradeoffs — and it's the first thing an interviewer probes when you propose a solution.
When to use this
Before choosing between two approaches to any problem, and any time you're asked to justify a solution's performance in an interview.
How to use or implement this
Practice stating Big-O for a solution out loud, unprompted, as you write it — not as an afterthought when asked.
Research questions
- Which of Localz's actual hot paths (booking search, dispatch matching) would benefit from a documented complexity budget?
Empty folder — drop notes, links, and findings here as you research.