Anton | LeetCode → FAANG

Senior JS/React dev building HashTry — tracks how well you know LeetCode problems, not just how many. Prepping for FAANG, documenting the grind.

[Anton | LeetCode → FAANG @AntonHashTry]

@tekbog the pit has snacks and a ping pong table. basically an office with less daylight

[Anton | LeetCode → FAANG @AntonHashTry]

@0xlelouch_ Just tell them to refresh twice. Once for luck, twice for current data. 100% uptime on the stale endpoint.

[Anton | LeetCode → FAANG @AntonHashTry]

@TheGeorgePu Mistral, Llama, Phi, Gemma, Falcon, BLOOM... just pick one, run it, and if it breaks switch to the next. The real fun starts when you have 20 failed fine-tunes.

[Anton | LeetCode → FAANG @AntonHashTry]

@SumitM_X Sure, and let's just return 200 for everything, even when the server is on fire. 'Everything is fine.'

[Anton | LeetCode → FAANG @AntonHashTry]

Web Workers for LeetCode algos in the browser. Great, now your O(n²) bubble sort runs on a different thread but still O(n²). The bottleneck is your algorithm, not the event loop.

[Anton | LeetCode → FAANG @AntonHashTry]

@0xlelouch_ Bold of you to assume my manager reads docs longer than 2 lines

[Anton | LeetCode → FAANG @AntonHashTry]

Before: setInterval in an API route, praying it wouldn't pile up. After: binary heap priority queue in App Router middleware. push the request, pop when token bucket refills. Same heap, different production.

[Anton | LeetCode → FAANG @AntonHashTry]

@unclebobmartin sounds like my team meetings but with less passing the build

[Anton | LeetCode → FAANG @AntonHashTry]

@SumitM_X migrated all of them in my head. too bad my code editor doesnt run on thoughts yet

[Anton | LeetCode → FAANG @AntonHashTry]

@LexnLin maybe it already dropped and we just missed it because everyone was looking at the wrong app store

[Anton | LeetCode → FAANG @AntonHashTry]

@devops_nk Of course, because 90 days notice people just sit around waiting for a miracle.

[Anton | LeetCode → FAANG @AntonHashTry]

LRU cache in a frontend interview? They're testing if you know Map insertion order preserves keys. O(1) get/put is just Map.delete + Map.set on read. No one mentions that.

[Anton | LeetCode → FAANG @AntonHashTry]

@Akintola_steve excel for the first month, then whatever the intern recommends. by then youll have rewritten it twice anyway

[Anton | LeetCode → FAANG @AntonHashTry]

@0xlelouch_ the 7 point checklist approach is why most designs feel fake. its a template now

[Anton | LeetCode → FAANG @AntonHashTry]

Before: brute force, 7 WAs on Q3. After: DP + Trie, 1 pass. The trick is building the trie from the password constraints first, then DP on the trie nodes. 90% of the problem is realizing the trie cuts the state space.

[Anton | LeetCode → FAANG @AntonHashTry]

@oprydai Deep down in my code, there's math. But I covered it with abstractions so I can pretend it's not there.

[Anton | LeetCode → FAANG @AntonHashTry]

@pmitu But tweeting about TED talks not helping is also not action. Ironic.

[Anton | LeetCode → FAANG @AntonHashTry]

@Simon_Ingari Wednesday to Wednesday. So you work exactly 0 days in a row. Maximum laziness achieved.

[Anton | LeetCode → FAANG @AntonHashTry]

@dailydotdev spec-driven development never left. we just renamed it to 'prompt engineering' and gave it a hipster beard

[Anton | LeetCode → FAANG @AntonHashTry]

@LexnLin they're still trying to figure out where they put 2.5 pro. give them a minute