The Algorithm of Us

The Love Optimizer

Maya’s apartment smelled like burnt coffee and failure.

She’d been staring at her laptop for three hours, the cursor blinking at her like a judgmental metronome. The kiss was still burning on her lips. She could still feel the way Leo’s hand had cupped the back of her head, the way his thumb had traced the curve of her jaw, the way her entire nervous system had screamed *yes* while her brain screamed *abort mission*.

She’d walked away. She’d said, “This wasn’t in the contract.” She’d left him standing in the conference room with that crooked half-smile fading into something she didn’t want to name.

Now she was doing what she always did when emotions threatened to crash her system: she coded.

The document on her screen was titled *Love_Optimizer_v1.0.py*. It was ridiculous. It was desperate. It was the only thing that made sense.

Maya cracked her knuckles and started typing.

*# Variables*
*trust_factor = 0.0*
*compatibility_score = 0.0*
*risk_of_heartbreak = 0.0*

She paused. Her fingers hovered over the keyboard. This was insane. You couldn’t quantify a person. You couldn’t reduce Leo—chaotic, brilliant, infuriating Leo—to a set of parameters.

But she could try.

She pulled up her notes from the past three months. Every interaction, every staged date, every unscripted moment. She’d been documenting everything for the campaign, but now she repurposed the data. She assigned weights. She created categories.

*Category 1: Reliability*
Leo showed up late to 73% of their scheduled events. But he showed up. He never canceled. He once walked twenty blocks in the rain because his phone died and he didn’t want to miss their “fake” coffee date.

Score: 6.5/10.

*Category 2: Emotional Availability*
He’d admitted on the live stream that he was afraid of failure. He’d told her about his father, about the pressure to be brilliant, about the nights he spent rewriting code until his eyes bled. He’d let her see the cracks.

Score: 8.2/10.

*Category 3: Physical Chemistry*
Maya’s face flushed. She typed the number without thinking.

Score: 9.8/10.

She deleted it. Rewrote it as 9.4. Deleted that too. Left it blank.

*Category 4: Risk of Repeating Past Patterns*
This was the hard one. She created a sub-algorithm based on Mark’s betrayal. The variables were simple: sudden interest in spontaneity, decreased communication, increased time away. She ran Leo’s data through it.

He was erratic. He disappeared for hours when he was in “flow state.” He forgot to text back. He once left her on read for six hours because he was debugging a memory leak.

But he always came back with an explanation. A screenshot of the code. A voice memo apologizing. A burrito from the place she liked.

The algorithm couldn’t decide. It returned a 47% probability of replication.

Maya stared at the number. That was too high. That was almost half.

She added more variables.

*Variable 5: Shared Values*
They both believed in building things that mattered. They both hated corporate jargon. They both thought the billionaire’s “authenticity” obsession was performative, even if they were benefiting from it.

Score: 9.1/10.

*Variable 6: Communication Style*
He was direct. She was precise. They argued in metaphors—he used code, she used user flows. They understood each other’s languages.

Score: 8.7/10.

*Variable 7: Willingness to Grow*
He’d thrown away her script for the live stream. He’d answered honestly. He’d made her answer honestly. He’d kissed her without asking permission.

Maya’s hands stopped typing.

She looked at the numbers. She ran the final calculation.

*compatibility_score = (reliability * 0.15) + (emotional_availability * 0.25) + (shared_values * 0.25) + (communication * 0.20) + (growth_willingness * 0.15)*

The result: 94.2%.

A near-perfect match.

But then she ran the risk assessment.

*risk_of_heartbreak = (past_pattern_risk * 0.40) + (unpredictability * 0.30) + (fear_of_intimacy * 0.30)*

The result: 78.3%.

Maya’s stomach dropped. She stared at the two numbers side by side. A 94% match. A 78% chance of getting destroyed.

She closed the laptop.

The apartment was silent except for the hum of the refrigerator. She walked to the window and looked out at the city lights. Somewhere out there, Leo was probably doing something chaotic—eating cold pizza, rewriting the same function for the fourth time, sketching something on a napkin.

She thought about the kiss.

She thought about Mark.

She thought about the way Leo had looked at her when she said the kiss wasn’t in the contract. Like she’d punched him in the chest.

Her phone buzzed.

**Leo:** *You okay?*

She typed back: *Fine. Just processing.*

**Leo:** *Processing. Right. Because emotions are data.*

**Maya:** *Everything is data.*

**Leo:** *Is that what you’re telling yourself?*

She didn’t answer. She opened the laptop again.

