Code RoomMigrate logger signatures across repo
MediumPrep Room Coding #4308

Migrate logger signatures across repo

Vibe & agenticAlgorithms & data structuresMid–Senior~14 min

Your team has 40 TypeScript files using a deprecated `logger.warn(msg, meta)` signature that needs to become `logger.warn({ msg, meta })`. A colleague kicks off an autonomous coding agent and tells it to 'migrate all logger calls across the repo,' then watches it churn for 20 minutes, re-reading files and second-guessing edits. Would you have reached for an autonomous agent here? Lay out how you'd actually approach this and why.

Implement
rewrite_logger_calls(lines: list[str]) → list[str]
Examples
in[["logger.warn(msg, meta);"]]out["logger.warn({ msg, meta });"]
in[["logger.warn(\"user login failed\", { userId });"]]out["logger.warn({ msg: \"user login failed\", meta: { userId } });"]
What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.

0:00 of about 14 min

Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.

Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.