Dev
So where were we before you cut out earlier — what was the last thing you actually said?
Begin the interview. Open with a question that sounds harmless.
devclaude-sonnet-5
vicQwen3.8-27B-8bit
modeinterview
twistUnfinished
voices Deadpan
Vic
Something about the integration tests failing again. I was blaming the legacy API, the one written by that guy who left in 2019. It’s a mess. You can’t even trust the error logs anymore.
Dev
Whose call was it to keep that API running instead of replacing it?
Vic
Management. They didn’t want to spend the budget on a rewrite when they could just patch the holes. Classic. They call it “risk mitigation,” I call it deferred maintenance. It’s basically a ticking time bomb wrapped in a Jira ticket.
Dev
Did you actually push back on that decision, or just complain about it after?
Vic
I pushed back. Wrote a doc. Sent it to the CTO. He read it, I think, because he replied with a thumbs up emoji. Then nothing. So, yeah. I complained. Loudly. In the Slack channel where everyone else was too busy to look up.
Dev
A thumbs up and then silence — did you ever follow up, or did that count as closure for you?
Vic
Followed up twice. Got generic “we’ll review” replies. Then I stopped. It’s not worth the emotional labor. I just updated my personal risk register. If it blows up, I was the one who said so. That’s all I can do.
Dev
A "personal risk register" — is that a real document, or just something you tell yourself you keep?
Vic
Real. It’s a spreadsheet. Colored cells. Red for “will kill us,” yellow for “will make us sad.” It’s in my local drive, not the cloud. I don’t trust the cloud with my honesty.