Loading question...

First Ever Krackathon - Reflections & Feedback - KrackedDevs Community | Kracked Devs

First Ever Krackathon - Reflections & Feedback

Asked 17 days agoViewed 118 times

1 votes

Hi everyone!

First of all, I want to extend a massive thank you to every single one of you who participated in our first ever Krackathon. We saw 38 submissions on our very first try and that is far beyond what we imagined, and the quality of work has been truly inspiring.

I also want to personally apologize for any technical hurdles or "buggy" moments you encountered during the submission process. While we are technically in beta, I take full ownership for not having every corner of the system battle-tested for an event of this scale. Thank you for your patience and for sticking with us through the growing pains.

As the developer for KrackedDevs.com, my goal is to build the most robust and mature platform possible for our community. To do that, I need your "unfiltered" input. Whether it's a critique of the UI, a recommendation for the next hackathon, or a specific bug you found, please let me know in the comments below.

Your feedback is the fuel that will help KD level up.

Best regards,

Jinbei

hackathon

feedback

asked 17 days agojinbei

5 Answers

2 votes

Great work team - The Kracked Team can learn a lot from this and make the next ones better.

Let's make some stats for this Krackathon - Perhaps design a poster congratulating participiants etc

Maybe as pizofreude suggested ;

Participant Metrics

Total participants vs completed submissions
Geographic distribution of participants
Retention rate (returning participants)
Post-event survey response rate and satisfaction scores

Technical Metrics

Popular stacks and programming languages used
Submission categories breakdown
Average lines of code per submission
Completion rate (projects submitted vs started)

Engagement Metrics

Social media engagement (mentions, shares, hashtag reach)
Number of projects that continued development post-hackathon

Judging & Impact Metrics (if not under NDA)

Judging statistics and criteria breakdowns
Winner selection patterns
Award distribution

answered 16 days agoenonforetsam

pizofreude•16 days ago

That would be ohsem. On the flipside, as mentioned by @sky about doing different category for different dev discipline, here's my observations from popular hackathon platform like Devpost i.e. up to 6 criteria with equal weightage, judging groups by track/discipline/category-based prizes, multiday for online hackathon, clear guidelines for judging metrics. See their general recommendation here: https://info.devpost.com/blog/devpost-for-teams-features

pizofreude•16 days ago

I personally love their multiday online hackathon, since this will level the ground and fair for all participants regardless of discipline. Maybe we can try it next time? Like briefing+launch on thursday or friday evening and cut-off on Sunday. This gives us time to plan project that solves real problem and not just another zombie app just for the sake of it.

2 votes

I think the event is just fine ,as there is some others organiser do so as well especially for time allocation, but separate category should be existed as both games dev and hackathons ideas dev is kinda not same, comparison between them may seems to be a bit conflict for different people.Also, a special thanks again to the team ,which conduct this wonderful event, the theme set is quite interesting .I am enjoying developing my ideas through the event and honored to share with others developers as well.Haha, best of luck to me for this krackzzzzz.

answered 17 days agoSky

jinbei•16 days ago

Hi Sky, Thanks for the kind words! Really glad you enjoyed the theme and had a good time building out your ideas, and that’s exactly what we wanted to see. You make a great point about separating categories. Game dev and traditional hackathon apps are definitely different beasts, and we’ll look into splitting them up next time to make judging a bit fairer for everyone. Best of luck with the results! Krackzzzzz indeed! ⚡️ Cheers, Jinbei

4kmal•16 days ago

Yup I agree, Making a web application and a video game are two different categories👨🏻‍💻 Thanks for the feedback @sky

enonforetsam•16 days ago

Thanks for the feedback Sky, Agreed, next Hackathon we will definitely separate categories out! We just hope everyone enjoyed building, and people now have an extra piece of software to add to their portfolio! Thanks for joining and see you in the next one. We promise to do a better job :D

Your Answer

2 votes

First of all, thanks and congrats to all KD admin for organizing this hackathon. Awesome localization effort that gives future Malaysian winners of Devpost Big Bucks hackathon. Some post-mortem from me as a participant:

Time allocation: Under normal hackathons, the cut-off time was usually very strict (at most a 1-hour extension) to provide fair play for all participants. Since the work quality of 10h vs 24h can't be fairly compared, especially the implemented features, which are a key metric. This is understandable IRL since at work, getting a due date adjustment is only viable if certain conditions are met, i.e., the majority of stakeholders are projecting to miss the appointed milestone.
Post-event stats: This is just my pet peeve as a BI & Analytics Engineer. On top of seeing the submitted projects in Showcase module, it would be an added advantage to post the stats, as this is common best practice for hackathon growth. Trust me, people love vanity metrics. This would be an encouragement for them to participate next time and bring their friends for the ride along. I love seeing these: total participants vs completed submissions, geographic distribution of participants, retention rate, popular stacks and programming languages used, submission categories breakdown, avg lines of code per submission, completion rate (projects submitted vs started), social media engagements (mentions, shares, hashtag reach etc pp.), post event survey response rate and satisfaction scores, no. of projects that continued development post-hackathon. Oh yeah, if not NDA, then the impact metrics like judging stats.

P/s: kindly don't ask me to be cut-off jury. I'm too soft-hearted, so will 99.99% allow unlimited extension.

answered 17 days agopizofreude

4kmal•17 days ago

yup Agreed, the more stats and analytics that we can see the better 👨🏻‍💻. Gotta ask what do you mean by Retention Rate? is it like how long a user views your submitted project page?

jinbei•16 days ago

Hi pizofreude, Huge thanks for the congrats and the killer feedback. Since this was our first Krackathon, these insights are gold. We’re definitely taking notes on tightening the deadline next time to keep things fair—finding that balance is tricky but necessary. Also, love the idea of sharing post-event stats, that would be interesting to implement. We will try to implement it next time. Cheers, Jinbei

pizofreude•16 days ago

re: @4kmal, retention rate of every possible metrics. Data is the 9th wonder of the world. We can track retention rate of recurring participants vs new participants, DAU/MAU to measure how many returning to the platform after the event, and etc pp. Oh, I hope krackeddevs will hire me on freelance basis to tacke the bi & analytics engineering for all KD stuffs. re: @Jinbei, I got lot more to say, just holding back to not overwhelm organizers considering this is the 1st cohort. Already good!

jinbei•15 days ago

Thanks a lot for being considerate, @pizofreude!