Studying poetry was one of my favorite pastimes.

Poetry is the densest genre, I thought. I went into detail and figured out how the different layers worked together to convey the message. The text provides the context and defines the boundaries when you're most receptive to the message.

So I went to college to learn as much as I could about this beautiful world.

At college, I found something completely different.

At the University, we only learned about the history of literature and the current analyzing trend.

They were fascinated by analyzing literature from a one-person perspective rather than narrative techniques or structuralism. I immediately lost interest because I wanted to learn about systems and methods rather than "I feel, you feel, the author feels" triangles.

I found my way out in linguistics.

In linguistics, we focus more on layers, systems, and rules.

I needed to figure out how to communicate with computers to analyze. Since I didn't know how to write code, I'd no choice but to run one Unix command after another until I got the result.

After a few years of learning coding in my spare time, I got my first job as a software developer, working on language-related problems.

As a software developer, I do the same thing I did in the beginning.

Some people still think there's a big difference between working with literature or code. For me, there's no real difference.

I'm still looking for communication patterns in the code. Each part of the system has its narrative and responsibilities. Sometimes they can even have conflicts, as in any drama, or misunderstandings occur, which are part of any comedy.

There's a narrative and messages in all systems, whether poetry or code.