10 months ago
The last Codegeist hackathon had some amazing submissions. Dmitry Pashkevich and team took home the prize for Best Software Team App in Atlassian Codegeist 2017 for their project, Class Diagrams for Bitbucket, and wanted to pass along these tips to help you with your Codegeist 2020 project:
- Identify a real need. This sounds obvious, but technology just for the sake of technology can only go so far, especially in a hackathon context. If you struggle to come up with ideas, try surfing through Atlassian's community forums - there are plenty of feature requests upvoted by hundreds or even thousands of their customers
- Explore the latest tools and APIs. While building Class Diagrams for BitBucket, I was able to take advantage of the new API Proxy module that sped up my development significantly. You have limited time in a hackathon, so you want to take advantage of every new platform feature there is, even if it's experimental. I recently saw that Atlassian launched a new platform, Forge, to make creating apps for their ecosystem even easier. Definitely planning on checking it out!
- Move fast and focus on what's most valuable. A hackathon is a testing ground for a new idea. What you're doing is you're putting together a prototype you can demo on a tight timeline. Be a good programmer and write code that you won't get tangled in, but also cut corners wherever reasonable. Don't be afraid of novel approaches and experimental tools/APIs. A hackathon is about hacking - your goal is to demonstrate value and gauge interest, you can polish your solution later if it gets traction
- Get help / Connect with the community. I was lucky to be attending Atlassian Connect Week (later renamed to App Week) when working on Class Diagrams. It was an in-person event that got me direct access to Atlassian developers, product managers and designers whom I could tap for expert help and feedback. I'm guessing there won't be an in-person event this year, but the Slack Channel is a great alternative to connect with their resources and other participants.
Do you have a tip you’d like to share with your fellow devs? Be sure to share it in the Hackathon Slack Channel, we know they’ll appreciate it!
If you have any questions about the hackathon, please post on the discussion forum.