Data Structures of the Heart - Building and Managing Relationships

I reached for my phone on the nightstand and opened the voice memo app. The last recording, from the night before, was still there: ‘Chapter Two. Or maybe it is still Chapter One.’ I smiled and deleted it. I had started a new chapter now, and I needed a fresh recording.

‘Chapter Three,’ I said into the microphone. ‘Data structures of the heart. How do we organize the people in our lives? In programming, we have arrays, lists, dictionaries, trees. Each has its strengths and weaknesses. An array is simple—a linear collection, easy to access but rigid. A linked list is more flexible, but you have to traverse it node by node. A dictionary uses keys and values, allowing you to find someone instantly if you know their name. But what happens when the key changes? What happens when the data becomes corrupted?’

I paused the recording and sat up. The metaphor was fitting, but it felt too abstract. I needed a concrete example. I thought of Ričardas. He was like a linked list—reliable, sequential, always there when I needed to traverse my thoughts. I knew exactly how to reach him: a walk down the street, a knock on his door. But there were others in my life, people I had not seen in years, whose keys I had lost. Mr. Kvedaras, for instance. I had not spoken to him since I left Lithuania, but his influence was still in my code.

I decided to visit him. It was a Sunday, and I knew he would be at home, tending to his garden or reading. I dressed quickly and walked to the bus stop. The morning air was crisp, carrying the smell of damp earth and fallen leaves. As the bus carried me through the outskirts of the town, I watched the houses blur past and thought about the different data structures I had used in my life.

When I was a teenager, I had kept a notebook of friends—a simple array, each name in a row. I added new friends at the end, and when a friendship ended, I crossed out the entry with a single line. It was crude, but it worked. In my twenties, in England, I had tried to build a more sophisticated system: a social calendar, a network of contacts, a mental map of who owed me what. But people are not static data. They change, they move, they delete themselves from your array without warning.

The bus arrived at the stop near Mr. Kvedaras’s house. It was a small, neat cottage with a red-tiled roof and a garden full of late-blooming roses. I knocked on the door, and after a moment, it opened. Mr. Kvedaras looked older than I remembered—his hair was white, his face lined—but his eyes were the same: sharp, kind, and full of curiosity.

‘Danguole,’ he said, surprised. ‘Come in, come in. It has been too long.’

I stepped inside. The house smelled of old books and tea. We sat in his living room, surrounded by shelves of programming manuals and literary classics. He poured me a cup of chamomile tea, and I told him about my writing, about the online comments, about the metaphor of data structures.

He listened without interrupting. When I finished, he nodded slowly. ‘You are trying to organize your relationships like code,’ he said. ‘But code is static until you run it. People are always running. They are processes, not data.’

‘Then how do I manage them?’ I asked.

‘You don’t manage people,’ he said. ‘You interact with them. Think of an array in a dynamic language like Python. It can grow, shrink, change type. You can append a new element, pop an old one, or sort the entire list. But the array itself does not control the elements. It just holds them. Your heart is the array. The people are the elements. You cannot control what they do, but you can choose how to arrange them.’

I thought about that. It was a subtle distinction, but important. For years, I had tried to control my relationships—to keep them in neat rows, to avoid conflicts, to predict outcomes. But that was not how people worked. They were messy, unpredictable, full of bugs.

‘And what about the empty spaces?’ I asked. ‘When someone leaves, there is an empty slot in the array. Do I fill it with a placeholder, or do I let it remain?’

Mr. Kvedaras smiled. ‘In programming, an empty slot can cause an index error if you try to access it. In life, an empty slot is just a memory. You can leave it empty and move on, or you can fill it with something new. But you must be careful not to overwrite the old data completely. That is how you learn.’

We talked for another hour, about algorithms, about life, about the nature of literalness. He reminded me that people are literal in their own way—they say what they mean, but they often mean more than they say. The key is to read between the lines, to parse the subtext, to handle exceptions gracefully.

When I left, the sun was high and warm. I walked back to the bus stop with a lighter heart. Mr. Kvedaras had not given me a solution, but he had given me a new perspective. Relationships were not about control. They were about flexibility, about being able to resize the array without crashing.

On the bus ride home, I took out my phone and checked my notifications. There was a new comment on my reply to DigitalNomad42. It was from a user I did not recognize: ‘I enjoyed your response. It reminded me that even in the chaos of online interactions, there can be grace. I would love to read more of your writing if you share it.’

The username was ‘DulcineaSeeker.’

I stared at the screen. Dulcinea. The name was not a coincidence. It was a signal, a key in a dictionary I had not yet built. I felt a flutter of hope—or was it foolishness? I had spent so long chasing an idealized reader that I had forgotten that real readers could be kind.

I typed a reply: ‘Thank you. I am still learning how to write, but I share most of my thoughts on my blog. The link is in my profile. I would be honored if you read them.’

I hit send and put the phone away. The bus rumbled on, carrying me back to my life, my writing, my data structures. But something had shifted. The array of my heart had grown by one element. And for the first time in a long time, I was not afraid of what the new data might bring.