There are a few obsessions that almost grab you by your throat with the amount of interest you develop in them (lmao look at you for instance). You feel genuine love for it before you could simmer down to what it is that makes you so invested in that obsession. For me, it was poetry and coding. Pretty odd, innit? How can something that is mainly so technical and rigid merge with something so fluid and almost unpredictable?

The difference is that_ both of them are playing with rules and regulations_ instead of confiding in it. Poetry mutates grammar to bleed; coding forces syntax to *_inovate`

Back when I was learning coding, I would play around with the given rules, adding and deducting, making and breaking to create new efficient codes. When I started writing poetry, I would play with my words, tease ’em up, make something with the words. Both poetry and coding are like building blocks — you use, replace, and turn them around and make something entirely new with them.

# Code as Poetry
def love_letter():
while alive:
print("You are my semicolon;")
print("I run only with you.")


// Poem as Code
if (emptiness == cup) {
death = true;
}


Lack of experimentation in poetry and coding takes away the joy in doing both. I like it when I get bold in my poetry and coding. I like to playtease with my codes and words, making a new meaning, a new purpose to it. I like it the most when the words i played with and the codes i tried to do differently come out so good

Poems and codes are also very similar as:

• Move a bracket or miss a space, your code crashes meanwhile, a difference in punctuation,line or word changes the entire poem.
• Both of them produces magic, in hearts and in machines.
• Both of them require to learn the rules to play with them.

Coding and Poetry — They could be distant cousins. They both have many rules and regulations that you can play with and see which one you would like more. They both require you to think out of the box and, most importantly, both are so generously rewarding, like the feeling you ate after you compared the empty cup to death or when you made your program much better than how it was before. You’ve got to add, break, make, and shake to create something that stays, both in your machine and heart.So next time ou come across a rigid code,ask what would Edgar Allen Poe do.

Before y'all come for my neck, think.

• Doesn't debugging feel exactly like rewriting a metaphor till it lands?