The coolest part? Citation Mapping.

Because we track the research steps, we can link the output back to the source.

I used D3.js to visualize the "web of inspiration." You can see exactly which folklore blog post inspired your villain.

To stop the AI from generating a "wall of text," I enforce a strict JSON schema.

This acts as a contract. The AI must return structured objects for NPCs, Locations, and Plot Hooks.

No more rambling. Just usable data.

The "Secret Sauce" is Exa (Neural Search).

Google searches for keywords. Exa searches for concepts.

If I want "realistic dragon biology," Exa skips the movie reviews and finds niche biology forums.

We create a research task and return a taskId instantly.

I love digging into the "weird" parts of JavaScript.

Here is the classic "Predict the Output" game that trips up even Senior Developers during interviews.

What prints first? The Timeout (0ms) or the Promise?

🧵 Let's visualize the Event Loop. 👇

I interviewed with Big Tech and Startups in 2025.

The result? A widening gap that is breaking the hiring process.

We are moving from "Meritocracy" to "Pay-to-Win."

Here is the reality of LeetCode vs. Vibe Coding (and why it matters). 🧵

The PWA install prompt is pulling the default placeholder from a manifest.json file.

This is the digital equivalent of a professional painter leaving a "paint sample" swatch on a finished wall.

Here's the final "FastWidget" component.

It combines both techniques. It's blazing fast because it lets the browser do all the heavy lifting, and React just manages the simple container

While I'm waiting for Llama API access, you can already use it with @livekit.io!

So excited about what we're working at in my new job (it's a game changer for AI developers)! Getting the old recording gear ready to announce something really big in a new video, coming soon...