They were graduates of Central Node University. They wore pristine white lab coats and certified anti-static gloves. To them, Molen wasn't a colleague; he was a glitch, a statistical anomaly that had just invalidated their degrees.
"He definitely skipped the rear standoff screws," Kael, the trio's leader, muttered as he approached one of the towers Molen had sealed.
With a mix of resentment and the hope of catching a bug, Kael opened the chassis. He expected to see spaghetti wiring, poorly applied thermal paste, or loose connectors... the standard signature of a dirty JIT.
But the inside was immaculate.
The cable management surpassed the manual's standard. The airflow channels were optimized like healthy arteries. There wasn't a single fingerprint on the silicon. It was a flawless deployment.
"Damn it," Kael whispered, violently slamming the case shut. "He optimized the hardware by bypassing the chassis bureaucracy. That... that shouldn't be legal."
"Vincent won't let this compile," another technician said, wiping his glasses. "A JIT can't humiliate a Department of Solidity and expect the system not to throw an exception. Tomorrow he'll be terminated for 'breach of safety protocols.' Just watch."
Inside his glass-walled office, Vincent wasn't screaming. Vincent's silence was far more dangerous than his shouting.
He sat in front of his terminal, parsing Molen's temporary contract line by line. His eyes, cold as blue LEDs, were hunting for a clause, an ambiguity—a bug in the legal agreement that would allow him to terminate the worker process without severance pay.
"'Clause 4.2: Insubordination or deviation from standard ISO-9001 protocols...'" Vincent read under his breath. A reptilian smile rendered on his face.
Molen had won the production bet, true. But by doing it through his custom method instead of the company's official documentation, he had technically thrown a quality protocol violation.
Vincent minimized the window when he saw Robert and Molen pass by toward the server zone. He wouldn't execute anything today. He'd let Robert play with his new "pet" for a while. When the Architect got bored of the kid—because they always got bored of JITs—Vincent would trigger his termination script.
"Enjoy your visit to the executive tier, trash," Vincent muttered, smoothing the pin of the Order of Solidity. "The Garbage Collector runs first thing tomorrow."
On the other side of the security firewall, the atmosphere shifted drastically. The air no longer smelled of ozone and sweat; it smelled of sterile cold, ether, and money.
Molen walked half a pace behind Robert, painfully self-aware of his worn-out boots and grease-stained cargo pants against the flawless white polymer floor. Everything here seemed designed to intimidate anyone lacking a master's degree.
"Sit down," Robert said as they entered his personal office.
It wasn't a standard office. The walls were floor-to-ceiling monitors rendering real-time data cascades. Latency graphs, CPU loads, and transactions per second surrounded the black glass desk like a digital nervous system.
Robert dropped into his ergonomic leather chair and executed a quick command.
"Watch. This is what's killing us."
One of the walls violently refreshed. It wasn't just plain text; it was an open wound in the software. Blood-red lines of code spawned from the top of the screen and dripped downward, like a severed artery in the system's core.
java.lang.NullPointerException at com.macrosystems.erp.core.WaterFactory.getWater(WaterFactory.java:42)
at com.macrosystems.erp.core.WaterManager.distribute(WaterManager.java:15)
... 42 more
"There you have it," Robert said, pointing at the hemorrhage. "The ERP killer."
Molen leaned forward, squinting. He didn't parse half the words. What was com.macrosystems? What did at ... :42 mean? But the structure... the structure felt familiar. It was like looking at an electrical schematic where a wire was abruptly severed.
"It looks... it looks like a dead end," Molen muttered hesitantly. "As if something promised to be there, but vanished."
This narrative has been purloined without the author's approval. Report any appearances on Amazon.
Robert nodded, surprised by his intuition. "Technically, we call it a Stacktrace. It's the footprint the program leaves right before it dies."
"Alphonse, a friend of mine... he called it 'The Abyss,'" Molen said, recalling late nights in his mentor's repair shop. "He used to say it's when the system tries to grab a handle, but only catches thin air."
"Your friend Alphonse has a poetic way of describing a Null Reference," Robert said with a half-smile. "It triggers inside the WaterFactory. It's a critical module."
"Module?" Molen asked.
"A legacy piece of code. A... component," Robert translated, simplifying it. "It was written fifteen years ago by the founders. It's untouchable. Ten days ago, the system crashed. The Basic Maintenance team—your friends in the white coats—did the only thing they know how to do: they rebooted the servers."
Molen shook his head instinctively. He recognized that patch. "That's like having your house flood and your solution is to mop the floor with rags without turning off the valve," Molen said. "The water is just going to overflow again."
Robert raised an eyebrow. The analogy was perfect. "Exactly. The system held up for ten days because it took that long for the memory to leak and fill up with errors, but my metrics indicate the bleeding is going to return. And this time, a reboot won't work."
"Why don't you... patch it?" Molen asked with genuine innocence. "Why don't you just go into that WaterFactory and swap the pipes?"
Robert stood up and began pacing the room, gesturing with frustration.
"Because no one knows what's inside that Factory, kid. The documentation was lost ages ago. It's a 'Black Box'. If we try to pry it open and blindly refactor the source code, we could break compatibility with twenty other downstream systems. It's like trying to swap out the foundations of a skyscraper without evicting the tenants."
Molen stayed quiet, buffering the data. His imposter syndrome was screaming at him that he had no right to an opinion, that his domain knowledge was strictly limited to capacitors and voltages. But his curiosity overrode his doubt.
"My team is pushing for Defensive Programming," Robert continued. "They want to wrap the consumer, the WaterManager, in validation shields. Fill the codebase with null checks. Asking a hundred times, 'Is there water?' before taking a sip. It's safe, it's industry standard... and it's cowardice. It's going to bottleneck the system by 40%."
Molen stared at line 42 of the crimson error. He recalled another lesson from Alphonse about shipping crates. "If the factory doesn't have water... it shouldn't deliver the void," Molen said, compiling his thoughts. "It should deliver... a box."
Robert stopped in his tracks. "A box?"
"Yeah. Alphonse used to say that if you don't know whether the cat is alive or dead, you don't open the box. You deliver the sealed box." Molen moved his hands, trying to map the abstract concept into physical geometry. "A box labeled 'Might be empty.' That way, whoever receives it doesn't crash from shock if there's nothing inside. They just see the empty box and... look for an alternative route."
Robert stared at the young tech for a long minute. He could see the gears turning in the kid's head. The boy didn't know what a Wrapper was, nor a Monad, nor an Optional. Yet he had just perfectly described the functional design pattern to prevent nulls, routing it all through an analogy of cats and shipping crates.
The Architect felt a chill. He processes logic like a Senior Engineer, but uses the vocabulary of a child, he thought.
"You have the intuition, JIT," Robert said. "It's an elegant solution. But this is where your theory collides with my reality."
Robert swiveled toward his desk and typed a rapid sequence. "I'm granting you temporary access so you can review the architecture. I need you to parse the historical documentation before we touch a single line."
A red pop-up window rendered on the massive screen, accompanied by a harsh, low-frequency rejection buzz.
ACCESS_DENIED: User 'Molen_T' lacks security clearance LEVEL_3.
Robert slammed his fist against the desk. "Damned bureaucracy!" he growled. "The Active Directory rejects you. Your JIT profile doesn't even have read permissions for the digital cafeteria menu, let alone the ERP source code."
"So... is it over?" Molen asked, feeling the port that had just opened beginning to close.
Robert ran a hand through his messy hair, calculating. "No. I'm not going to let an HR background script dictate how I run my department."
The Architect unlocked a secure drawer in his desk and pulled out a heavy, reinforced industrial tablet, entirely air-gapped from the mainframe network. "It's going to take me at least 48 hours to force a guest token for you without triggering security alarms. Vincent is going to be logging every move, so I have to inject this carefully."
Robert slid the tablet across the black glass toward Molen. "This holds a static dump of the last five years of logs and the architectural blueprints from the Foundation Era. It's read-only. You can't break anything from there."
Molen took the tablet. It was heavier than it looked. It carried the weight of a root responsibility.
"What do I do with this?" he asked.
"Study," Robert commanded. "I want you to cache every error, every design pattern, every single time that damn WaterFactory has coughed up blood. If you truly believe your 'Box' theory outperforms my Defensive Programming, you're going to need a lot more than cat analogies to prove it to me."
Molen nodded, slipping the device into his worn-out backpack. "When do I come back?"
"Thursday. Same time. If by then you haven't compiled a way to implement your idea without demolishing the building..." Robert left the string hanging and pointed to the door. "Now log off and get out. I have to fight with three directors to justify why I'm handing a classified tablet to a parts-swapper."
Molen exited the office, crossing back through the glass partition. As he returned to the workshop, the clean, conditioned air was abruptly overwritten by the smell of ozone and sweat.
He felt the weight of the tablet against his back. He had a 48-hour timeout. He had a night job spinning up in an hour. And he had an unsolvable bug to fix.
For the first time in his life, Molen genuinely smiled. The hunger to learn was running louder than his exhaustion.
> Enjoyed the code? If you want to buy this Dev an energy drink (BMAC)
or read upcoming chapters early (Patreon), check the links:
https://buymeacoffee.com/molaya
?? Patreon: ;
Also you can read it in my web page:
__________________________________________________________________