JavaScript is the only language where you can take a six-month sabbatical and come back to find that your entire tech stack has been deprecated, replaced, and then 're-imagined' as a Rust-based CLI tool
Caching can be a tricky topic, especially when pages don’t update the way you expect. I recently ran into a situation on my /writing page where new articles would not appear immediately, even though individual posts showed up instantly. Diving into Next.js caching taught me a lot, and I want to share what I learned so others can avoid the same confusion
Caching appears simple: store something once, reuse it later. In reality, caching introduces *time* as a dependency and time is one of the hardest things to reason about in systems.