Monolith extraction as code move
Leadership wants to extract the 'notifications' domain out of a Rails monolith into its own service, and proposes having an AI agent move the relevant classes and wire up an HTTP client where the in-process calls used to be. As the senior on the project, what's wrong with treating this as a code-move, and how do you scope the work and verify behavior is preserved?
Implement
settle_outbox(attempts: list[str]) → list[int]Examples
in
[["n1=ok","n2=timeout","n2=ok","n3=error"]]out[2,0,0,1]in
[["n1=ok","n1=ok"]]out[0,1,0,0]in
[[]]out[0,0,0,0]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 28 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.
Run or narrate your approach, then ask the coach.