Build a self-verifying Boeing 747 and full airport in Three.js
Takeaway: Next time I'd specify up front that I want a technical showcase, not a cinematic trailer — that would have saved a couple of rounds of camera direction back-and-forth.
Takeaway: Next time I'd specify up front that I want a technical showcase, not a cinematic trailer — that would have saved a couple of rounds of camera direction back-and-forth.
Takeaway: I'd open with the HF Space compatibility question up front next time, since that's what actually gated the refactor — asking 'will this still deploy' before greenlighting the extraction was the right move.
Takeaway: I'd clarify upfront that our HF Space remote is named 'origin' not 'hf', since the agent had to figure that out itself.
Takeaway: Next time I'd start the session by asking the agent to check both Modal deployments end-to-end (health + authenticated /chat) before I go poking at env var naming one variable at a time, since most of the friction was just me and the agent working through STORY_FORGE_API_KEY vs MODAL_API_KEY confusion.