Fixing Someone Else's Code

Not even out of bed, Tommy, out of habit, reaches for his phone. In the chat with Tom2036 — a fresh picture.

— Ha, — Tommy snorts into his pillow. — A familiar scene.

I was the same, until the course knocked the habit of charging into everything at once out of me. Funny little gag about some other fool — they asked for one door, and he trashed the whole apartment. Tommy closes the chat and reaches for the laptop. There is work there, not comics about painters.

At work, Tony drops a task without much fanfare: in the launch portal there is a partner zone — a block of sponsors and partners — and there is a small thing that needs fixing in one place. Not a rewrite, not an improvement, just a fix to one specific thing. "Go in carefully, touch only this."

Tommy opens the file — and his hand with the mouse freezes. He stares at the screen for a second, then another. Scrolls up, scrolls down. And feels something unpleasant: he does not understand anything here at all. Not a single familiar foothold.

— What even is this, — he mutters aloud.

Before, he'd open his own file — and immediately be at home: here are the header styles, here is the button logic, this block depends on that one. But this bit was written by an external contractor, handed in, and long gone. The class names are somebody else's, the structure follows someone else's weird logic, the comments trail off halfway through a sentence.

Tommy runs his eye over the lines the way he is used to — diagonally. Trips on the first function.

— What do you even do? — he asks the function aloud. The name stays silent; you can't tell from it.

He reads it again. Fog. A line below looks redundant — or maybe everything depends on it. In his own code he'd know the answer; he wrote it himself. Here, every piece is a question mark, and not a single answer.

— Great, — he mutters at the screen. — They turned off the lights, and now I have to feel my way around.

— On the other hand, — he continues aloud. — If I don't understand anything, it doesn't mean Sam won't handle it...

And he forwards Tony's request to Sam: fix this here and that. But he sets no boundaries at all — hard to do that in code you don't understand. Sam gets to work, and Tommy disappears into the browser for a couple of minutes.

He comes back after 20 minutes — the needed fix is in place, everything is correct. Tommy is already about to say "done, commit it" when his eye catches that the diff is not three lines, as he expected. It's half a screen.

Tommy scrolls down. And more. The smile slides off.

Sam has reformatted half the file while at it: moved the indents to his own taste, neatened the neighboring chunks, changed some things "for aesthetics," and straightened the indentation everywhere. He even renamed a couple of functions. An entire block is shifted — supposedly tidier, but Tommy is no longer sure it was there for no reason. The real fix is drowning in this cosmetic work, like a needle in a haystack.

— Damn it, — he exhales. — I asked you for one thing.

And suddenly he recognizes what he's looking at. This is the same beast from last night's log — when the agent "while at it" rewrote the working module and everything quietly went sideways. Back then he was reading about it in someone else's log, after the fact, safely. And now that same accident is right before his eyes — and in someone else's code, where he doesn't even know which of the "neatened" bits was holding the layout together.

— In my own code I'd roll it back and forget about it, — he says out loud. — But here... — He jabs at the renamed function. — Where else are you even poking around? Who keeps tugging you? — The function stays silent. Whether it broke from the rename or not — impossible to tell.

His hand hangs over the keyboard. Roll everything back and go in again — a shame, because the needed fix has been made. Pick out the extra stuff by hand — but will he be able to tell extra from necessary in a file where half the names are empty noise? A simple task, but not something the autopilot can sort out: the autopilot is tuned to his own code, and this is someone else's.

He glances at the phone, where this morning there was a comic. A painter, one door — and an apartment trashed with the cat in it. This morning — a joke about someone else's fool. Now — his own screen.

Oliver, passing by, catches sight of that sprawling diff — and for the first time all month, doesn't grumble. He recognizes contractor code instantly: he used to dig through code like that himself. And instead of his usual snark, he says something unexpected:

— Listen, let me help. Without an experienced partner, it's easy to get burned here.

Tommy looks up. All month Oliver had only snorted at his "toys," kept his distance — but now he came over on his own, and not to mock, but to help. And on his own turf: not about agents and not about vibe, but about ordinary craft — how to understand in five minutes in someone else's file where the load-bearing pieces are, and where it's better not to poke at all. He spent years crawling through other people's code by hand, before there were any agents at all, and had to build the map in his head from scratch.

— Let's do it, — says Tommy. — I'm really sinking here.

— The first thing you did wrong just now, — Oliver says, nodding at the diff, — is you started too fast. In your own code, you can go quickly. Here — no. Speed here doesn't save time; it plants a mine.

Tommy doesn't argue. He just saw that mine with his own eyes. And for the first time today, he doesn't want faster — he wants slower and cleaner.