Debug silent ASR failure in Gradio read-along app
Takeaway: Next time I'd paste the log and ask directly for exception logging around the ASR wrapper instead of first asking 'what's happening,' since that's exactly what we ended up doing anyway.
Takeaway: Next time I'd paste the log and ask directly for exception logging around the ASR wrapper instead of first asking 'what's happening,' since that's exactly what we ended up doing anyway.
Takeaway: Next time I'd flag the .gitignore rule on .hackathon/submission up front so the agent checks tracked status before writing handoff files there, since I nearly lost those prompts silently.
Takeaway: Next time I'd bundle the doc-consistency check into the original implementation prompt instead of asking for it separately, since the docs drift as soon as behavior changes.
Takeaway: Next time I'd lead with the Space's hard constraints (1GB repo limit, free-tier build memory, no CUDA) before letting the agent draft a plan, since two of our failures were pure packaging/build issues we could have anticipated upfront.
Takeaway: Next time I'd start by telling the agent explicitly not to commit anything without asking, since it committed twice before I stepped in to stop it.
Takeaway: Next time I'd start by asking for a ground-truth labeling workflow and benchmark harness before building any alignment logic, since that's what actually let us tell good methods from bad ones.
Takeaway: Next time I'd specify upfront that word clips must not bleed into adjacent words, since that was the real bug hiding behind 'alignment isn't better' — the fix was clamping word end to the next word's start plus much smaller padding for aligned clips versus the proportional fallback.
Takeaway: Next time I'd open with the fact that TTS needs to work instantly for a kid clicking words, not just eventually — that would have surfaced the Modal cold-start problem before I burned time on Gradio 6 launch-arg compatibility.
Takeaway: Next time I'd ask for the environment sanitization (Conda vs .venv Torch conflicts) to be handled up front, since that same libtorch_python.so issue bit me twice, once during GGUF conversion and again during local_inference.py testing.