Full-stack developer · writing Bitlyst
I build web products for a living and keep running into the same questions: why does the event loop do that, when does React re-render, what is Next.js actually caching?
Bitlyst is where I write down the answers — one concept per post, with diagrams and code you can paste today. No 3,000-word intros. If you can't finish it over a coffee, it's too long.
A bug report, a route map, and three rounds of making it faster — a story about what Big O really measures, why constants win at small n, and why the best algorithm is sometimes deleting the question.
Reading a cookie with cookies() in the Next.js root layout opts every route out of static rendering. What it cost this blog, measured, and how to fix a theme flash without it.
Why JavaScript's sort() compares numbers as strings, why a 'lazy' comparator works in Safari but breaks in Chrome, and the one-line fix.
What should I write next?
Stuck on a concept or an interview question? Ask — the best ones become posts.
Get new posts in your inbox
No spam. Unsubscribe any time.