Introduction:
I am a philosophy student. And I am also a coder. For a long time I did not believe those two sentences could belong to the same person.
My first encounter with coding happened before I joined the seminary. From the very first moment I was captivated. Coding felt like the most amazing thing a person could ever discover. I remember thinking that no one could possibly come across this world and not fall in love with it. It is that consuming. Once you start there is no going back. There is always that urge to continue, to know more, to build more, to understand more.
Then life took an unexpected turn and I entered the seminary to study philosophy. Suddenly I felt that coding had no place in the path I had chosen. I could not see the connection. I could not find the bridge between these two worlds. And having already fallen in love with coding, that hurt. More than I expected. But the thirst never left. The curiosity kept pulling at me quietly in the background. Eventually I could not resist anymore. I dove back in.
And what I discovered surprised me completely. These two worlds were not opposites at all. They were deeply and beautifully interconnected in ways I never imagined.
This article is for every arts student who has ever looked at a screen full of code and thought that is not for me. I want to tell you what I wish someone had told me. It might be more for you than you think.

The Biggest Misconception
Let me be honest about what happens the first time an arts student sees code.
You don't even look at it twice.
It looks impossible. A wall of strange symbols, brackets and words that seem to belong to a completely different universe. Your brain immediately whispers — this is not for you. So you look away and move on.
But then something unexpected happens. Curiosity begins to grow quietly in the background. You start wondering what does this actually mean? What is it doing? How does it work? That small whisper of curiosity becomes a persistent voice that refuses to go away.
And then comes the moment you actually start to understand something. One concept. One line. One small piece of the puzzle clicks into place.
That moment feels incredible. Almost indescribable. Like being handed a key to a secret world that you were told was locked to people like you.
That is the great misconception about coding and arts students. The difficulty you see at first glance is not a wall it is a door. It looks impenetrable from the outside. But the moment you push through even slightly everything changes.
The code that once looked impossible begins to look like a language. And like any language with patience, curiosity and time it can be learned by anyone willing to try.

** What Arts Actually Gives You**
Here is something that might surprise you. Arts students do not come to coding empty handed. They come loaded with skills that pure tech students spend years trying to develop.
Let me explain.
Philosophy taught me critical thinking at a deep level. Not just the ability to think but the ability to think correctly. To examine a problem from multiple angles, question assumptions, build logical arguments and arrive at sound conclusions. That is not a soft skill. That is the foundation of good programming.
When a piece of code breaks a tech student might panic or randomly try different solutions hoping something works. A philosophy student approaches it differently. They sit with the problem calmly, trace the logic carefully and argue their way to the answer step by step. That is critical thinking in action.
Arts students also bring something else that is rare in the tech world creativity. Coding is not just about writing correct syntax. It is about solving problems in elegant and innovative ways. Philosophy, literature, theology and the humanities train the mind to think beyond the obvious, to see connections others miss and to approach old problems with fresh perspectives.
And then there is analysis. Arts students are trained to read complex texts, extract meaning and communicate ideas clearly. These are exactly the skills needed for writing clean code, clear documentation and effective tech content.
The truth is arts students do not lack what it takes to code. In many ways they have what pure tech students are missing. The advantage is already there it just needs to be recognised and used.

** The Career Misconception**
When I was purely in the arts world my vision of my future was narrow. Not because I lacked ambition but because no one had shown me the full picture. I thought my options were clear and limited become a scholar, a teacher or a lecturer. Respectable paths all of them. But a small and predictable map for a big and curious mind.
Coding felt like it belonged to a completely different career universe. One that had no door marked "arts students welcome here."
I was wrong.
The moment I began to see how deeply arts and coding are intertwined everything changed. Doors I never knew existed suddenly swung open. Tech writing combining the ability to explain complex ideas clearly with technical knowledge. AI ethics using philosophical training to navigate one of the most important conversations of our generation. App development building real tools that solve real problems for real people. Content creation in the tech space, sharing knowledge and experiences that help thousands of beginners find their way.
None of these paths require you to abandon your arts background. In fact they demand it. They need people who can think deeply, write clearly, reason ethically and communicate effectively. They need people exactly like you.
The arts did not close career doors for me. It just took coding to show me how many more were waiting to be opened.

The Moment You Fall In Love With It
Let me tell you something that will show you just how consuming coding can become.
There was a year in my life where I had no access to any electronic device. No phone. No computer. No screen of any kind. Just books, thoughts and time.
And yet coding never left me.
Every time my mind wandered it went to code. I would sit with my notebook the kind meant for lecture notes and philosophy essays and write code by hand. No compiler. No screen to run it on. No way to know if it worked. Just me, a pen and the burning need to express something that had taken hold of me completely.
The feeling was indescribable. Like a fire that refused to go out no matter how little fuel it had. My greatest wish during that entire period was simple to get access to a computer. To find a platform where I could learn. To get back to the thing that made me feel most alive.
That is what coding does to you when it truly gets hold of you. It does not let go. It follows you into rooms with no screens. It fills notebooks that were never meant for it. It burns quietly and persistently until you find your way back to it.
If you have ever felt even a fraction of that curiosity about coding then listen carefully, that feeling is not random. It is not a passing interest. It is a calling worth answering.

Who Is Coding Really For?
Most people carry a hidden assumption about coding. They believe it is reserved for a certain kind of person. Someone with expensive equipment, fast internet, the latest laptop and unlimited access to technology. They believe coding belongs to the privileged to those who grew up surrounded by screens and gadgets and opportunities.
But that assumption is wrong. And my story is proof.
I wrote code in a notebook with no computer in sight. I learned Flutter with a borrowed device and a slow connection. I built an android app while carrying the weight of philosophy assignments and seminary life. None of those conditions were ideal. None of them stopped me.
Because coding is not about what you have. It is about what burns inside you.
I have come to believe that coding can attract anyone. It does not discriminate based on your background, your degree, your resources or your career path. It is open to the curious, the persistent and the passionate, regardless of where they come from or what they studied.
And here is the most important thing I want to say directly to every arts student reading this.
If you are sitting there wondering whether coding is for you, that question itself is your answer. The curiosity you feel, the pull you cannot quite explain, the way you keep coming back to this question even when logic tells you to walk away, that is not confusion. That is a calling.
Coding is for you. It has been waiting for you all along.

Conclusion
If there is one thing this journey has taught me it is this coding does not require a specific degree, a specific background or a specific kind of mind. It requires an open one.
An open mind that is willing to sit with confusion until it becomes clarity. An open mind that sees a wall of strange symbols and chooses curiosity over fear. An open mind that believes the impossible is simply the unfamiliar and that the unfamiliar can always be learned.
I came to coding as a philosophy student in a seminary with no computer, no ideal conditions and no roadmap. I wrote code in notebooks. I lost sleep over debugging errors. I rebuilt projects from scratch after updates wiped everything away. None of it was easy. All of it was worth it.
And if I could go back and say one thing to my younger self standing at that crossroads wondering whether coding had any place in an arts student's life, I would say this. Stop wondering and start. The path reveals itself only to those who begin walking.
Coding is possible for anyone who is genuinely interested and truly ready to explore. Your arts background is not a barrier, it is a bridge. Your philosophical training is not irrelevant, it is your greatest advantage.