How to Survive a Software Engineering Degree as a Social Anthropologist
Oops, I did it again… With a Master’s degree in Social Anthropology (or Ethnology, to put it the more European way) I ended up working in an IT company. Inspired by the empowering ability of my co-workers to build things, I tried to grasp what they’re doing by using online programming courses. Some time passed and I found myself accepted by CODE University of Applied Sciences.
So, to all the Anthropologists or Social Scientists, who consider a career in Tech, I’d like to share my personal experiences so far — and the advice I would give to my old self a year ago. Hopefully my insights also make sense to you.
1. Be prepared to enter Babylon
As always, when you are entering a new field, you’re going find yourself surrounded by people “speaking in tongues”. But this time, not only the language seems cryptic, but also the various underlying concepts. Never mind, you are trained in grasping (sub-)cultures, right? You gonna learn the lingo.
2. Don’t let them overwhelm you
Speaking to more experienced developers and browsing the web for resources will most certainly overwhelm you at some point — Analysis paralysis alert! — #beenthere #donethat. So, if you tend to over inform yourself, just get started somewhere. In the end, I decided which programming language to choose by deciding which community and which mentor I feel most comfortable with outside University.
3. Find the right Community
Learning programming is not only fun. You’re going to sweat blood. Believe me. And isn’t it nicer to suffer together? Having a bunch of like minded people around me, who are experiencing the same struggles had me being more productive and happier than trying on my own. In order to get fresh input from people outside the University ecosystem, you can join local Meetups, for example.
4. Find the right mentor
Besides approaching mentors at CODE with my noob questions, I am attending Ruby Monstas, a local Ruby on Rails study group in Berlin. I heard from the group by accident and spontaneously decided to join. Especially in the beginning, when I had not the slightest clue on how to write code, this group was REALLY helpful. Thanks to our mentor Sven, for knowing how to create a comfortable and beginner friendly environment and being part of providing us with confidence.
5. Get ready for the “coder’s high”
Last but not least, the point that by now triggers me most — and I wish someone had told me about years ago: the sensation I like to refer to as “the coder’s high”. Diving into a project usually starts with the feeling of being lost and not understanding a thing. Navigating through several layers of complexity and breaking everything a couple of times, can be horribly frustrating. But the moment when your program does what you intended it to, makes you jump through the room like a 5-year-old on a newly purchased trampoline.
Do you have the same or completely different experiences? I am excited to learn about your perspective!