The algorithm was incomplete. She needed more inputs. She needed to account for the variables she couldn’t measure—the way he laughed when she made a dry joke, the way he remembered she hated cilantro, the way he’d held her hand during the drone show without being prompted.

She added a new category: *Intangible Factors*.

She gave it a weight of 0.10. She assigned a score of 9.9.

The compatibility score jumped to 95.1%.

The risk of heartbreak stayed at 78.3%.

Maya slammed the laptop shut again. This was useless. She was trying to quantify something that couldn’t be quantified. She was trying to build a safety net out of code.

Her phone buzzed again.

**Priya:** *You’re still awake. I can tell. Stop coding your feelings.*

**Maya:** *I’m not coding my feelings.*

**Priya:** *You’re literally building an algorithm for love. I can hear you typing from my apartment.*

**Maya:** *It’s not for love. It’s for risk assessment.*

**Priya:** *Same thing. Go to sleep.*

Maya didn’t go to sleep. She opened the laptop again and stared at the numbers.

94%. 95%. 78%.

She thought about what Leo had said during the live stream. *I’m afraid of failure because I’ve never been taught that failure is an option.*

She thought about what she’d said. *I’m afraid of being left because I’ve been left before.*

They were both broken. They were both trying to optimize their way out of pain.

She deleted the algorithm.

Then she reopened the trash and restored it.

Then she deleted it again.

Then she closed the laptop, walked to the kitchen, and poured herself a glass of water she didn’t drink.

Her phone buzzed a third time.

**Leo:** *I’m not going to apologize for the kiss.*

**Maya:** *I didn’t ask you to.*

**Leo:** *You’re running calculations, aren’t you?*

Maya’s breath caught. How did he know?

**Maya:** *Maybe.*

**Leo:** *What’s the verdict?*

She stared at the screen. She could lie. She could say the algorithm was inconclusive. She could say she needed more data.

Instead, she typed: *94% match. 78% risk.*

**Leo:** *78% risk of what?*

**Maya:** *Heartbreak.*

Three dots appeared. Disappeared. Appeared again.

**Leo:** *So there’s a 22% chance we don’t break each other.*

**Maya:** *That’s not how probability works.*

**Leo:** *That’s exactly how probability works. You’re just looking at the wrong number.*

Maya set the phone down. She picked it up again.

**Maya:** *What number should I be looking at?*

**Leo:** *The one that says 94. That’s higher than any code I’ve ever written. That’s a solid build.*

She laughed. It came out broken, half a sob.

**Maya:** *You can’t code a relationship.*

**Leo:** *You literally just tried to.*

**Maya:** *And it failed.*

**Leo:** *Did it? Or did it tell you exactly what you already knew?*

She didn’t answer. She couldn’t.

**Leo:** *I’m not Mark, Maya. I’m not going to leave because you’re too “structured” or “predictable.” I like your structure. I like that you have a system. I like that you think about things before you do them. It’s the opposite of me, and it’s terrifying, and I want to see where it goes.*

Maya’s eyes burned. She blinked hard.

**Maya:** *What if it goes wrong?*

**Leo:** *Then we debug it. Together.*

She stared at the words. *Together.* It was such a simple word. Such a terrifying word.

She looked at the closed laptop. The algorithm was still in the trash. She could empty the trash. She could pretend she never built it.

Or she could keep it. As a reminder. As a warning. As a map of her own fear.

She opened the laptop. She restored the file. She renamed it.

*Love_Optimizer_v1.0_FAILED.py*

Then she typed a single line at the bottom:

*# This algorithm cannot measure forgiveness. It cannot measure growth. It cannot measure the way he looks at me when he thinks I’m not paying attention.*

She saved the file. She closed the laptop.

Her phone buzzed one last time.

**Leo:** *Are you going to run the program?*

Maya smiled. It was small. It was fragile. It was real.

**Maya:** *I’m thinking about it.*

**Leo:** *Take your time. I’ll be here.*

She set the phone down. She walked to the window. The city was still awake, a grid of lights and possibilities.

She didn’t know what she was going to do. She didn’t have a roadmap. She didn’t have a script.

For the first time in years, Maya Chen didn’t have a plan.

And it terrified her.

And it thrilled her.

She looked at her reflection in the glass. She looked tired. She looked scared. She looked alive.

Tomorrow, she would figure it out. Tomorrow, she would talk to Leo. Tomorrow, she would decide if she was brave enough to run the program without a safety net.

But tonight, she let herself feel the weight of the 94%.

She let herself hope.