Mapping your DevRel: How recurring hackathons drive continuous growth
I recently finished a month-long road trip in my new-to-me 1997 Ford Econoline. Other than getting pulled over for a broken brake light exactly 42 miles from my final destination, the trip was a shining success and I enjoyed getting to see so much of the United States.
As I traveled to different places, staying for various lengths of time, I became more comfortable navigating without the use of maps — relying more so on the routes I had become accustomed to and the knowledge I had gained about my surroundings along the way.
Some might claim it’s a stretch to say DevRel and roadtrips have a lot in common, but I wouldn’t be too sure! Just as traveling back and forth on a route provides familiarity, engaging with your developer community continually over time through cadenced hackathons improves both the developer experience and the outcomes brought on from building.
Hackathon One: Learning the wei
Let’s say you just moved houses, and you are looking for a grocery store nearby. For that first shopping trip, you might need to (and I would definitely need to) use a maps app to help get you there. The goal is simply getting there.
During the first hackathon, a builder may have very limited knowledge — whether it’s the resources provided by the organizer or information learned prior to the start of the project. With this, they build, they submit, and for the lucky ones, they win.
Hackathon Two: Feeling comfortable
As you become more familiar with your new home, going to the store becomes a bit easier. For me, I might still pull up directions but may not actually look down at them. You may even know a few neighbors at this time that can help with different routes.
The same can be said for the second hackathon, workshop, or event: there’s a sense of comfort in what needs to be done and the people who can help you get there. Documentation is still there for assistance, and there are other builders involved in the building process. There’s still some hesitancy, but that is partnered with a higher level of confidence that wasn’t there previously.
Hackathon Three: Paving new paths
By now, you know the way to the store and probably have other places you usually visit. You’re more comfortable driving in your neighborhood and likely have a general feel for your community — though there’s so much more to learn!
Likewise, the more a builder participates in an ecosystem, the more comfortable they feel building within it. They know more about the resources they need for the projects that lie ahead, along with issues they might face (and how to face them). They are ready to be part of a community more than simply contributing to it, and they have the context in order to do so.
Conclusion
Much like the journey of becoming familiar with a new neighborhood, the progression through multiple hackathons offers a parallel experience of growth and comfort within a developer community. Just as the first trip to the grocery store might require a maps app, the initial hackathon presents a learning curve where builders navigate with limited knowledge but determination. As familiarity grows, akin to knowing the routes in a neighborhood, subsequent hackathons provide a sense of ease and confidence. Over time, builders are not just contributors but integral members of the community. So, whether it’s exploring a new city or diving into hackathons, the journey leads to a deeper understanding, comfort, and readiness to build upon what has been learned along the way.
Ready to chat?
Interested in discussing how your organization can stay engaged with a growing builder community? Contact us today to learn more about our modular devrel offerings, including dedicated support from the buidlbox team to manage and assist with full-cycle hackathon strategy, engagement, and marketing campaigns.
