The doubt from yesterday lingered like a hangover. I sat at my desk, staring at the CodeForge icon, the question still echoing in my mind: What if I can't think anymore? The morning light filtered through the office windows, casting long shadows across the floor, and I felt the weight of the question pressing down on me like a physical thing. I'd barely slept. The realization from the day before, that I couldn't solve a simple bug without AI, had followed me home, had sat beside me at dinner, had kept me awake long past midnight. Every time I closed my eyes, I saw that blank editor, that blinking cursor, that terrifying void where my thoughts should have been. But as I watched my colleagues begin their day, I noticed something. The developer to my left had a chat open with an AI assistant, the familiar interface glowing on his screen. The one across the aisle was copying code from a suggestion, her fingers moving in that quick, efficient rhythm I'd come to recognize. Even Sarah, who'd always been skeptical of new tools, was using AI to generate test cases, her screen filled with the characteristic output of machine-generated code. Not just some people, everyone. The entire office was humming with the quiet productivity of AI-assisted work. Prompts being typed, responses appearing, code being copied and committed. The sound of it had become background noise, as natural as the hum of the HVAC or the distant rumble of traffic. Maybe I'm overthinking this, I told myself. Maybe this is just... normal. The thought was a relief, a door opening onto a less frightening path. I wasn't broken. I wasn't losing my mind. I wasn't some cautionary tale about technology rotting brains. I was just adapting to a new reality, the same as everyone else. The panic from yesterday seemed suddenly excessive, the doubt overblown. This was the future of work. This was what progress looked like. This was what being a modern engineer meant. I opened CodeForge, typed my first prompt of the day, and watched the code appear. The question from yesterday faded, replaced by the comfortable rhythm of productivity. I was fine. I was just being efficient. That was all. --- The team standup that morning was unremarkable, the usual round of updates and blockers. Jennifer stood at the front of the room, her tablet displaying the sprint board, her voice carrying that practiced enthusiasm that made every meeting feel like a sales pitch. But something was different in how people talked about their work. "I used CodeForge to refactor the legacy module," Mike said, his tone casual, like he was mentioning the weather. "Saved about three hours. The code came out cleaner than what I would have written manually." "I had it write the documentation for the new API," Sarah added. "Actually came out pretty good. Just needed a few tweaks here and there. Way better than staring at a blank page for two hours." "Same here," another developer chimed in from across the room. "I'm using it for everything now. Why would you do it the hard way? That's like refusing to use a calculator because you want to do long division by hand." There were nods around the room, murmurs of agreement. The comparison struck me, calculators. We'd all grown up hearing that argument, that tools were just tools, that using them didn't make you weaker, only more efficient. And it was true, wasn't it? Nobody thought less of an accountant because they used Excel instead of paper ledgers. Nobody criticized an architect for using CAD software instead of drafting by hand. The words hung in the air, and I felt something shift inside me. This wasn't just me. This was everyone. The entire team was using AI, relying on it, depending on it. And no one seemed worried. No one seemed to think they were losing anything. No one was lying awake at night wondering if they could still think. So why should I? The question felt liberating. I'd been torturing myself over something that was completely normal. Everyone used AI. Everyone let it do the heavy lifting. That was the point, that was what it was for. I wasn't weak or dependent or broken. I was just... modern. I was just doing what everyone else was doing. After the standup, I walked back to my desk with a lighter step. The doubt from yesterday seemed distant now, a bad dream that had faded in the morning light. I was overthinking. I was being dramatic. This was fine. Everything was fine. --- Around mid-morning, I found myself in the break room, pouring coffee into my travel mug. The space was quiet, most people still at their desks, riding the wave of morning productivity. Sarah was there, scrolling through her phone, a distracted look on her face that I'd come to recognize as the expression of someone mentally debugging code. "Hey," I said, settling into the chair across from her. "How's it going?" She looked up, smiled automatically. "Good. Busy. You know how it is." She set her phone down, giving me her attention. "How about you? You seemed a little off yesterday. Everything okay?" The question caught me off guard. I hadn't realized anyone had noticed. "Yeah, I'm fine. Just... a weird morning. The AI service was down for a few hours." "Oh, that." She nodded sympathetically. "I heard about that. Sucks, right? It's like losing power or something. You don't realize how much you depend on it until it's gone." The words landed differently than she probably intended. You don't realize how much you depend on it until it's gone. That was exactly what I'd been feeling. That was exactly the thought that had kept me awake. "Can I ask you something?" I said, the words coming out before I could stop them. "Sure." She leaned back in her chair, coffee cup in hand. "Do you ever... I don't know. Do you ever worry about using AI too much? Like, depending on it? Losing something?" Sarah's expression flickered, something I couldn't quite read. A brief hesitation, quickly covered. Then she laughed, a short, dismissive sound that felt slightly forced. "Worry about it? Why would I worry about it? It's a tool. Like Stack Overflow. Like my IDE. Like Google. I use whatever helps me get the job done." "Yeah, but..." I hesitated, trying to find the right words without sounding crazy. "Don't you ever feel like you're not... thinking? Like the AI is doing the work for you? Like you're just the middleman between the prompt and the code?" She looked at me strangely, her head tilting slightly. "Marcus, I'm a software engineer. My job is to solve problems. If AI helps me solve problems faster, that's a good thing. The thinking is still mine, I'm just not wasting it on boilerplate. I'm focusing on the interesting stuff, the architecture, the design decisions." "But what if..." I stopped, unsure how to finish the sentence. What if the interesting stuff becomes boilerplate too? What if you forget how to think through anything? What if you become dependent without realizing it? "Look," Sarah said, her tone gentle but firm. "I've been doing this for ten years. I've seen a lot of tools come and go. IDEs, linters, testing frameworks, CI/CD pipelines. Each one made us more productive. Each one took away some tedious task we used to do manually. That's not dependency, that's progress. AI is just the next step." The answer was reasonable. It was the same thing I'd told myself a hundred times. But something in her tone made me wonder if she'd ever asked herself the question I was asking. If she'd ever felt that moment of blankness, that terrifying void where her thoughts should be. If she'd ever tried to work without AI and found herself unable to. "Right," I said. "Yeah. That makes sense." She stood, gathering her coffee cup. "Don't overthink it. We're all just doing our jobs. If the tools help, use them. That's what they're for." She paused at the door. "And Marcus? You're doing great. The metrics don't lie. You're one of the top performers on the team. Don't let imposter syndrome mess with your head." I watched her walk away, the conversation replaying in my mind. She was right. Of course she was right. This was just how things worked now. The old way of doing things, struggling through every problem, thinking through every line of code, that was the past. This was the future. And I was good at it. The metrics proved it. Jennifer's praise proved it. My position on the leaderboard proved it. So why did I still feel that nagging doubt? That afternoon, I found myself watching David. He sat at his desk, hunched over his keyboard, typing slowly. His brow was furrowed in concentration, the familiar look of someone wrestling with a difficult problem. Beside him, a stack of printed documentation sat half-read, covered in handwritten notes and highlighted passages. His whiteboard was covered in diagrams, arrows connecting concepts in a web of thought that he'd built himself, line by line, connection by connection. He was still doing it the old way. Still thinking through every problem. Still refusing to use the tools that everyone else had embraced. Still believing that the struggle was part of the process, that understanding came from effort, that the mind was something to be exercised, not outsourced. And he was struggling. I could see it in the tension of his shoulders, the frustrated exhales, the way he'd stare at his screen for long minutes without typing. I could see it in the growing stack of unfinished tickets, the missed deadlines, the increasingly frequent conversations with Jennifer that left him looking defeated. His productivity had dropped. His metrics were at the bottom of the leaderboard. His career was stalling while everyone else's was accelerating. Meanwhile, I was flying. My tickets were closing in record time. My metrics were climbing. Jennifer had praised me in front of the team twice this week alone. I was being positioned as a leader, a model, an example of what success looked like in the AI era. I was winning. This is the right choice, I told myself, watching David struggle. He's the one who's wrong. He's the one who's falling behind. He's the one who refuses to adapt. But even as I thought it, I remembered the morning two days ago, the panic, the blankness, the terrifying realization that I couldn't think without AI. David had never had that moment. David could still solve problems on his own. David still had something I'd lost, something I'd traded away for productivity and metrics and praise. I pushed the thought away. It didn't matter. What mattered was results. What mattered was productivity. What mattered was staying ahead, keeping my position, proving my value. The company didn't care how I solved problems, only that I solved them. The metrics didn't measure thinking, they measured output. And my output was good. Better than good. It was excellent. By the end of the day, I had successfully buried the question. I had rationalized, justified, and dismissed. I had compared myself to others and found myself not just normal, but ahead. I had watched David struggle and felt validated in my choice. I had talked to Sarah and heard the same things I'd been telling myself. I had returned to the comfortable rhythm of AI-assisted work, and the doubt had faded to a distant whisper. But the question was still there, buried deep, waiting. It would come back. It always comes back. Questions like that don't stay buried forever. For now, though, I was fine. I was productive. I was successful. I was in control. I closed my laptop and stood, stretching muscles stiff from hours of sitting. The office was emptying, the usual evening exodus. Tomorrow would be another day of prompts and responses, of problems delegated and solutions accepted. The comfortable, seductive ease of not having to think. I walked toward the exit, passing David's desk. He was still there, still working, still thinking. For a moment, I felt a pang of something, envy, maybe, or respect. He still had what I'd given up. He could still do what I couldn't. He was still whole in a way I wasn't sure I was anymore. But the moment passed. I had a train to catch, and tomorrow was going to be another productive day. The question was safely buried under layers of rationalization and productivity and the comfortable, seductive ease of not having to think. At least for now. Word Count: 2,318
The morning started like any other. I arrived at the office, opened my laptop, and began my AI-assisted workflow. The rationalization from yesterday had settled into a comfortable certainty, a warm blanket I could wrap around myself whenever the doubt threatened to surface. I was fine. Everyone used AI. This was just how things worked now. The question that had haunted me for days was safely buried, covered by layers of productivity and the quiet hum of the office around me. My metrics were good. My tickets were closing. Jennifer had praised me in the team meeting just yesterday, holding me up as an example of what "AI-native engineering" looked like. I was winning. I was succeeding. I was exactly what the company wanted me to be. But around noon, I noticed something different. Hushed conversations. Worried glances. The particular tension that always preceded bad news, the kind of atmosphere that made everyone look up from their screens, suddenly aware that something was wrong. I'd been in enough reorgs and layoffs to recognize the signs. The way people clustered in corners, speaking in low voices, their eyes darting around the room. The way managers walked quickly between meetings, their faces carefully neutral, their footsteps just a little too fast. The way the usual office banter had been replaced by a nervous silence that felt like holding your breath. "Did you hear?" someone whispered as they passed my desk. It was Mike, his expression tight with concern, his voice pitched low enough that only I could hear. "There's going to be layoffs. Today. This afternoon, I think." I felt a cold knot form in my stomach, a familiar dread that I'd felt three times before in my five years at Nexus. Layoffs. The word hung in the air like a threat, like a storm cloud on the horizon, dark and inevitable. "Who?" I asked, though I wasn't sure I wanted to know. Mike shook his head, his eyes scanning the room nervously. "Don't know specifics. But Jennifer's been in meetings all morning. HR is here, I saw them come in around eleven. You know what that means." I did know. I'd been through this before. The closed doors, the hushed voices, the boxes in the hallway. The sudden empty desks that used to belong to people you'd worked with for years, now cleared out overnight, their existence erased as if they'd never been there. The company had done layoffs before, it was practically a quarterly tradition at Nexus, part of the "optimization" cycle that kept the numbers looking good for investors, the headcount lean, the shareholders satisfied. But this time felt different. This time, there was a new metric in play. --- The afternoon stretched on, tense and watchful. Everyone was waiting, wondering who would be called, who would disappear. The usual rhythm of the office had been disrupted, replaced by a kind of collective holding of breath. People typed at their keyboards, but their eyes kept drifting to Jennifer's office door, to the HR representatives who moved through the space like ghosts, to the faces of their colleagues, searching for clues. I tried to focus on my work, typing prompts into CodeForge, watching the code appear, but my mind kept drifting. The leaderboard was still up on the dashboard, names and numbers ranked in order of productivity. My name was at the top, a steady climb of green numbers showing my ever-increasing output. David's was at the bottom, a flat red line that barely registered above zero. The connection was impossible to ignore. They're measuring us, I thought, the realization crystallizing with sudden clarity. They're ranking us. And the people at the bottom... I didn't want to finish the thought. Didn't want to acknowledge what I already knew. The company had made its priorities clear from the beginning. AI adoption wasn't optional. Productivity wasn't just encouraged, it was required. And those who couldn't or wouldn't keep up... I looked at David's desk, across the open-plan office. He was working, as always, his brow furrowed in concentration, his fingers moving slowly over the keyboard. He didn't seem to notice the tension in the room, or maybe he was ignoring it. Maybe he'd made his peace with whatever was coming. Around 2:30, Sarah stopped by my desk, her expression grim. "Have you talked to David today?" I shook my head. "No. Why?" "Someone should." She glanced across the room at his desk, then back at me. "He's been struggling for weeks. I think he knows what's coming." "What do you mean?" "Come on, Marcus. You've seen the metrics. You've seen the meetings with Jennifer. You've seen the way she looks at him during standups." She lowered her voice further. "He's not using AI. He's not hitting his numbers. In this environment, that's..." She didn't finish the sentence. She didn't have to. "I should talk to him," I said, though I wasn't sure what I'd say. Sorry you're about to get fired because you have principles? Sorry I'm part of the system that's destroying you? But before I could move, Jennifer's door opened. --- At 2:47 PM, Jennifer stepped out of her office. Her face was composed in that corporate mask that revealed nothing, the same pleasant, professional expression she wore in every meeting, every conversation, every difficult discussion. But there was something in her eyes, a hardness I'd seen before, that told me everything I needed to know. She walked toward David's desk. The office went quiet. Everyone knew what was coming. "David, can you come to my office for a moment?" Her voice was pleasant, professional, the same tone she used for every conversation. But we all knew what it meant. The closed-door meetings. The HR representative waiting inside. The box that would be provided for personal belongings. The end of a career. David looked up from his screen. For a moment, I saw something flash across his face, surprise, maybe, or resignation, or the particular expression of someone who'd been expecting this moment but still wasn't ready for it. Then he nodded, stood slowly, and followed Jennifer down the hall. His desk lamp was still on, casting a warm glow over his workspace. His whiteboard was still covered in diagrams, the web of thought he'd been building for weeks. His coffee cup was still half-full, a ring of condensation on the coaster beneath it. The everyday artifacts of a working life, suddenly frozen in time, waiting for a return that wouldn't come. I watched them disappear into Jennifer's office. The door closed with a soft click that seemed to echo through the silent room. The office held its breath. The wait was interminable. Twenty minutes. Thirty. I stared at my screen, pretending to work, but my eyes kept drifting to Jennifer's closed door. Around me, my colleagues did the same, the furtive glances, the whispered speculation, the shared knowledge of what was happening behind that door. David was being fired. We all knew it. The only question was why, and even that wasn't really a question. His metrics had been declining for weeks. His AI usage was near zero. He'd refused to adapt, refused to conform, refused to become what the company wanted him to become. And now he was paying the price. The about our conversations over the past few weeks. His resistance, his principles, his insistence on thinking through problems himself. The way he'd looked at me when I'd offered to help with CodeForge, the disappointment in his eyes. The things he'd said about what it meant to be an engineer, about the value of understanding, about the cost of convenience. I'd judged him for it. Felt superior to him. Validated in my own choice to embrace AI. I'd watched him struggle and felt relief that it wasn't me, that I was on the right side of the metrics, that I was winning. This is my fault, I thought, the realization hitting me like a physical blow. I'm part of this. My metrics, my productivity, my willingness to use AI, I'm the standard they're measuring him against. I'm the example they're holding up. I'm the reason he looks bad by comparison. The guilt was sudden and sharp, a blade between my ribs. I'd never wanted this. I'd never wanted to be the reason someone lost their job. I'd just wanted to be productive, to succeed, to stay ahead. But success in this system meant someone else's failure. The leaderboard wasn't just a measurement, it was a ranking. And rankings meant winners and losers. At 3:15 PM, Jennifer's door opened again. David emerged with a cardboard box in his arms. The office went silent. Everyone knew what this meant, but knowing didn't make it easier to watch. The box was standard issue, the kind HR provided for exactly this purpose, the vessel for a career's worth of accumulated artifacts. Inside, I could see the edges of books, a coffee mug, a framed photo, a small plant. The debris of a working life, packed up in minutes. David's face was pale, his jaw tight, his eyes fixed on some middle distance that wasn't quite here. He walked slowly through the open-plan office, past the desks where his colleagues sat frozen, watching. No one spoke. No one knew what to say. The silence was heavy, oppressive, filled with all the things that would never be said. He passed Mike's desk, then Sarah's. He passed the whiteboard where he'd once explained a complex architecture to me, back when I was still learning, back when I still thought the goal was understanding rather than output. He passed the break room where we'd had a hundred conversations about technology and life and the strange industry we'd chosen. And then he passed my desk. For a moment, our eyes met. I saw something in his expression, not anger, not accusation, but something worse. Disappointment, maybe. Or resignation. The look of someone who'd seen this coming, who'd tried to warn me, who knew that I was still in the cage even though the door had just closed behind him. I wanted to say something. Sorry. Goodbye. You were right. I should have listened. But the words caught in my throat, choked by guilt and fear and the terrible knowledge that I was still here, still employed, still "productive," while he was being escorted out. David looked away and kept walking. The moment passed. He disappeared through the glass doors at the front of the office, the box in his arms, and then he was gone. After David left, the office slowly returned to its normal rhythm. Keyboards clicked. Meetings resumed. The AI usage leaderboard updated, David's name disappearing from the bottom of the list, the rankings shifting to fill the void. It was as if he'd never been there. As if fifteen years of experience and expertise could be erased with a single meeting and a cardboard box. I stared at my screen, CodeForge waiting for my next prompt, and felt something I hadn't felt in weeks: fear. Not fear of being laid off, I was too "productive" for that. My metrics were too good, my output too high, my position on the leaderboard too secure. Jennifer had praised me just yesterday. I was exactly what the company wanted. But that wasn't the fear I was feeling. The fear was deeper. More fundamental. I was trapped now. I had to keep using AI. I had no choice. If I stopped, even for a day, I'd become like David, unable to function, unable to produce, unable to justify my existence. And David was gone. Fired. Erased. The cost of non-conformity made viscerally clear. The thought should have motivated me to work harder, to prove my value, to stay ahead. Instead, it made me want to run. But where could I go? AI was everywhere. Every company was adopting it. Every job listing mentioned "AI-first" or "AI-assisted" or "leverage AI tools." It was the future. It was the industry. It was my cage. I typed the next prompt, watched the code appear, and wondered if this was what freedom looked like. That evening, I stayed late again. Not because I had work to do, I'd cleared my queue by 4 PM, but because I couldn't face the train ride home, the empty apartment, the silence where my thoughts should be. David's desk was already being cleared. Someone from facilities had come by, packed up the remaining items, wiped down the surfaces. The whiteboard was clean now, the diagrams erased, the evidence of his thinking wiped away. By tomorrow, someone else would be sitting there. By next week, most people would have forgotten his name. That was how it worked. That was how it always worked. The company moved on. The metrics updated. The machine kept running. I opened my laptop and stared at the CodeForge interface. The cursor blinked, patient, waiting. It had been waiting all day, through the rumors and the tension and David's walk of shame. It would keep waiting forever, indifferent to the human cost of the productivity it enabled. What am I becoming? The question surfaced again, the one I'd been burying for days. But this time it felt different. This time it was mixed with something else, guilt, maybe. Or shame. The knowledge that my success was built on David's failure. That my productivity had helped create the standard that destroyed him. I could still stop. I could still learn to think again. I could still... But even as I thought it, I knew it was a lie. I couldn't stop. I didn't know how anymore. The blankness I'd felt two days ago, the terrifying void where my thoughts should have been, that wasn't a temporary glitch. That was what I'd become. That was the price of efficiency. I typed a prompt, watched the code appear, and tried not to think about what I'd lost. Word Count: 2,547