*Post header illustration by @gelabert.art ๐๐ปโโ๏ธ
Why Hackathons are bad for you
I hate Hackathons ๐. That's a bit ironic because as a developer I have participated in quite a few: a Game Jam for beginners, CodinGame (which I still love ๐ nevertheless), teaming up with a friendโฆ but there was always something about the concept that didn't agree with me ๐ค.
If you think about it, it has nothing to do with the way teams ๐ช construct a modern software product in most companies. For example, in such a short time, you cannot implement a real Agile Methodology for your project ๐งฎ.
I think Hackathons generally proclaim a big myth in our global dev community: "a good programmer should just ignore their need to rest and just code all night, drinking enormous amounts of coffee โ, in order to be able to finish a product worthy of the public attention ๐ค๐ผ". I believe this is more intense in the game development industry ๐ญ, where indies and employees are usually "crunching" to meet impossible deadlines ๐ .
Why is crunch bad?
It excludes people with healthy sleep routines ๐ช from tech jobs
It even excludes people with children ๐ถ๐ฟ or old people ๐ต๐ป at their care who doesn't have so much free time โณ
A big portion of those excluded people are women and people older than 40 years, those who traditionally take care of other family members ๐ฉโ๐งโ๐ฆ. Those two groups are still minorities in our software industry, while for example in the case of women ๐ฉ๐ฝ, they actually are half of the global population. I think we'll agree that men ๐จ๐ป should be included in this "caring responsibility" but I don't think diversity will be accomplished meanwhile companies in Software Development ๐ญ keep expecting people to work overtime every week and code all weekend in a Hackathon "to have fun" ๐ฅฑ.
- Crunch damages the physical and mental health of the ones that experience it ๐ข. Mental health is one of the bigger health problems on the rise in modern societies: and our industrial-age-old paradigms ๐ญ about how to produce are just making it worse.
But Hackathonsโฆ!
I understand the main counterpoint: Hackathons allow people to focus on a single task and motivates them to do things they normally would be too distracted to even try. But, is that really true? ๐ต๏ธโโ๏ธ
I have known a lot of many developers in my career. And mostly all of them have told me a story about having an impossible-to-fix bug ๐ or a feature too hard to design. But, after a good night's sleep or maybe just a peaceful walk, they had a breakthrough idea and fixed their issue in no time at all ๐ช.
They actually saved time having proper rest. They just needed to escape from the Cognitive Tunneling trap ๐ณ.
This kind of creativity ๐ญ that the mind can access when wandering off or by organizing thoughts and memories while sleeping is just not present in a Hackathon. There's too much rush and stress.
That pressure is cool when your goal is clear and your task monotonous, but a lot of Hackathon's themes are only decided inside the time limitation of 24-48 hours โฐ...
There's a good documentary ๐บ named Take Your Pills about how our modern society is obsessed with being productive at all times.
Is there a way to design better Hackathons?
Yes, indeed. There's a very good example in the "Unity" and "Games for Change" Cross-Cultural Impact Jam. They decided to make the Jam one week long ๐, so students from different parts of the world could team up and participate while keeping up with their studies ๐จ๐ฟโ๐.
Closing time
So, yeah, I believe that's all I had to say about Hackathons ๐ค. I cannot assure you that I myself won't be participating in any new Hackathon someday, but I'm sure in the future we will all out-grow this kind of practice as a global community, making Software Development a more inclusive and healthy environment ๐ .
Have pros or cons to add about Hackathons? Show them to me in the comments ๐