Hacking without Coding
Do you code? Well then this article is not for you, I actually highly encourage you to find a better use of your time elsewhere.
So to the remainder of you; If you have ever looked into attending a Hack A Thon you will quickly see within the FAQ you don’t need to be able to code.
“We encourage people without a coding background to come learn some new skills in workshops, and we encourage those who have been coding since they first met a computer to share their skills. As long as you are interested, willing to contribute ideas, and want to get your hands dirty building a new product you’re set.” — ArchHacks 2016
At Hacks there is are a tremendous number of people with the ability to code. However, the intent is not to code a new product but to create a product in order to create a solution. Your solution will most likely take the form of hardware or software, however, the components which make up that solution often are not made of code.
As an individual you bring your own experiences and observations with technology. This is not something that you should discount. As people create new technologies its often the views of individuals from outside the production room that can give the best input. Hence, by not having the background to code you become an integral part of the team. This does leave you with the extra responsibility to push your team to explain what they are working on. As they break down their ideas into layman’s terms you can reimagine their solution in new environments that they had never expected.
You can:
- Ideate: Design, Sketch and Find Interesting Ways to Pitch the Solution
- Conduct Research: Research competitors, find flaws in current products, segment markets, guerilla test the product
- As a Team Member: Keep the team on track, provide extra opinions, manage ideas
If you are willing to adapt you can become an invaluable resource to your team.
Before you become over confident, I’ll remind you of the most intimidating moment; Walking into a bustling room and everyone is throwing around technical terms you have never heard before. It’s most likely late at night and you are wondering why you didn’t have an extra coffee before you left home. You have ideas, you’re excited but most of all you’re nervous because the time has arrived for you to find yourself a team.
Think about what you are interested in and find a team that aligns with your goals of the event. Not every team needs someone with your skill set, but this happens to everyone regardless of your backgroun. Believe in yourself and your expertise; And as stated in the ArchHacks FAQ: Be interested. Be willing to contribute ideas. Be willing to get your hands dirty.
It is all about problem solving not about coding.
