Speed up NES emulator rendering pipeline (TypeScript + Rust)
Takeaway: Next time I'd give the agent something more concrete to profile against, since it couldn't watch my screen recording and had to guess where the slowdown was from code alone.
Stack · 6 sessions
napi sessions with coding agents
6 sessions on napi with a coding agent: the agent failed at least once in 1, and 3 finished without a human stepping in.
Explain pi-nes architecture audit findings
Takeaway: I'd ask for this same full trace-and-explain pass again since it worked well as-is — pointing the agent at the audit doc plus 'read everything referenced' got a thorough, evidence-backed walkthrough without needing any correction.
Build automated test suite for pi NES emulator extension
Takeaway: Next time I'd start by telling the agent explicitly which ROMs I actually care about and that I want tests tied to real gameplay symptoms (freezes, missing sprites) rather than emulator-accuracy test suites like blargg/nestest.
Audit pi-nes codebase, plan refactor, and diagnose Mario freeze regression
Takeaway: Next time I'd start by asking directly for a refactor plan scoped to 'simple, non-duplicative, not excessively defensive' rather than getting a generic audit first and then having to talk it back down to size.
Research CRT/NTSC filtering for pi-nes terminal NES emulator
Takeaway: Next time I'd ask upfront for both the research and a concrete GitHub issue in one go, since the agent handled the investigation (codebase read, web research on Blargg's nes_ntsc and TetaNES) well without any correction needed from me.
Explore a multi-extension Pi TypeScript repo
Takeaway: I'd start by pointing the agent straight at the extensions I care about instead of letting it read every README and package.json in the repo — most of that breadth wasn't needed for a first pass.