What kind of people typically join Hackership? It's a question we get a lot. The answer is a simple one: all kinds of people.
Some of our learners are very experienced developers, others are just starting out. Some studied computer science, others studied history, or physics, or art. And yet another group skipped university altogether. We have welcomed people from many different countries and people belonging to many different age groups. So yeah, we really mean it when we say 'all kinds of people'.
Yet after three batches we see some commonalities. Chief among them: designers and artists looking to improve their coding skills.
Stephen Koller is one of them – sort of. Stephen is the rare hybrid: not a coding designer, or a designing coder, but a developer as well as a designer. In this short interview we explore his reasons for joining Hackership and why he thinks designers should learn how to code.
Who is Stephen Koller?
I'm a software developer and music aficionado from the Midwest of the USA: Ann Arbor, Michigan, 45 minutes away from Detroit. I grew up with digital creativity in my veins: my first programming class was at age 13, where I built a space shooter in Python.
I dabbled in digital music, art, and programming through my time at university, studying fine arts. After school, I became a front-end programmer, merging my artistic sensitivity with my skills as a developer.
Why did you decide to join Hackership?
Hackership offered a unique opportunity: learn new skills, while living in a foreign country and having the support of other talented programmers around me. I was intrigued and excited about the idea of learning in a semistructured, but ultimately self-driven, environment.
What did you work on during Hackership?
I also had the pleasure of participating in Music Hack Day Berlin, where my team won the jury prize for a real-time interactive music visualization in collaboration with the electronic artist Phon.o. The program reacted both to the pulse of the music played during a DJ set and the motion of smart phones during the performance, using Websockets and the HTML5 accelerometer API.
Why not just stick to one thing, code OR design?
I think designers should learn to code (and developers should learn to design) so that the communication between the two is much more fluid. I believe the end result is a product which gets to market faster and has a high potential to delight the end user. For myself, I wanted to learn to quickly prototype ideas, with frameworks like AngularJS, so that I can get a sense of how my idea would really work, with a minimum of time spent building a full-fledged product.
What's life like post Hackership?
Currently, I am an enterprise software consultant helping large companies improve their software and methodologies, with a special emphasis on the UX of enterprise applications. I'm also considering moving into the mobile app market soon.
Hackership was an absolute blast and I highly recommend it for anyone, especially if you are looking to learn new skills, or feel stagnant in your current position.
Stephen Koller was a learner during the Berlin Summer Batch of 2014. To see what he's been working on, please check out his github!