A Young Colleague Laughed: “Auntie, step aside, programmers are needed here, not cleaning ladies.” An Hour Later, He Was Submitting His Code to Me for Review
“Woman, where are you going? This is a work area, not the utility room.”
I stopped. A folder in my hand, a pass hanging around my neck. The third-floor corridor, glass partitions, and behind them—monitors, chairs, young faces. A guy in a bright hoodie with headphones around his neck stood in front of me, blocking the way. About twenty-five, no older. Trendy haircut, white sneakers, a confident look from above.
“Auntie, step aside. Programmers are needed here, not cleaning ladies.”
He said it loudly. Not in a whisper, not under his breath—in a full voice, across the whole corridor. Two guys at the nearest desk raised their heads. One snorted. The other looked away, but failed to hide his smile.
I could have answered. Twenty-three years in the profession had taught me how to answer in a way that leaves the other person choosing their words for a week afterward. But I didn’t. Silently, I walked around him, went down the corridor to the end, and sat at an empty desk by the window. I put down my folder. Took out a notebook—an ordinary paper one, squared. I wrote: “Kirill. Hoodie with logo. Headphones. First impression.”
He watched me go. I saw out of the corner of my eye as he turned to the guys and twirled his finger at his temple. As if to say: See that? Some auntie with a little notebook wandered into the IT department.
It was nine in the morning. The planning meeting was at ten.
For twenty-three years I have been writing programs. More precisely—code. Those very lines on a screen that later become websites, phone apps, online banking systems. I started in 2003, when half of these boys hadn’t even been born yet. I was twenty-five then—the same age as that guy in the hoodie now.
I bought my first computer with money I had saved for three months from my accountant’s salary. My husband at the time twirled his finger at his temple: a thirty-two-year-old woman, what courses? What programming? Go cook borscht.
I cooked borscht too. And at night I studied the language machines speak. Variables, loops, functions—it’s like words and sentences, only for a computer. Then I got a job at a small firm. Then another. Then a third. Twelve years at my last job—I grew into the head of a development team. A team lead is like a foreman on a construction site, only among programmers. I check what they have written. Without my approval, not a single line of code goes into production. If I find a mistake—you redo it. Simple as that.
The company closed in January. I spent three months unemployed. I sent out resumes—seventeen in March alone. I went to interviews. At five out of seven, they told me the same thing: “You have impressive experience, but we’re looking for someone younger.” Not exactly like that, of course. More politely. “We are focusing on a different candidate profile.” But the essence was the same—forty-eight years old in this profession sounds like a sentence. The average age there is twenty-seven. I am twenty years older than some managers.
Viktor Sergeyevich called me himself. Director of development, a large company, eighty people on staff. His voice was calm, solid.
“I need a team lead for a department of nine programmers. Not a boy fresh out of courses, but a person who knows what working code is. You were recommended. Two of your former trainees work here now.”
I started work today. My first day. A gray cardigan, hair tied back, no makeup. An ordinary forty-eight-year-old woman. With gray at her temples and a notebook in her hand.
And the first thing I heard at my new workplace was: “Auntie, step aside.”
At five to ten, people started entering the meeting room. I recognized the guy in the hoodie—Kirill. He sat in the far corner, sprawled in his chair, and took out his phone. The two guys who had laughed in the corridor sat next to him. Lena—thin, quiet, about thirty—settled by the wall and opened her laptop.
Viktor Sergeyevich entered last. Tall, wearing glasses, with a gray beard. He looked around at everyone and nodded to me.
“Colleagues. We have changed. Instead of Dmitry Olegovich, who left last month, the team will now be led by a new manager. For those who don’t know, the team lead accepts your work. Reviews code, assigns tasks, decides what is acceptable and what needs to be redone. Please welcome Nelli Arkadyevna Samsonova. Twenty-three years in development. For the last twelve, she led a team at Systempro. She built an online bank for three and a half million users.”
I stood up. Nodded. I looked around the room.
Kirill put his phone away. Slowly. Very slowly. He looked at me. Then at Viktor Sergeyevich. Then at me again. His ears turned pink. Not red yet—pink.
“Colleagues, questions?” Viktor Sergeyevich sat down.
I opened my notebook.
“Let’s get acquainted. Who does what, what tasks are in progress, where help is needed. We’ll go around the room. Name, project, current task.”
They introduced themselves one by one. Lena—server side of the system. Anton, twenty-eight, mobile app. Sergey, thirty-two, database—the place where all user information is stored. I wrote everything down in my notebook. Briefly, to the point. Name—project—current work.
Then it was Kirill’s turn. He cleared his throat. His voice was still confident, but his posture had changed—he was sitting upright now, no longer sprawled.
“Kirill. Frontend. I’m working on the user account.”
“Frontend is what an ordinary person sees on the screen,” I explained, although the explanation was more for the notebook, for order. “Buttons, forms, pages. The user account is where a person logs in with a username and password, changes settings, views history. Correct?”
Kirill nodded. Briefly.
“Deadlines?” I asked.
“Well, normal. In progress.”
“More specifically, please. By what date?”
He shrugged.
“By Friday, probably.”
“Good. I expect what is already ready today by five. For review. I want to see the current state.”
He smirked. Barely noticeably, with one corner of his mouth, but I saw it. And so did the two guys beside him. One of them—the one who had snorted that morning—leaned back in his chair.
The planning meeting ended. Everyone moved toward the door. I was gathering my notebook when I heard Kirill’s voice in the corridor. Not loud, but not a whisper either. He deliberately spoke so it could be heard—but so that later he could say, “I wasn’t talking to you.”
“She got placed here through connections. Did you see—the little notebook, the little pen. Like in accounting. Twenty-three years of experience, but dressed like a librarian. We’ll see how long she lasts.”
Someone laughed quietly.
Lena was standing by the water cooler. She heard everything. She looked at me. I turned back to the monitor.
Three times. Three times in half a day. The first—in the corridor, “Auntie, step aside,” with two witnesses. The second—the smirk at the planning meeting when I gave him a task. The third—“through connections” behind my back, but loudly enough for me to hear.
I opened the project code on the screen. I needed to understand what had already been written. My fingers settled on the keyboard—and I felt calmer. This was my territory. Age did not matter here. Only one thing mattered: whether it worked or not.
By five o’clock, Kirill sent his code for review. I opened the files. Twelve modules, a little over four hundred lines. The user account—the very page where a person logs into the site, changes their information, sees what they bought. Not the most difficult task, but one that requires care. Especially when it comes to security—because behind that page are real people with real passport data.
Kirill came over to my desk. Hands in his pockets, chin slightly raised. Headphones around his neck.
“I sent it. Everything works. Can I go?”
“Wait,” I said, scrolling through the code on the screen. “Sit down, please.”
He didn’t sit. He remained standing, shifting from one foot to the other.
The first error was found in the third minute. Incorrect password validation—the program allowed an empty field. It was like a door lock that opens if you simply pull the handle. No key. Anyone could enter someone else’s personal account without knowing the password.
“Here,” I pointed to the line. “The validation doesn’t trigger. A user can log in with an empty password. Do you understand what that means? A stranger enters your account and sees everything—name, address, card number.”
Kirill leaned toward the screen.
“Oh, yeah. A small thing, I’ll fix it later.”
“That is not a small thing. That is a door without a lock.”
The second error—the user data was being transmitted without protection. As if a letter containing passport details were sent not in an envelope, but on a postcard. Anyone could read it along the way.
The third—the same action had been written in four different places instead of one. As if, in a cooking recipe, the instructions “preheat the oven to one hundred eighty degrees” were printed four times—on every page. The program works more slowly because of it and breaks more often.
Fourth. Fifth. Sixth.
Kirill was silent. His ears were no longer pink—they were red. Bright red, like crayfish on a plate. He took his hands out of his pockets and crossed them over his chest.
Seventh error. The program did not check whether the user existed before showing him the page. Like a postman carrying a package to an address without making sure that such a house even exists. The package goes into emptiness. And the data—who knows where.
“Seven errors,” I closed the notebook. “In four hundred lines. Three of them critical. If this code had gone onto a real website, users’ personal data would have been lying out in the open.”
Kirill stood there. His arms were no longer crossed—they hung along his sides. His fingers were clenched into fists.
“I’ll fix it,” he said quietly.
“Of course you will. I expect the corrected version tomorrow by ten in the morning. All seven points.”
He turned around and left. Quickly, without looking back. He did not slam the door—he held it. But his back was rigid.
I leaned back in my chair. Unclenched my fingers—they ached. All day I had been gripping the pen from my notebook as if my life depended on it. My neck was stiff from tension. My shoulders felt wooden.
Lena came over and placed a glass of tea beside me.
“I googled you yesterday,” she said quietly. “At your last place, you built a system for a bank. For millions of users.”
“For three and a half million,” I corrected. “But thank you for the tea.”
She smiled slightly and left.
The tea was hot and sweet. I warmed my palms around the glass. The first warm feeling of the whole day. But it was too early to relax.
In the notebook, on the last page, in small handwriting: “He can do it. But he doesn’t want to. We’ll see tomorrow.”
The next morning, the code arrived at nine forty-seven. Thirteen minutes before the deadline. I opened the files and began checking. Four of the seven errors had been fixed. Three had not. And they were the most important ones. The very ones concerning security.
Kirill appeared at ten oh-five. His sneakers squeaked at the doorway.
“I sent it,” he threw out from the threshold.
“I see. Three errors remain. The exact ones I marked in red yesterday.”
“Everything is fine there. I checked.”
“No. It’s not fine. Sit down, I’ll show you.”
He sat down. I displayed his code on the large monitor. Line by line, I showed where the program was failing. I explained each point. In simple words, without humiliation, without mockery. The way you explain a difficult task to someone who can understand—if he wants to.
He did not want to.
“This is nitpicking,” he said. “At my last workplace, code of this level went through with no questions.”
“Then your last workplace had different requirements. Here, they’re mine.”
“Maybe your requirements are from the 2000s. Nobody works like that now.”
I looked at him. Calmly. Silently. Three seconds. Five. He did not look away, but he blinked—quickly, nervously.
“Kirill, security requirements are the same in 2003 and in 2026. A password must not be empty. User data must not travel without protection. This is not fashion. This is the foundation. Like the foundation of a house—without it, everything collapses.”
He stood up. The chair slid back sharply—the legs scraped against the floor.
“I’m going to write to Viktor Sergeyevich. You’re nitpicking because I greeted you wrong yesterday. This is personal.”
And he walked out. He did not slam the door. But his steps down the corridor were fast and angry.
I sat alone. The air conditioner hummed quietly under the ceiling. On the screen—his code with three red marks. My hands lay on the desk, palms down. Calm. But inside—there was a spring. The kind that tightens slowly, coil by coil. I had been tightening it for twenty-three years. For twenty-three years I had endured: “Grandma, you’re in the wrong place,” “Woman, this is serious work,” “Are you sure you wrote this yourself?”
I trained fourteen programmers over those years. Eight of them are now managers themselves. Two work here—that was why they recommended me to Viktor Sergeyevich. An online banking system for three and a half million people. Not a single failure in four years.
And a boy with two years of experience tells me I am nitpicking. Because I am a woman. Because I am forty-eight. Because I have gray hair at my temples and a cardigan instead of a trendy hoodie.
The email from Viktor Sergeyevich arrived an hour later.
“Nelli Arkadyevna, please come in. And call Kirill too.”
The development director’s office. A large desk, two chairs opposite it. A presentation screen on the wall. Viktor Sergeyevich took off his glasses and laid them on the desk. Rubbed the bridge of his nose.
“Kirill wrote that you are assessing his work with bias. A personal conflict, he says. That you are taking revenge for some morning misunderstanding. Kirill, do you confirm?”
Kirill sat upright. His voice was even, rehearsed.
“Yes. Yesterday she came into the department, I didn’t recognize her, I mistook her for a facilities employee. A normal mistake happens to anyone. And now she’s failing my code. Seven comments for four hundred lines—that’s not normal. The code works, I checked it myself.”
Viktor Sergeyevich looked at me over his glasses.
“Nelli Arkadyevna?”
“May I use your computer?”
He nodded. I moved to his laptop, opened Kirill’s code file, and put the first error on the wall screen.
“Here is the password check,” I said calmly, pointing to specific lines. “Look, Viktor Sergeyevich. I enter an empty field—nothing, not a single character. I press ‘Log in.’ And the system lets me inside. Into any user’s personal account. Without a password. Name, address, purchase history, phone number—everything exposed.”
Viktor Sergeyevich put on his glasses. Looked at the screen. Then at Kirill.
“This is not nitpicking,” I continued. “This is a hole through which someone can get into other people’s data. Kirill considers it a small thing.”
I showed the second error. Data without protection—a postcard instead of an envelope. The third—the program does not check who is in front of it before showing information. I explained each one simply, with examples. Slowly. Without anger. Without triumph. The way one shows an X-ray: here, and here, and here.
Viktor Sergeyevich removed his glasses. Put them on the desk. Quietly.
“Kirill, do you see this?”
Kirill was silent. His fingers were interlocked on his knees. His knuckles were white. His neck was red in blotches—unevenly, from the collar of his hoodie to his ears.
“Nelli Arkadyevna is right,” Viktor Sergeyevich said. “These are not nitpicks. These are security errors. If this code had gone onto a live site, we would have had serious problems. Very serious. Legal ones too.”
Kirill stared at the floor.
And then I said something I replayed in my head a hundred times afterward. Whether I should have or not—I still don’t know.
“Kirill,” my voice was even, quiet. I looked straight at the top of his head, because he wasn’t raising his eyes. “Yesterday you introduced me to the department. Publicly. In front of the whole corridor, you explained that programmers were needed here, not cleaning ladies. And then in the corridor you told the guys that I had been placed here through connections.”
He jerked his head up. His eyes were angry and frightened at the same time.
“If you want, I can arrange a public review for you. Do you know what that is? It’s when your code is put on the projector in front of the whole department. Nine people look at every line. And see empty passwords, unprotected data, and code you didn’t check yourself. How would you like that introduction to the team?”
One second. Two. Three.
Kirill unclenched his fingers. Then clenched them again. Said nothing.
Viktor Sergeyevich coughed.
“I think there is no need for that. Kirill, fix the code. Today. Nelli Arkadyevna—thank you, get back to work.”
We left. Kirill first. Quickly, without looking back. His sneakers squeaked along the corridor. I followed. Slowly. Closed the door. Leaned against the wall.
My hands were shaking. Not from fear. From what I had said. Out loud. In front of the boss. I had proposed a public dissection of the boy’s work in front of the whole department—mirroring what he had done to me yesterday in the corridor. An eye for an eye. Fair? Maybe. Right? I’m not sure.
He is a boy. Twenty-five years old. Two years of experience. Foolish, insolent, self-confident. But still a boy. I could have simply shown the errors and left. Without that phrase about a public review. Without the mirror. Professionally and dryly.
But I said it. And it hit exactly where I aimed.
Lena was standing by the coffee machine. She saw us come out. She looked at me—long and attentively. I straightened up. Pushed myself away from the wall. I walked to my desk.
By three o’clock, the corrected code was on my screen. All seven errors closed. Neatly, competently, cleanly. Kirill could write well. When he wanted to. Or when he understood that his work would actually be checked.
That evening, I sat alone in the empty office. Everyone had left. The monitor glowed blue. A glass of cooled tea stood beside me. The notebook was open on today’s page. Seven points—all crossed out. Fixed.
I finished the cold tea. And thought—was it necessary to do it like that? With a threat of public review? For twenty-three years I had built my reputation. Line by line. Sleepless night by sleepless night. Fourteen trainees. A system for millions. And one guy with headphones around his neck decided I was a cleaning lady. Because of age. Because of a cardigan. Because of gray hair.
No. I did not regret it. But there was no lightness either.
Two weeks passed. Kirill says hello now. Nods without looking me in the eye, squeezes out “good morning” through his teeth, but he says hello. He submits code on time. The errors became three, then two, then one. He is learning. Silently, without questions—but he is learning. I can see it in the code.
Only in the smoking area—Lena told me, I don’t go there myself—he says something else. That I am “asserting myself at the expense of young people.” That “they dragged in some auntie who ruined everyone’s life.” That “everything used to be normal here, and now every comma gets checked.” Half the department nods. They had gotten used to submitting code no one looked at. The other half stays silent and works. Their code has become cleaner. I can see that too.
And every morning I come in at nine. Sit at my desk. Open my notebook. The gray at my temples is still there. The gray cardigan is the same one—from the first day, and every day after. Twenty-three years behind me. Fourteen trainees. Three and a half million users who do not even know that their data was safe because one “auntie with a little notebook” checked every line.
And one question that will not let me go.
Did I go too far back then, in Viktor Sergeyevich’s office? With that public review—was it right, or too harsh? He is, after all, a boy. Foolish, but a boy.
Or was it right that I immediately made things clear—that here, people are not judged by age, but by results?
What do you think?