Today is my one year workaversary, which also happens to be my one year anniversary of being a professional developer. (“Professional developer” still feels weird to say/write.) It’s been a year full of professional challenges and victories, and I’ve felt prepared every step of the way.
I accomplished my first year as a developer because of my family and friends. Because of my instructors, classmates, community, and training at The Iron Yard. And more and more over the past year I’ve realized that I accomplished my first year as a developer in some part because of my liberal arts education and humanities background.
But…a humanities degree from a liberal arts college…applicable to front end development? I know, I’ve heard the skeptics’ sounds before. Writing a thesis on media coverage of major oil spills through the lens of Ulrich Beck’s Risk Society and architecting and documenting a pattern library are different. However, the core skills and competencies I learned in undergrad have been invaluable to my work as a front end developer. Here are four of the biggest lessons from my liberal arts education I’ve carried with me:
During my time in undergrad, I got the most of my education when I took time to think about how my classes related to each other. I took a class that combined film theory, communication studies, and history. Sometimes I would walk out of a comm ethics class thinking about what I learned in environmental studies earlier that week. My studies were enriched because of the parallels I could draw between courses.
At work, specifically, there’s a way for all four disciplines (research, UX, visual design, and front end development) to work together. The work that is produced from an interdisciplinary approach is undeniably better than work produced if everyone worked in a bubble. We can all learn from each other, grow, and better our own work because of that knowledge.
Critical and Creative Thinking
When I was exposed to a different or unorthodox perspective in a reading assignment or class discussion, I had to reconcile how it fit with my own worldview. I had to really think and have solid reasoning as to why or why not I held a certain view. “Because I’ve always felt this way” was never an acceptable answer.
As a front end developer, I solve problems daily. Whether it’s thinking about the structure of the project, the structure and architecture of the code itself, debugging, or working with the designers on the team—there are always challenges to solve and learn from. “Because this is the way it’s always been done” is never an acceptable answer.
In undergrad, I wrote papers in all of my classes, including science and math. Writing helped the ideas I was learning make more sense. Writing allowed me to put the theories that I learned into practice and helped me understand what I learned. Writing also helped me make sure that I could communicate my ideas to my peers and professors in a way they could understand. Writing is how I grew.
Writing is a critical skill for developers. Whether it’s documenting code, documenting your process/product (in a way that doesn’t assume a certain level of familiarity so that everyone can understand), or sharing something you know on your blog or in a response to a question on StackOverflow, developers need to know how to write. I think it’s a huge part of how we grow.
How, Not What, to Learn
The most valuable skill I learned in my liberal arts education was how to learn. I was never spoon fed what I need to learn in order to pass some test. Instead, I learned how to search for what information was missing in my understanding of a topic and make the most of a resource. It was a critical mindset to have.
Being a front end dev requires this skill. Whether it’s learning a new language or (another) JS framework, a new naming convention, etc. There is always something new to learn, and it’s up to me to find the resources and learn.
So, Mama Millsaps, here’s to you for preparing me for a career I never thought I would have. Go Majors.