feedback and suggestions

feedback:

Firstly, the task outline was rather vague. This leading to a number of interpretations, expressed in the sheer number of projects that didn't just vary, but were completely different and had no real correlation with each other. That being said, the projects on display and the winners were all great in their own rights.

Secondly, making hackathons more accessible via virtual hosting was great. But there needs to be more control in who participates and in what. As unlike in person events, members will be most likely not be at a venue and therefore work on projects only when either circumstances permit them, or they just feel like it. this leading to frustrating situations where whole areas of a projects weren't done or couldn't be completed as originally pitched. This issue is further exuberated by the varied levels, experiences, work-stacks, age groups and, willingness to communicate displayed by members.

suggestions:

• Implementing sticker control on who and "shouldn't" participate and also what exactly is required to be submitted with clear themes and objectives.

• Putting into effect a sort of matchmaking system for just beginner level hackathons; allowing the group making process is streamlined to a degree, simulating real word setting where team can't always be hand picked, and allow newbie developers to experience reading/editing/working with other people's codes that may be unfamiliar to themselves.

• Implement some sort site specific chat and that also recognizes group members for a particular hackathon as participants. so potential teammates can have exchanges without having to divulge their contact info and/or feel pressured to join who ever responds, basically gambling with the skill levels and work ethic.

• Another idea is for center groups of new devs around one or more experienced devolves.

Built With

• englsih