The Last Programmer --- **Kael Eriksson** *Kelford Press* --- First published in 2026 by Kelford Press Copyright © 2026 Kelford Press. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means — electronic, mechanical, photocopying, recording, or otherwise — without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other non-commercial uses permitted by copyright law. ISBN 978-1-7394521-3-9 (Digital) ISBN 978-1-7394521-4-6 (Print) ISBN 978-1-7394521-5-3 (Audio) Kelford Press Where Words Find Their Home Est. 2006 www.kelfordpress.com --- *For everyone who ever made something that wasn't there before.* --- ## Contents 1. The Compile 2. Severance 3. The Whisperers 4. The Woodworker 5. The Anomaly 6. The Boy Who Never Typed 7. Synthesis 8. The Cascade 9. Reading the Machine 10. The Root 11. The Testimony 12. The Fork 13. Compile Again About the Author Also by Kelford Press Become a Member --- # Chapter 1: The Compile The function was eleven lines long. Ava Chen had written it in nine minutes, which was slow for her, but she wanted it to be right. It checked the oxygen-saturation readings from a pulse oximeter against a patient's baseline, flagged deviations beyond two standard deviations, and routed alerts to the appropriate nursing station. Eleven lines. Nine minutes. Three lives saved per year, statistically, if the hospital adopted it. She pressed compile. The terminal filled with green. No errors. She pressed it again, because she always did, because trust wasn't the same as certainty, and because this was the last function she would ever write for Meridian Technologies. The all-hands had been scheduled for ten o'clock that morning, which was unusual. All-hands meetings at Meridian happened on Fridays at four, when bad news could be metabolised over the weekend. A Tuesday morning slot meant the news was too significant to bury. Ava had known what it was before Diana Falk, the CEO, opened her mouth. "We've partnered with Synthesis," Diana said, standing at the front of the Cascade auditorium, a room named with the optimism of a company that still believed its own mythology. "Beginning next quarter, all new software development at Meridian will be handled by the Architect platform." Ava watched the faces around her. Ravi Patel, three rows ahead, was already nodding. He'd been studying prompt engineering for six months, showing up to work with a second monitor running Synthesis tutorials. He'd seen this coming the way some animals sense earthquakes — not through intelligence but through vibration, something in the floor. Next to Ava, James Moreau, a backend developer who'd been at Meridian for fourteen years, sat with his arms folded and his jaw set. He was looking at Diana the way you look at a doctor who's just told you the lump is malignant. "This isn't a replacement," Diana continued, and Ava nearly laughed, because it was precisely a replacement, and Diana knew it, and everyone in the room knew it, and the only purpose of the sentence was to create a bureaucratic record of something that could be cited later in a lawsuit. "It's an evolution. Architect will handle the implementation layer. Our people will move into orchestration, oversight, and product strategy." Our people. As if the two hundred and thirty engineers in this room were interchangeable with the forty product managers who would actually survive the transition. Diana introduced Marcus Adler via video link. He appeared on the auditorium's thirty-foot screen — forty-four, Danish-American, rumpled linen shirt, speaking with the easy authority of someone who had never doubted that the future was his to design. "I want to show you something," he said. The demo took forty minutes. In those forty minutes, Architect built a patient-scheduling system — the same system Ava's team had spent three months designing, testing, and deploying for Providence Health in 2024. The AI started with a natural-language specification, decomposed it into microservices, generated the code, wrote the tests, ran the tests, fixed the failures, and deployed to a staging environment. The architecture was clean. The code was readable. The test coverage was ninety-seven per cent. Ravi turned around and caught Ava's eye. He was grinning. She looked away. The room was quiet when the demo ended. Not the quiet of awe — the quiet of a funeral where nobody wants to be the first to cry. "Questions?" Diana asked. James Moreau raised his hand. "What's the timeline for the transition?" "We'll begin onboarding teams to Architect next month. Full transition by Q3." "And for those of us who don't transition?" Diana paused. It was a short pause, practised. "We're committed to supporting every member of the Meridian family through this change." James lowered his hand. He didn't ask a follow-up. There was no need. --- After the meeting, Ava went back to her desk on the fourteenth floor. The open-plan office was designed to encourage collaboration. Today it felt like a waiting room. She opened the patient-monitoring codebase. The oxygen-saturation function was part of a larger module she'd been refining for two years. She knew every function in it. She knew why the threshold was two standard deviations, not three. She knew why the alert routing used a priority queue instead of a simple FIFO. She knew these things because she'd sat in a hospital in Portland and watched nurses miss alerts, and she'd talked to a cardiologist who'd explained the difference between a reading that was concerning and a reading that would kill someone in twenty minutes. Architect didn't know any of that. Architect knew patterns. It had ingested millions of lines of medical-software code and learned what patient-monitoring systems usually looked like. It could build one faster than Ava. Whether it could build one that understood why the threshold mattered — that was a different question. She closed the module and opened a blank file. She didn't know what she was going to write. She sat there for a while, cursor blinking, and then she wrote a comment: ``` // This is the last function I write here. // It checks whether someone is dying. // That seemed like a good thing to end on. ``` She deleted the comment. Comments were for other developers. There would be no other developers. --- At six-fifteen, the office was nearly empty. The cleaning crew wouldn't arrive for another hour. Ava packed her bag — laptop, charger, the small jade plant she'd kept on her desk for three years. She looked at her monitor one last time. The terminal was still open, the compile output still green. She thought about the first programme she'd ever written. She was twelve, in her parents' apartment in Bellevue, and her father had brought home a battered copy of *Structure and Interpretation of Computer Programs*. It was far too advanced for her. She didn't care. She typed the first example into a Scheme interpreter and watched the screen print `"Hello, World"` and felt something click into place behind her sternum, a feeling she would spend the next twenty-six years chasing. That feeling had a name, though she'd never said it aloud to anyone except June Watanabe, who understood. The feeling was: *I made something that wasn't there before, and it works, and it's mine.* She shut the laptop. The screen went dark. The office lights, on motion sensors, began switching off behind her as she walked to the lift. Section by section, the fourteenth floor went dark. In the car park, she sat in her Volvo for three minutes before starting the engine. Rain stippled the windscreen. Seattle rain, fine as mist, the kind that doesn't fall so much as materialise. She thought about calling Leo, but it was a school night and he'd be doing homework — or, more accurately, telling the AI to do his homework while he watched something on his phone. She thought about calling David, her ex-husband, but David would say something well-meaning and insufficient. She thought about calling June. She started the engine instead. The drive home took thirty-five minutes. She lived in a craftsman house in Fremont. The house was dark — Leo was at David's this week. She let herself in, set the jade plant on the kitchen windowsill, and opened her laptop. The terminal was still there. Green text on black. ``` Build succeeded. 0 errors. 0 warnings. ``` She stared at it for a long time. Then she closed the terminal, and the laptop, and sat in her kitchen listening to the rain, and did not cry, because Ava Chen was not a person who cried, but the silence in the house was the loudest thing she'd ever heard. --- # Chapter 2: Severance The letter arrived by email at 7:14 a.m. on a Thursday, which struck Ava as unnecessarily precise. She was eating toast — sourdough, from the bakery on 36th Street that still employed humans — when her phone buzzed with the subject line: *Your Meridian Transition Package*. Eighteen months of salary. Continuation of health benefits for twelve months. A $5,000 "professional development stipend" that could be used for retraining courses. Stock options vested through the end of the quarter. A non-disparagement clause. A release of claims. The letter was six pages long, generated by an AI — Ava could tell from the sentence rhythms, the way each paragraph anticipated and defused a potential objection. Simultaneously generous and litigation-proof. She signed it. The alternative was a lawsuit she would lose, because there was no law against replacing employees with software. --- The bar was called The Bracket, a programmer joke that had become less funny in recent months. It occupied the basement of a converted warehouse in Pioneer Square, and on the last Friday of every month, it hosted "the wake" — an informal gathering of recently laid-off tech workers. Ava hadn't intended to go. She'd spent the first three weeks of her severance in disciplined routine: up at seven, coffee, ninety minutes of exercise, then an afternoon that stretched before her like an empty car park. She read. She cleaned. She reorganised the garage. She did everything except open a code editor. James Moreau had texted the address. *Come. It helps.* She doubted this but went anyway, because the house was very quiet. The Bracket was half-full, which for a basement bar on a Friday night meant about sixty people. Ava recognised some of them. James was at a table near the back with two women Ava didn't know. She ordered a gin and tonic — Hendrick's, neat pour, not too much tonic — and joined them. "Ava, this is Petra. Backend at Amazon, twelve years. And Song-yi. Frontend at Google, eight years." "Was," Petra said. She was in her late forties, with close-cropped grey hair and the kind of posture that suggested a military background. "I was backend at Amazon." "Was," Song-yi agreed. She was younger, early thirties, and she was drinking what appeared to be her third beer. "Past tense is important now." They talked for three hours. The conversation had a pattern Ava would come to recognise at subsequent gatherings: a oscillation between anger and dark humour, with occasional descents into genuine grief. Petra had been part of the team that built the recommendation engine for Amazon Fresh. She'd spent four years optimising delivery routes for groceries. Architect had replicated her work in a weekend sprint. "The thing that gets me," Petra said, "is that it used my code as training data. My commits. My architecture decisions. It learned from me, and then it replaced me. I taught it everything it needed to make me unnecessary." James nodded. "I've been thinking about becoming a plumber." Song-yi looked at him. "Seriously?" "Completely seriously. My uncle's a plumber in Tacoma. He's sixty-three. He's booked out six weeks in advance. He makes more than I did at Meridian. And no AI is going to crawl under a house to fix a pipe. Not in our lifetimes." "The trades are having a renaissance," Petra said. "My brother-in-law is an electrician. He's been turning down work." Ava sipped her gin. "The numbers are staggering," she said, because someone had to say it. "Three hundred and forty thousand developer layoffs in the US in the last fourteen months. That's not a correction. That's an extinction event." "It's not extinction," James said. "It's evolution. We're the Neanderthals." "Neanderthals didn't go extinct because of anything they did wrong," Ava said. "They were perfectly adapted. The environment changed." "That's not more comforting." "It's not meant to be." --- The world outside tech responded with a muted shrug. Ava noticed this with a bitterness she hadn't expected. Programmers had spent two decades telling everyone that disruption was creative and necessary and the future, and now the future had arrived for them, and the general public seemed to regard this as poetic justice. Her neighbour Margaret brought over a casserole. "I heard about the layoffs. I'm sorry, dear. What is it you did again?" "I was a software architect." "Oh. Well, I'm sure you'll find something. You're so clever with computers." Ava thanked her for the casserole. --- David called on Sunday, when he dropped Leo off. Ava's ex-husband was a landscape architect — a profession being disrupted at a much slower pace, because gardens had the inconvenient property of existing in the physical world. "How are you doing?" he asked, standing in her doorway with the particular expression of concern that she'd found both touching and maddening throughout their twelve-year marriage. "I'm fine." "You're not fine. You haven't been fine since the announcement." "I'm fine in the sense that I'm functional, fed, and solvent. I'm not fine in the sense that the thing I've done every day for twenty years no longer exists as a profession." David leaned against the doorframe. He was tall, bearded, the kind of man who looked like he should be hiking in a Patagonia catalogue. "Maybe this is a chance to slow down. You've been running at a hundred per cent since — well, since I've known you. Maybe this is an opportunity to figure out what else you want." "I want to write code, David." "I know. But maybe there's—" "There isn't a 'but maybe.' That's the thing you don't understand. For you, landscape architecture is what you do. For me, programming is what I *am*. The difference matters." He looked at her for a long moment. Then he said, "Leo needs new trainers. I'll take him to the shops next weekend." "Fine." "Ava." "Fine. Thank you. I appreciate it." He left. She closed the door. She could hear Leo upstairs, talking to someone — or to something, more likely, one of the AI companions that his generation treated as friends. She stood in the hallway and listened to her son having a conversation with a machine, and she felt the distance between them like a physical thing, a gap