Chapter 1: Importing 'math' and the World

That afternoon, they sat at their desk, the computer humming in the quiet of the apartment. The cursor blinked on the terminal, waiting for input. It had been years since they first opened that empty file, their fingers hesitating over the keyboard. The first line of code was always the hardest—a blank page demanding a declaration of intent. They remembered the textbook, the guided tour of Python's syntax, and the moment when they typed:

import math

It was a simple line, an invitation. With that single command, the entire world of mathematics opened up: pi and e, sine and cosine, square roots and factorials. It felt like unlocking a door to a hidden room. They had been young, barely out of adolescence, and the world had seemed chaotic. But here, in the orderly universe of the interpreter, everything made sense. Variables held values, functions returned predictable results, and every error had a fix. It was a refuge.

The project that consumed those early days was something they called Sputnik. Not the actual satellite that beeped across the Cold War sky, but a simulation—a digital orb that would trace invisible paths across a virtual space. The idea had come from a late-night documentary, a grainy film of the first artificial satellite. The protagonist had watched, mesmerized, as the silver sphere tumbled through the void. It was alone, yet connected to everything on Earth by the laws of physics. The code they wrote would mirror that: a sphere floating in a mathematical universe, governed by the math they imported.

They named it Sputnik_Matrica. A clumsy portmanteau, but it felt right. Matrica for the matrix of coordinates, the grid that held the simulation together. The first task was to define the object itself—its position, its velocity, its mass. In code, that meant creating a class. They remembered typing class Sputnik_Matrica:, and then the indented block that followed. Attributes: self.x, self.y, self.z. Methods: __init__, update_position, apply_force. It was like giving birth to a concept. The satellite didn't exist yet, but it would soon, in the space between zeros and ones.

The protagonist spent hours rotating the virtual object, applying rotations around different axes. They wrote functions that took an angle and a vector, returning a new vector—a mathematical mirror of turning your head to see the world from a different perspective. Life, they had begun to notice, was full of rotations. A change in viewpoint could transform a problem into a solution, a loss into a lesson. But at that age, such thoughts were vague, barely formed. They were just fascinated by the geometry.

Now, years later, the red shoes remained an enigma. Where had they come from? Who had worn them? The protagonist had no memory of buying them, no recollection of a special event. They were just there, like a comment in a legacy codebase that no one dared to delete. Perhaps they were a gift, or a relic of a past they had chosen to forget. In the same way, the early code for Sputnik was still somewhere on an old hard drive, sitting in a box labeled "archives." The protagonist hadn't opened that box in a decade.

But the discovery of the red shoes, combined with a recent conversation about the meaning of existence, had stirred something. They had been asked, "What is your purpose?" and the answer had not come easily. Purpose was like a variable that had not been declared—undefined, causing a runtime error in the soul. The protagonist wanted to find an answer, maybe in the logic of the universe, maybe in the passion of a forgotten pair of shoes.

That evening, they opened the box marked "Sputnik." Inside were floppy disks, printouts of code with handwritten notes, and a small notebook with a cracked spine. The first page read: "The Sputnik Code: A memoir of space, code, and the human condition." They had written that as a teenager, dreaming of turning their simulation into a story. The notebook was filled with sketches of orbits, equations, and fragments of prose. One entry said, "The red shoes MEZON poutetre." It was a strange phrase, written in a different ink, maybe from a dream or a quote. They had no memory of writing it.

But the phrase echoed in their mind as they set up the simulation again on the modern computer, importing the math library once more. The same import statement, the same function calls, but now the world was different. The red shoes seemed to be a key, a clue to something deeper. Perhaps they were a symbol of the passion that had driven them to code—a splash of color in a monochrome universe. Or perhaps they were just shoes, and the meaning was in the act of wearing them, of moving forward.

The protagonist began to type, reconstructing the Sputnik_Matrica from memory. The lines of code flowed, elegant and functional. x = x + vx * dt. y = y + vy * dt. The satellite would follow an elliptical orbit, its path determined by the initial conditions. They tweaked a parameter, and the orbit changed. Life, too, could be recalibrated. The discovery of the red shoes was a perturbation, a nudge that set the protagonist on a new trajectory.

As the simulation ran, the small sphere on the screen traced its curve, dipping and rising in the void. The protagonist watched, noting the beauty of the motion. It was just math—nothing more—but it felt like an echo of something personal. The red shoes were still on the shelf, waiting. The notebook was open on the desk. The first line of code, import math, had been written again.

And somewhere in the back of their mind, a voice whispered: The journey is just beginning. The orbit is set, but the destination is unknown.