For Chase and Janette, understanding the train's programming was a constant source of conflict. While various specialists took care of the mechanical systems, only Chase and Janette possessed the insight needed to decipher its digital workings. Over time, their knowledge steadily grew, yet September always withheld the full picture, revealing one layer at a time. To prompt a deeper investigation into the train's systems, Chase seized upon a seemingly trivial incident: a sliding door between modules 12 and 13 had remained open for five minutes until a slight nudge closed it. Amanda had mentioned the door during the morning meeting, and Chase immediately formed a team to examine the malfunction.
At the next meeting, the team reported that nothing appeared to be seriously wrong with the door. Despite the minor nature of the incident, Chase saw it as an excellent opportunity to deepen the crew's understanding of a critical safety system. With a calm yet determined tone, he reminded everyone that even a small malfunction in a vital component was worthy of careful study. He believed that learning the details now could prevent future problems and enhance their overall readiness.
"This is not merely a door," he continued. "It separates compartments that sustain distinct sealed atmospheres. Even though it only got stuck this time, imagine what could happen if it failed completely. It might leak atmosphere or induce a vacuum in one module. I want you all to treat this as a chance to examine every aspect of the door's design and operation. By investigating its seal, its mechanics, and the controls behind it, we can learn how to prevent a real failure when it matters most."
Reluctantly, the crew dismantled and reassembled the door while carefully examining every component. What had seemed like a straightforward task soon revealed itself to be complex. Working under strict conditions, it took them eight days to remove the door without damaging the panel. Their progress was further slowed by uncertainty over a possible atmospheric loss in module 12, forcing them to proceed with extra caution.
Chase refused to let the door be removed without a complete understanding of its inner workings. He insisted that every detail be uncovered, from the operation of its seal to the computer program that controlled it, and that every conceivable scenario be simulated. To prepare for any eventuality, the crew ran full emergency drills, clearly outlining each person's role, their assigned location, and the communication protocols to follow if something went wrong.
After fourteen days of careful work, the team finally removed the door and stripped it down to its core components. Since it was connected to the adjacent module, there was no loss of atmosphere. They inventoried every piece, documented the process with pictures taken, and developed a detailed procedure for disassembly and reassembly. During the work, an unexpected discovery emerged. On the inside of the panel lay a small tag, scrawled in what appeared to be blood: “You win again.” When Sam presented the photo at the meeting, confusion reigned. The crew’s inquiries to September about the graffiti produced no explanation, and they quickly moved on.
---
Janette made an important discovery regarding the function of this specific door, or more likely, all doors on the train. During a morning meeting, Janette pointed out a critical flaw: “If a fire breaks out in any module, all doors will lock down, leaving that module to burn. No override is possible even three hours after the fire.”
Throughout this time, Chase frequently grilled Janette on even the most mundane aspects of the program. “What is the logic behind the door's operation? How does it work? Can we optimize it? What redundancies exist?” As the lead programmer, Janette was tasked with breaking down every detail of the code that controls the door's opening and closing. Chase ordered her to create a companion code to run alongside the current one. The new version was expected to handle every scenario that the old code managed while performing faster and more reliably. He made it absolutely clear that she must start completely from scratch. Janette felt both challenged and frustrated by the demand.
What had taken months, perhaps even years, to evolve in the original code now faced a total overhaul at Chase’s insistence, giving Janette only days to complete it.
In barely over a week, Janette had crafted fresh code, and she savored the sense of achievement it brought. After the morning meeting, she presented her work to Chase. As the crew lingered over their coffee after the meeting, a high-profile VORN streaming moment that everyone knew was coming slowly unfolded.
"Janette, you are our lead programmer," Chase began, his gaze locked on her with an intensity that sent a chill through the room. "Do you truly believe you are a good programmer?"
She hesitated for a moment, then replied firmly, "Yes, I know I am good. Who else could write code at this level? The software in this facility operates on an entirely different plan, it must have taken years to perfect."
Chase raised an eyebrow, his tone hardening. "The code is advanced, but it has glaring gaps. You rushed to close issues like the fire override, and there are even more shortcomings hidden deep in the logic. I need you to redo the entire thing from the ground up. Do not simply patch over the flaws; I expect something far superior."
Janette's blood boiled. No one had ever dared call her work sloppy. Known among her peers as brilliant and precise, she shot back, "Are you calling my code sloppy? Can you even read it, or is it too complex for you to understand?" Her glare was so fierce it nearly made him step back. The charged silence that followed was thick with challenge and resentment, each word a spark that lit the already tense air.
Chase's jaw tightened as he searched her eyes for any sign of concession, while the assembled crew shifted uncomfortably, aware that this confrontation was about more than just code—it was a battle for respect and control over their future. The moment pulsed with raw intensity as both sides braced for the next exchange in this unexpected showdown.
Chase maintained his composure, his tone calm yet edged with determination. "I admit, the code is difficult to read. It seems as if you were programming while suspended upside down from a tree. Code should follow established conventions and flow like an orchestra playing a Mozart symphony rather than resemble a toddler banging on a drum set. I accept my share of the blame for not setting clear standards. From now on, your code must be refined and integrated, much like an orchestrated performance instead of isolated drumbeats." His words cut sharply, hanging heavy in the air.
Stung by his criticism, Janette snapped, "Are you calling my code unreadable, child? Do you need me to explain every line to you?" Though his remark left her visibly wounded, Chase remained resolute. "Of course I can read it. Now let us review it and pinpoint exactly where improvements are needed." He turned to the wall where September's interface was displayed. "Please bring up Janette’s code for the door." The AI responded evenly, "The code is on screen, Commander. Remember, no changes are allowed and no instruction may be given to modify it." Chase continued, his voice low and challenging, "Yes, September, I recall your little electric shock. I have no intention of altering the code directly, but I will highlight areas that need improvement. The final decisions remain solely with Janette. Does this violate your absurd rule?" The charged silence that followed left everyone in the room aware that this was more than a technical review, it was a battle for authority and respect.
"That approach is acceptable," September replied in a measured tone. "Do you have a code simulator?" Chase asked sharply. "Yes, I can simulate the code to test for bugs," the AI answered without hesitation. "Then run Janette's door code and test for bugs," Chase commanded. "Complete. No bugs detected in either code," September reported. At that moment, Janette felt a surge of smug satisfaction. She had already run the simulator herself and knew her code was flawless. In her mind, this only underscored that Chase lacked the programming insight that she possessed.
Chase was not ready to yield any ground. "September, display the processing times for both codes," he ordered. Within seconds, the screen lit up: "In-built door code: 0.03 second. Janette's door code: 0.14 seconds." His gaze cooled as he turned to her. "I asked you to improve the code, not produce one that runs nearly five times slower. Janette, you must refine your work. I expect it to be faster, smarter, and more integrated. Now, tell me, are we ready to move forward?" The air in the room crackled with tension as their exchange left no doubt that this confrontation was about more than just numbers—it was a battle for professional respect and control.
"I refuse to listen to your arguments about microseconds making a difference," Janette snapped, her voice laced with indignation. "You are compelling me to waste my time on a simple door. I spent eight grueling days writing code that now feels completely wasted. What is the point of rewriting it? Are you merely trying to squander my time?"
If you discover this tale on Amazon, be aware that it has been stolen. Please report the violation.
Chase's eyes narrowed as he turned to September. "Please highlight lines 12 through 25, 230 through 450, 560 through 578, 1760 through 1789, and 1978 through 2005." The AI replied curtly, "Complete." Chase then leveled his gaze at Janette. "Janette, explain what you were thinking when you wrote these lines. They read as if a child simply added one plus one plus one plus one to get four. With the advanced software we have, I expect something far more sophisticated." Noting Janette squirming in her chair, he pressed on relentlessly. "What about the pickup point for this code? Where exactly is it? It appears you merely copied the old code without truly grasping its structure. The pickup point is crucial. How does the AI know where to resume execution?"
Before the confrontation could escalate further, September interrupted coolly, "Commander Chase, you are venturing into areas beyond your clearance, and you are instructing Janette to modify code sections that are expressly off limits to you." Chase's tone turned defensive. "I am not asking her to change anything arbitrarily. I am simply demanding that she perform her job better. Is that not my responsibility as commander?" The AI did not waver. "Be advised, if you persist along this path, you will face disciplinary action." Still fuming, Janette retorted, "I would not worry, September. I doubt this imbecile even understands what he is talking about. This meeting is over anyway." With that, Janette stormed out of the command module.
Chase found himself unable to avert his eyes, even as he tried. Despite the heated words, she remained incredibly beautiful; he wondered if her allure grew with every defiant step or if he was simply falling more head over heels. As she left, he glanced around the room and saw that the rest of the crew sat in quiet observation, absorbing every moment of the clash. A deep, red flush spread across his face as the full weight of their silent judgment settled in.
“I’m sure you all have duties to attend to,” he snapped. There were a few laughs, and Patrick said, a little loudly, “The strange courting rituals of the hummingbird.” Everyone seemed to find this particularly funny and burst into laughter.
Chase sat alone after the confrontation, stewing over the harsh words that had been exchanged. He felt deep regret for having pushed Janette so hard. He knew that someone as self driven as she rarely needed any prodding, yet he had forced his will upon her. Despite the pressure, he could not ignore that she had done an impressive job. Under challenging circumstances, she had delivered a workable solution in only eight days, and her code was undeniably effective. It worked, which most would commend, but Chase craved more; he needed her to understand the code that they were working with fully. Unable to access the system himself, he was forced to rely on her talent, and that reliance ate away at him. In his mind, her rushed code held hidden potential, a few lines that could be transformed into a breakthrough if only they were refined correctly.
Yet as he examined his own role in their dynamic, Chase understood the heavy cost of pushing her relentlessly. Janette was the only one capable of understanding the system's intricate demands; brilliant, resourceful, and for him unquestionably captivating. He longed for her to be not just competent but the living embodiment of his ideal coding vision. Still, a gap lay between them. Given his imposed limitations and the ever-present AI, he struggled to explain his vision or gently guide her through its many nuances. Instead, he found himself compelled to push her further, hoping that his rigorous critiques would eventually coax her into delving deeper into the AI's labyrinth. That ever watching AI, controlling every operation, made his task even more urgent. Chase sometimes believed that, given unlimited time, he could outsmart it himself, but he doubted time was not on their side. So, with a mixture of frustration and reluctant determination, he resolved that he would continue to challenge Janette each day until her work not only functioned but also forced the system into reconsideration.
---
Chase sat with a heavy heart, replaying the confrontation in his mind. He wondered how long it would be before Kaya cornered him and questioned his style. In his thoughts, he debated whether pushing Janette was truly necessary, or if he was simply acting like a "little man" as she had once called him. Yet, knowing that Kaya had long assumed the role of protector for the crew helped him hold his ground. He realized he needed to push Janette; she was without question the crew's finest programmer. At the same time, he recognized that he would soon have to answer to Kaya.
Since their arrival on Mars, Kaya had evolved. She had always been a strong woman, but now she exuded a calm power that was as steady as iron. As if summoned by his inner turmoil, Kaya quietly took a seat opposite him at the table. Chase noted that several crew members who had been lingering after his intense exchange with Janette soon dispersed, leaving only him and the unwavering presence of Kaya.
Kaya sat silently, her steady gaze belying a quiet strength. Feeling both exposed and cornered beneath her calm intensity, Chase finally spoke. "I know you are here to ask if my approach was necessary or if I am just acting like a 'little man.' I admit I snapped once when Janette challenged my understanding, but I fought hard to maintain my composure. I believe it is important to push Janette because she is, without question, our best programmer. Yet, sometimes, she is too arrogant about her work. I must break through that barrier so that we can operate as a cohesive team. I cannot simply show her a perfect example; all I can do is determine what works and what does not."
Kaya's response was calm and resolute, her voice carrying a gentle authority. "As long as it is necessary, do not push her too hard. We cannot afford to see her break down.” In that moment, Chase understood that while he might need to continue challenging Janette, he would also have to navigate the unyielding strength of Kaya, a presence that reminded him that leadership required both firmness and restraint.
Kaya sat calmly, her gaze steady on Chase. He had come to dislike these meetings, despite his deep respect for her. He valued the way Kaya worked tirelessly with every crew member, ensuring that each person remained clear-headed and focused while they were here. More than anyone else, she served as his second in command, a guide who balanced quiet authority with genuine care. Yet each meeting left him feeling exposed, as if he were a little child under her watchful eye. Kaya never spoke down to him or treated him without respect. In fact, her frequent compliments and measured words only served to highlight his own doubts. It was as if she could see through every illusion he clung to, revealing the insecurities he kept hidden even from himself.
Breaking the silence, Kaya spoke in a calm, measured tone. "I want to discuss the writing on the door," she said softly. "We brushed over it during the meeting, but when I see words inscribed in blood, I find it difficult not to search for the hidden meaning. 'You win again' is not something one writes lightly." Chase sighed, his tone laced with uncertainty. "I am not sure what more I can say. I know as much as you do. There is no way to tell whether it was meant as a warning or a leftover joke from when they built the train. It may even have been placed deliberately by VornTV as an Easter egg to make us question our choices. If that is the case, we must bear it in mind. And do not worry, Kaya, I do not forget such things."
Kaya answered with quiet authority. "I believe it will be important in due time, yet I cannot shake the feeling that such a message casts a dark shadow. Have you seen any other evidence like this on the train? Is there anything you have kept hidden from me?" Chase replied defensively, "I am not keeping anything hidden, Kaya. I do have plans, but if I share them now, September will know. Truthfully, we still do not know enough. To your question, I have not come across any other example on this train."
Kaya nodded slowly. "Very well. Please inform me if anything new comes to light." With that, she rose gracefully and left the command module. Chase watched her depart, noting the calm and confident way she moved. He was uncertain of her true intentions, but it was clear that Kaya had her own plans. Though she often sought insight into his ideas, she never offered any glimpse of her own. The silent exchange left him with a mix of admiration and apprehension, aware that both their strengths and vulnerabilities would shape what lay ahead.
After about ten minutes, Chase was surprised to see Janette reappear. She still radiated fury as she ignored his presence and marched straight to her terminal to resume her work. In that moment, he silently applauded her resolve. This woman possessed a rare kind of fire that both infuriated and inspired him.
---
When Janette stormed out of the meeting room earlier, her anger had been nearly palpable. She left seething, convinced that no one could ever dare say her code was inferior. How could he possibly compare her work to that of a monkey? Yes, she admitted her code was not polished for management's sake, but that was because she never needed to embellish her work. The insult stung. How dare that little fucker call her work written like a baby? The thought roiled inside her as she briskly stormed into her bed space, pacing furiously and seething with indignation.
Janette knew he had targeted parts of the code that were merely simple introductory sections that offered no real flair and served only as a means to capture the proper variables. He had demanded a complete rewrite of the entire code using the fancy new Fathom language, instructing her to start completely from scratch instead of relying on established shortcuts. And she had done it in eight grueling days. Eight days of some of the hardest work she had ever put in. She deserved praise. She expected to impress everyone, including him. Instead, his condescending tone made her seethe; she felt as though that arrogant child could have scribbled out the entire program in five minutes with a pen stuck up his behind.
The simmering rage urged her onward and fueled a defiant determination. Though her heart pounded with fury, Janette returned to the command module determined not to let Chase's criticism break her spirit. Ignoring the lingering eyes of the disbanded audience, she sat down at her terminal and began from the very start. If he expected the code to be spruced up, then she would elevate it to a level he had never seen. Every line would bear the mark of her resolve, and every detail would be a testament to her brilliance. She vowed that no one, not even Chase, could match her intensity or her technical prowess.
