Eric Belongea

My experiences are from the outdoor industry; leading multi-pitch rock climbing trips, walks on glaciers, snowy summits, and celebrating the people. Are you wondering, “how does this relate to programming and code”? Well good news, I’ll tell you.

In the planning phase of outdoor adventures, we plan out our camps and routes, like sprints, to make sure that we stay on track, and think about the possible roadblocks on the journey. Next, we ask questions about the terrain, trip duration, weather forecast, experience of the team, possible roadblocks, and what is really necessary (MVP). Now it’s time for the fun part, we put on our shoes and start to do the dang thing. As we move through the mountains we talk, check-in, walk quietly, and enjoy the ‘co-workers’ that we’re with. Corny as it is to say, this is the most important part, the people that we meet and spend time with along the way. This is the company culture and our co-workers; the people that make our jobs so great.

As we get further into the mountainous unknown we are monitoring our surroundings for potential risk. As a guide, we take people into the wilderness and the potential for risk is always there. Clients/Customers/People look for a fun and safe experience when going on an adventure, just as they do on the web. A ‘user’ wants their data to be kept safe and to have an enjoyable experience. That’s why they keep coming back and recommending said services that the app provides! In the mountains dangers and potential roadblocks come up. How do we solve this? The team gets together and talks about potential outcomes and how decisions will affect us down the line. This is problem solving in physical form, and the best examples come from rock climbing.

Using nothing but your hands and feet how do I move my hand from one hold to another inching my way up the rock. To climb successfully one must fail. Failure is 90% of climbing, and that’s where we learn. Not by trying the same thing over and over, but making small adjustments that lead to success, or throwing the kitchen sink out the window and coming at the problem from a new angle. Receiving feedback from friends, watching how others do it, youtube videos, and talking with others helps inform and guide for best practices. This is community mentorship. Being able to ask for help when you need it, and having the humility to know when you’re wrong and there’s a better solution to the problem.

TLDR?

Enthusiastic and results-driven backend developer with a background of 5 years in outdoor experiential education and 2 years management, I am a blend of technical aptitude and exceptional communication skills. Backed by over 7+ years of leadership experience, I am looking for an inclusive collaborative environment with the opportunity to contribute and grow individually and with a team.