[antomeie]

From my experience, developers often feel pressured to achieve a lot of work in a very short period of time, possibly using technology that they are not so familiar with, in order to build a “Proof of Concept” of something. I have experienced this myself several times. The rest of the company are having fun being creative and “brainstorming” stuff, making presentations, while developers are stressed out in order to finish coding something before end-of-day presentation.

My suggestion is that developers know in advance what they will work on so that they can make sure that the scope is within reason. It also allows them to get started right away in the morning, without needing to wait around for a project to surface. Also, don’t force someone to come up with an idea themselves.

[tagolli]

That makes sense. I was planning to write up some ideas that people can just take if they want. Also, seems like a good idea to have people pick what they're working on before the actual hackathon starts.

Do you have any example of what non-technical people worked on? For example, we have QA members and I'd love to include them, but I don't have as many ideas as I do for developers.