Hackathons don't win you customers

Oddly I rarely talk about Developer Relations, but I feel like changing that today.

I feel really uncomfortable when I hear people suggest Hackathons are a part of building a sustainable, scalable developer ecosystem.

They are not.

I have run hackathons. Some better than others. I have learnt a lot about them.

Businesses and Platform creators:

Hackathons can be a thing of beauty, they can produce completely unexpected demos, but that is not your goal. You should be using it as a learning exercise for you, your team and fixing your product. It is the developer version of a beta test, not a marketing tool.

Learn from the developers using your platform. Ask yourselves the following questions:

You can answer all these questions at a Hackathon. That is what you should be concentrating on.

One little point, rather than just rewarding teams who produce a lot, reward filing bugs and issues on all parts of your product, the apis, the documentation, the demos and the value as well.

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)