"Another NPE in the resource module?" the voice came muffled from the development area, separated by an immaculate glass partition. "It must be the cache. Give the node a reset and clear the logs. That should hold it until Friday."
Molen paused his tool for a millisecond. A reboot doesn't solve the issue, it merely postpones it, he thought, visualizing the stack trace of the error in his mind. But he said nothing. He was a JIT, a Level 1 support technician. His voice lacked write permissions in architecture meetings.
He was one of the many JITs (Just-In-Time) who sustained the invisible infrastructure of the world. In the technocratic social pyramid, they were the brute force workforce, the self-taught coders who had scaled the ranks through relentless practice and teardowns, not through standardized curriculums. They were hot-compiled code: unstable to some, but fast and adaptable.
On the other side of the glass were the Soli, the elite. Graduates from the Global Consortium Universities, possessors of a verified intellectual "pedigree" and certified skills. The partition separating Molen's workshop from the climate-controlled office wasn't just physical; it was the unbreakable firewall of a caste system.
"Molen!" the shout cut through the air. "Stop trying to parse what the engineers are saying. Your JIT brain is going to overheat if you try to process high-level logic. Focus on the boards."
Vincent, the Department Head, approached with his arrogant stride. He was tall, lean, and wore a metallic-gray suit that only a Soli salary could afford. On his lapel gleamed the pin of the "Order of Solidity." For Vincent, that badge was a divine barrier against the scum.
Molen lowered his gaze, not out of submission, but out of survival. He knew how the architecture of the world worked. At the base layer were the Natives, the base class: humans with no technological affinity, destined for repetitive loop tasks. Then came him, a JIT: possessing raw power and low latency, but lacking credentials. And at the top was Vincent, a Soli who, ironically, possessed less actual technical skill than many JITs, but whose university degree acted as a lifetime VIP token.
Vincent lightly kicked one of the spare parts boxes.
"We have a batch of 1,000 mainboards with blown capacitors," he said, pointing to the mountain of hardware. "You have 15 days to replace them. My best technicians—engineers with real degrees, who actually studied—take 30 minutes per unit. Do the math: that’s over 60 days of work. If you don't finish, you'll be pulling unpaid overtime nights. It's the price for your lack of... pedigree."
Molen glanced at the wall clock. He had been on this task for three days. He calculated the exact runtime it took him to swap a single mainboard and replied.
"I won't need overtime, sir," he said with a calm that irritated his boss. "My calculations say I will finish in 10 days. In fact, I plan to finish 5 days ahead of your deadline."
Vincent's laugh was dry, the sound of a compilation error.
"Ten days? Your self-taught arrogance is what keeps you grounded, Molen. No one beats the baseline metrics set by the Manufacturer's Manual."
"Let's make a bet, then," a new voice interjected.
The deep voice echoed from the server room entrance. Robert, the Principal Architect and backend Tech Lead. Unlike Vincent, Robert didn't wear a suit. He wore a black cashmere hoodie bearing the discreet logo of an underground backend architecture conference—strictly forbidden to JITs—and branded tactical pants. His hair was messy, threaded with premature gray that betrayed far too many late-night deployments, and deep, dark circles under his eyes that spoke of a life entirely committed to the codebase.
Robert's presence shifted the atmospheric pressure of the room. If Vincent had administrative authority, Robert had Root privileges. Even Vincent shrank slightly; he knew Robert was the only one capable of keeping the core system alive, and that his salary tripled his own.
Robert observed Molen with an analytical, cold, and calculating gaze. There was no warmth in his eyes, only the gleam of a data miner who had just struck a gold vein in the mud. Where Vincent saw insolence, Robert saw throughput, potential. He saw an unoptimized resource, a high-performance processor being bottlenecked by basic background tasks, and his greedy mind was already calculating the ROI (Return on Investment) of claiming that talent.
"If Molen finishes the 1,000 swaps in the timeframe he claims, you pay him a month of your salary," Robert said, a smile failing to reach his eyes. "And, more importantly, you will allow him a seat at our table to listen to the ERP problem."
This story is posted elsewhere by the author. Help them out by reading the authentic version.
Vincent hesitated. A month's salary was painful, but throwing an exception at Robert was professional suicide. Besides, the public humiliation of a "JIT" like Molen was too tempting to pass up.
"Done. But if he fails, he works for free for three months and admits before the entire department that his empirical 'technology' is garbage compared to real engineering."
Every gaze locked onto Molen. Though the two titans had defined the parameters, the transaction couldn't be committed without his digital signature. It was his time and his life on the table.
Molen wavered. His mental processes entered a risk evaluation loop. He had been working at Macro-Systems for barely four days. He absolutely depended on that paycheck for rent and food, and although he ran a background job at night, he had no fail-safe. Winning the bet meant humiliating Vincent, his direct supervisor, a petty and vindictive man. Making an enemy out of a Soli with administrative power in his first week was, objectively, a terrible survival strategy. Vincent could make his life impossible with fragmented shifts, false bug reports, or "glitches" in his payroll until he forced a resignation.
Is it worth risking my livelihood for pride? he thought, feeling a cold sweat drop down his spine.
But then he looked at Robert. The offer wasn't the money; the money was just a temporal buffer. The real payload was the access. Listening to the ERP problem. Seeing how the "Architects" processed logic. It was a chance for vertical scaling that no JIT had ever been granted. A backdoor into the system they had always locked him out of.
Molen recalculated.
Risk: Critical. Reward: Exponential. Probability of success based on current skill parameters: 99.9%.
The fear of poverty clashed against a ravenous hunger to learn. He knew the knowledge he would parse at that table was worth any risk. The hunger won.
"Deal," Molen said, his voice firm, breaking the silence and staring directly into Vincent's eyes. "1,000 boards in 10 days. If I fail, you own my time for free. If I win, I want that seat at the table. And with it, the chance to stand at the starting line—to develop software," he thought.
The Process: Physical Refactoring (Days 4 to 10)
The other three certified technicians operated following the official algorithm: Unscrew chassis -> Extract power supply -> Disconnect drives -> Extract motherboard -> Replace -> Reassemble. A linear, safe, and terribly inefficient sequence. O(n2) in terms of effort.
Molen, however, had detected that the manual was "Legacy Code." It was written for towers from five years ago.
He had developed a Physical Exploit:
- Minimal Dependency Injection: He discovered that by loosening just two bolts on the drive bay and using a flexible tool, he could slide the motherboard out without unmounting the power supply or the hard drives.
- Tool Optimization: He used a modified magnetic extractor (custom-built from an old hard drive's scrapped magnets) that caught screws mid-air, completely eliminating search and drop latency.
- Latency Elimination: His movements had no blocked threads. While his left hand disconnected the SATA buses, his right hand already had the screwdriver positioned on the next anchor point.
It was a continuous pipeline. It wasn't manual labor; it was high-performance execution.
Vincent's jaw dropped on the eighth day. Molen's error rate was 0%. The Soli technicians, bound to their deprecated manual, looked like single-core processors trying to benchmark against a dedicated GPU.
The Output - Day 10. 15:00 hours.
The final screw locked into place with a satisfying click. Silence flooded the workshop. Molen had finished with time to spare.
Robert walked in, completely bypassing a red-faced Vincent who was sputtering excuses about how Molen must have surely cheated or bypassed security protocols, arguing that since the manual's instructions weren't followed, the execution shouldn't count.
Robert didn't even parse the manager; his attention was locked onto the final output: 1,000 machines online and ready.
"The hardware has passed the power-on tests, Vincent. Pay up and shut up," Robert said, with the indifference of someone dismissing a warning prompt.
Then he turned toward the young technician, toward the JIT. He placed a heavy hand on Molen's shoulder, a gesture that looked paternal but felt like a thread lock. This kid could scale me to new levels in the company, he thought.
"Come with me, kid. We have a problem in the Kingdom of Nouns."
Robert leaned in slightly, dropping his voice so only Molen could catch the audio.
"Your hands can hack the hardware, and that is useful. But I want to see if your mind can do the same with the code. Let's see if you can leverage this improbable opportunity, Molen; I hate wasting potential investments."
Molen wiped the thermal paste and grease off his hands with an old rag, feeling the heavy weight of that calculated gaze. He knew they weren't doing him a favor; they were provisioning him as a tool. But as he looked up and saw the glass partition, he knew it was a cost he was willing to pay.
JITs were not permitted—neither at Macro-Systems nor at any company owned by the three major families—to participate in the software life cycle. Without a certification badge, the furthest he could ever compile was cleaning workstations or replacing mainboards.
The glass had always seemed like a prison firewall, an abyss separating reality from imagination, the possible from the impossible. Today, it looked like an open port.
It was the first step toward Binarium, though he didn't know it yet.