Thursday morning. Michael had been coding since 5 AM, trying to fix what he'd broken. The dashboard was working again—mostly—but the investor meeting had been rescheduled for Monday, and David's silence on the phone had been worse than any lecture. He needed a break. Not a rest, never a rest, but a change of context. The desk in his apartment had been wobbling for weeks, one leg slightly shorter than the others. He'd meant to fix it, had bought the supplies, but there was always another deadline. Today, with his mind spinning and his code not cooperating, he grabbed the desk leg and headed out. The furniture workshop was three blocks from his favorite coffee shop. He'd walked past it a hundred times without stopping. Today he stopped. The workshop smelled of sawdust and something older—time, maybe. Michael stood in the doorway, waiting for his eyes to adjust to the dim light. "Can I help you?" The voice came from the back of the shop. A man emerged from behind a large workbench—tall, bearded, hands covered in sawdust. He looked like he belonged here, like he'd grown out of the wood itself. "I need to fix this." Michael held up the desk leg. "It's slightly short. The desk wobbles." The man took the leg, examined it, turned it over in his hands. His movements were unhurried, almost meditative. "Oak," he said. "Good wood. Shouldn't be wobbling." He looked at Michael. "Jake Morrison. You are?" "Michael. Michael Torres." "Nice to meet you, Michael." Jake gestured to a stool. "Have a seat. This'll take a few minutes." Michael sat and watched Jake work. The process was methodical. Jake measured the leg twice, marked it with a pencil, then selected a thin piece of wood from a drawer. He applied glue, positioned the shim, and clamped it in place. Then he waited. Michael's leg bounced. His fingers drummed on his knee. He checked his phone—three new messages, all work-related. He started to type a response. "You're going to wear yourself out." Michael looked up. Jake was watching him, a slight smile on his face. "What do you mean?" "All that energy. All that movement." Jake gestured at Michael's bouncing leg. "You're vibrating." "I'm just... efficient. I like to keep moving." "Efficient." Jake nodded slowly. "Is that what you call it?" The question felt like a challenge. Michael bristled slightly. "What do you call it?" Jake didn't answer immediately. He turned back to his work, sanding the shim he'd just glued. The sound was rhythmic, almost soothing. "I call it fear," Jake said finally. "Fear of stopping. Fear of what happens when you're not moving." Michael opened his mouth to argue, then closed it. The words felt too true. "I'm a software developer," he said instead. "Speed is part of the job. We ship fast, iterate, improve. That's how it works." "Ship fast." Jake tested the shim with his finger. The glue was still wet. "And then what?" "Then we fix the bugs. Add features. Ship again." "And does it ever feel done? Complete? Right?" Michael thought about the dashboard, the failed demo, the endless cycle of sprints and fixes. "No," he admitted. "It never feels done." Jake set aside the sanding block and picked up a different tool—a small plane with a wooden handle worn smooth from use. "This table," he said, gesturing to the large piece of furniture behind him, "I've been working on it for three months." "Three months?" Michael couldn't hide his shock. "For one table?" "It's not just a table. It's someone's dining room. Where they'll have meals for the next fifty years. Maybe longer, if I do it right." Jake ran the plane along the edge of the table, shaving off a thin curl of wood. "Three months is nothing compared to fifty years." "But the efficiency—" "Efficiency isn't always speed." Jake looked at him directly. "Sometimes the most efficient thing is to take your time and do it right. Because if you rush, you make mistakes. And mistakes take longer to fix than doing it right the first time." Michael watched the wood curl away from the plane. The movement was slow, deliberate, almost hypnotic. "That doesn't work in my world," he said. "We ship fast, iterate, fix later. There's no time to do everything right the first time." "How's that working out for you?" The question landed like a punch. Michael thought about the failed demo, the corrupted data, the investors' disappointed faces. "It... has its challenges." Jake smiled, but not unkindly. "Maybe your world needs to change." The desk leg was fixed in fifteen minutes. Jake refused payment. "Bring me something to work on sometime," he said. "If you want. I could use a website." Michael nodded, though he wasn't sure he'd come back. The whole experience had been unsettling—the slowness, the patience, the idea that something could take months and still be worth doing. That wasn't his world. That wasn't how things worked. He walked home through the Austin heat, the desk leg still in his hand. Three months. Fifty years of use. There was something there, something he couldn't quite name. A different relationship with time. A different way of measuring success. He thought about the dashboard, the quick fix that had failed, the sprint that never ended. Jake's words echoed in his mind: How's that working out for you? Not well. That was the honest answer. Not well at all. But what was the alternative? Slowing down? Taking three months to build one thing? That wasn't realistic. That wasn't how the tech world worked. Was it? He shook his head and picked up his pace. He had a dashboard to fix, a client to win back, a sprint to complete. There was no time for three-month tables. No time at all.
The website for Jake's workshop launched on a Tuesday. No fanfare, no sprint, no deadline, just a quiet moment when Michael decided it was ready. Jake looked at it on his phone, scrolling through the pages. "This is good," he said. "This is really good." "Thanks." Michael felt a strange pride. Not the frantic pride of a sprint completed, but something quieter. More solid. "You should meet someone," Jake said. "A friend of mine. Dr. Helen Park. She teaches history at UT." "What does history have to do with websites?" "Nothing. Everything." Jake smiled. "Just trust me. Come to dinner on Friday." --- Helen Park's house was filled with books. Not decorative books, but real ones, worn spines, dog-eared pages, margins filled with notes. She was older than Michael had expected, with silver hair and eyes that seemed to see through time itself. "Jake tells me you're learning about patience," she said, pouring tea into ceramic cups. "I'm... trying to understand it," Michael admitted. "It doesn't come naturally." "It never does." Helen settled into her chair with the ease of someone who had sat in it thousands of times. "We live in an age that worships speed. But speed is not the same as progress." Michael leaned forward. "That's what Jake says. But in my world, speed is everything. Ship fast. Iterate. Move or die." "And how is that working?" The question echoed Jake's, but Helen asked it differently. Not as a challenge, but as an invitation. "Not well," Michael admitted. "I keep sprinting, but I never get anywhere. I keep fixing problems I created by rushing." "Let me tell you a story." Helen set down her teacup. "In the 1960s, there was a movement for civil rights. The people involved knew it would take years, decades, to achieve their goals. They didn't sprint. They marched. They organized. They built institutions that would last long after they were gone." "And it worked." "It's still working. That's the point. Movements that are built to last don't sprint. They endure." Helen looked at Michael. "The question isn't how fast you can go. The question is: what are you building that will outlast you?" --- The conversation stayed with Michael for days. What was he building that would outlast him? Code that would be rewritten? Features that would be deprecated? Sprints that would be forgotten? He thought about Jake's table, fifty years of use. He thought about Helen's books, decades of knowledge, passed down through generations. What was he building? Monday morning. Michael was at his desk, starting a new project, when the old patterns kicked in. What's the timeline? What's the MVP? How fast can we ship? But this time, he paused. What if I asked a different question? he wondered. What if I asked: what will this look like in five years? The project was a customer portal for a healthcare company. In five years, the code would probably be rewritten. But the relationships with the customers, that could last. The trust built through reliable software, that could last. What if I built it to last? He called the client that afternoon. "I want to talk about the timeline," he said. "We need it in six weeks," the client said. "Can you do it?" "I can do it in six weeks. But I want to ask you something first." Michael took a breath. "What do you want this portal to look like in five years?" There was a pause on the other end. "In five years? I... I don't know. We've never thought about it that far ahead." "What if we did?" Michael leaned forward. "What if we built this not just for the launch, but for the long term? What would change?" The conversation lasted an hour. By the end, the timeline was still six weeks. But the approach had shifted. Instead of cutting corners to meet the deadline, they were building a foundation that could grow. It wasn't the long game, not yet. But it was a start. That night, Michael went back to Jake's workshop. "I talked to Helen," he said. Jake looked up from his work. "And?" "And I think I'm starting to understand. The sprint isn't the point. The building is the point." Jake nodded slowly. "That's a good start." "But here's my question." Michael sat on the stool. "How do you maintain patience in a world that demands speed? How do you play the long game when everyone else is sprinting?" Jake set down his tools. "You don't do it alone. That's the secret. You find people who understand. You build a community that values the long term. And you remind each other, every day, that the sprint is an illusion." "An illusion?" "The sprint feels like progress. But it's not. It's just movement." Jake gestured around the workshop. "Real progress takes time. Real value takes time. And the people who understand that, they're the ones who build things that last." Michael looked at the table Jake was working on. Three months. Fifty years. Maybe I can do this, he thought. Maybe I can learn to play the long game. He went home and opened his laptop. The new project was waiting. Instead of starting to code, he opened a document and wrote: What will this look like in five years? What foundation am I building? What will outlast the sprint? The questions felt strange. Unfamiliar. But also right. For the first time in his career, Michael was thinking beyond the deadline. For the first time, he was playing the long game.