From philosophy to code: critical thinking in programming

Before fully dedicating myself to development, I studied Philosophy. At first glance, it might seem far from programming, but my philosophical training has been one of my greatest strengths as a developer.

In philosophy, I learned to analyze problems from multiple perspectives, to question assumptions, and not to settle for the first answer. That habit of looking for root causes translates today into how I write and debug code: I don’t just patch errors—I try to understand why they happen and how to solve them in a solid, lasting way.

Formal logic and critical reasoning, core parts of philosophical study, also gave me a valuable foundation. Solving an algorithmic problem or designing a project’s architecture isn’t far from building a coherent argument: in both cases, it’s about structuring ideas, spotting contradictions, and finding elegant solutions.

Philosophy also taught me the importance of clarity in communication. Just as a good argument must be understandable, good code must be readable to others. That perspective constantly reminds me that programming isn’t only technical—it’s also collaborative.

Ultimately, my degree in Philosophy wasn’t a detour; it’s a foundation that has accompanied me to this day. It gave me a critical mindset and a different way of facing technological challenges, showing that abstract thinking and programming aren’t just compatible—they enrich each other.