I saw a disstrack dropped at a hackathon.

  • 30 sept. 2024
  • 30 sept. 2024
  • 7 min de lecture
  • llms.txt

And on perplexity of hackathon. See this on substack

Cohere Toronto Office

feels and results.

The train station loomed, a grey monolith against the ever-darkening sky. It was half-past seven on a Sunday, and I ran late for the 20:23 Lakeshore West Train back to Hamilton. Quickly grabbing my laptops from the bags I packed for the weekend away, I hop back onto the stream to catch others’ presentations. It wasn’t any ordinary Sunday, but rather the demo night of New Build

Exhaustion clung to me like a second skin after 48 hours of sleep deprivation and intense focus on hacking on a project. Our team had already finished the demo, yet something gnawed at the corner of my mind. A vague unease, shapeless as the fog, settled over me. I couldn’t shake the feeling of displacement that slipped through my fingers, leaving the aftertaste of a half-remembered dream.

I have done a fair shares of hackathons in the past, yet New Build stood apart from most hackathons I have attended. New Build is the definition of “unc cracked tpot club” that build projects during the weekend. It was the distilled essence of Toronto’s raw talents that represents the ever-fast-growing tech scene in Canada. New Build was a multidisciplinary hackathon that combines intensive project development with team formation inspired by NBA Draft1. One major feature that differentiated New from other hackathons is the draft mechanics. We knew who the team captains were. Lo and behold, yours truly was one of them.

Given the crowd of cracked and brilliant minds participating in this event, the weight of self-imposed expectations hung heavy. I felt compelled to match their prowess, not for their sake but to prove something to myself. Yet beneath it all, a voice whispered a simple desire lingering at the back of my mind - to savour the experience and craft something genuine and quaint. I had an idea in mind infused with warmth, a reflection of my inner child, free from the cold glare of corporatism.

I want to play and build something novel!

Yet, on Saturday morning, as soon as the clock struck 08:30, my corporate-wired mind took control, drowning out any remnants of authenticity I have. We immediately got carried away into short-term optimisation2 of the problem statement, min-maxxing for the potential outcomes of the project. Additionally, we were fixated on the name such that we wanted to make it work.

We have fallen into the trap of corporatisation of hackathons.

This mindset got to me, and it showed during the demo. The panel said nothing. No questions, no grilling. Defeat washed over me, heavy as the silence. I felt small, like one of those shuttered storefronts dotting the neighbourhood.

On the train home, I watched the city blur past - all grit, neon, and late-night diners. Something shifted, quiet as a whisper: I know my shit. Damn good, actually. The city kept moving, indifferent. And so would I.

on hacker culture and implications of New Build.

the following is an excerpt from Hacking the Hackathon

A weird thing about startup/hustle culture: We fetishise exhaustion as a badge of honour. We have collectively decided that bags under our eyes are way cooler than a new iPhone. This behaviour very much stems from Silicon Valey’s saviorism attitude. The time-boxed nature of hackathons only serves as microcosms of this zeitgeist and compels participants to push their limits in a 24-36 hours sprint to push out marketable products.

The fundamental issue with this approach is its reductionist nature. These rapid-fire development sessions rarely build upon existing knowledge or work in the field. More often than not, they ignore crucial context surrounding the complex issues they attempt to address, distilling multifaceted problems into a simple web app3. This methodology prioritizes speed and novelty over depth and nuance, potentially leading to superficial innovations that fail to address root causes or consider long-term implications.

“Hackers” are makers compelled to create - not for money or fame, but for the pure joy of bringing something new to life. The congregations of craftsmen eventually led to the formation of hackerspaces such as hackathons – a kind of digital-age speakeasy for the intellectually adventurous. These spaces were initially conceived as the “third space” outside the state’s influence and the capitalist market.

Yet, these spaces often struggle to remain true to their vision without intentional intervention. The commercialisation of hackathons can be seen as an unintended consequence of their underlying financial incentives. Hackathons aren’t cheap to run, so organizers, with the best of intentions, turn to sponsorships to keep the lights on and the Red Bull flowing.

But each logo slapped on a banner chips away at the original ethos.

It’s a classic chicken-and-egg problem. Hackathons need money, but the incentive structure to foot the bill slowly morphs hackathons away from their original purposes. It is tricky, right? How do you keep the spirit of innovation and learning while all these other factors are at play?

flowchart LR
A[sponsors trying to maximize the benefits] --> B[organizers increases size and scope of events]
B --> C[Hackers are incentivized to build]
C --> A

I think organizers should emphasize the ethos of hackathons, eliminate the focus on prizes and short-term projects, and replace it with something better.

Reclaiming the design spaces means to cultivate a culture of play - a space for “for unfettered exploration which gives individuals freedom to explore ideas that might not have clear monetary values.”

A hackathon should be the infrastructure layer so that everyone can play.

implications from New Build.

New Build tackled addresses some problems and challenges pretty well, such as the draft mechanics which introduces some entropy, but fell short in terms of prizes incentives.

_K and I were chatting about how New Build felt like extended New Office Hours, which is a good first step in cultivating spaces for play_

New Build represents what Toronto has to offer, a first step to solve the “human capital flight” (often refers as “brain drain”) in Canada.

Looking ahead, I’d love to see New Build create more space for pure play. Maybe even go full retreat-style, similar to rabbitholeathon.

I have faith in the New Build team. They’ve got good people. And good people are the ultimate moat.

going forward with hackathons.

As for me, I keep saying each hackathon will be my last. The 36-hour coding binges aren’t as appealing as they once were. But I said that last time too, so who knows? There’s something addictive about the energy of a good hackathon4

Here’s the thing about hackathons: they don’t have to choose between being recruiting events and playgrounds for innovation. The best ones are both. But right now, the scales are tipped too far towards recruitment. It’s like optimizing for an acquisition instead of building something people want. The real magic of hackathons happens when you put hackers first. Everything else – the jobs, the networking, the sponsorships – that all follows naturally when you get the core experience right.

to my teammates.

    I'm obsessed with your work.
    I'm so blessed to have a chance to work with you all.

    I'm sorry that I couldn't do more,
              but overall it was a net positive.
    I wouldn't trade anything for it.

    Even though we didn't win, I'm glad that we did work on something together.

    I do hope that we would cross path again in the future.

    regards, aaron.

Footnotes

  1. At a conventional hackathon, one can form teams beforehand with friends or pick one team at the event for the unversed. ↩

  2. Hackathons as Co-optation Ritual: Socializing Workers and Instituionalising Innovation in the “New” Economy by Sharon Zukin and Max Papadantonakis ↩

  3. One team built AI agents to solve public policies. Per the demo, it seemed to recommend building “more police stations” to solve Moss Park’s challenges. However, it is not as simple as just “building more police stations”. The judge was pretty firm on this, but the idea was there. ↩

  4. Honestly, I only do this one because of Tommy, tyfe. ↩

⌘ '
afficher les raccourcis clavier
raccourcis clavier

Liens retour

I saw a disstrack dropped at a hackathon.

And on perplexity of hackathon. See this on substack

Cohere Toronto Office

feels and results.

The train station loomed, a grey monolith against the ever-darkening sky. It was half-past seven on a Sunday, and I ran late for the 20:23 Lakeshore West Train back to Hamilton. Quickly grabbing my laptops from the bags I packed for the weekend away, I hop back onto the stream to catch others’ presentations. It wasn’t any ordinary Sunday, but rather the demo night of New Build

Exhaustion clung to me like a second skin after 48 hours of sleep deprivation and intense focus on hacking on a project. Our team had already finished the demo, yet something gnawed at the corner of my mind. A vague unease, shapeless as the fog, settled over me. I couldn’t shake the feeling of displacement that slipped through my fingers, leaving the aftertaste of a half-remembered dream.

I have done a fair shares of hackathons in the past, yet New Build stood apart from most hackathons I have attended. New Build is the definition of “unc cracked tpot club” that build projects during the weekend. It was the distilled essence of Toronto’s raw talents that represents the ever-fast-growing tech scene in Canada. New Build was a multidisciplinary hackathon that combines intensive project development with team formation inspired by NBA Draft1. One major feature that differentiated New from other hackathons is the draft mechanics. We knew who the team captains were. Lo and behold, yours truly was one of them.

Given the crowd of cracked and brilliant minds participating in this event, the weight of self-imposed expectations hung heavy. I felt compelled to match their prowess, not for their sake but to prove something to myself. Yet beneath it all, a voice whispered a simple desire lingering at the back of my mind - to savour the experience and craft something genuine and quaint. I had an idea in mind infused with warmth, a reflection of my inner child, free from the cold glare of corporatism.

I want to play and build something novel!

Yet, on Saturday morning, as soon as the clock struck 08:30, my corporate-wired mind took control, drowning out any remnants of authenticity I have. We immediately got carried away into short-term optimisation2 of the problem statement, min-maxxing for the potential outcomes of the project. Additionally, we were fixated on the name such that we wanted to make it work.

We have fallen into the trap of corporatisation of hackathons.

This mindset got to me, and it showed during the demo. The panel said nothing. No questions, no grilling. Defeat washed over me, heavy as the silence. I felt small, like one of those shuttered storefronts dotting the neighbourhood.

On the train home, I watched the city blur past - all grit, neon, and late-night diners. Something shifted, quiet as a whisper: I know my shit. Damn good, actually. The city kept moving, indifferent. And so would I.

on hacker culture and implications of New Build.

the following is an excerpt from Hacking the Hackathon

A weird thing about startup/hustle culture: We fetishise exhaustion as a badge of honour. We have collectively decided that bags under our eyes are way cooler than a new iPhone. This behaviour very much stems from Silicon Valey’s saviorism attitude. The time-boxed nature of hackathons only serves as microcosms of this zeitgeist and compels participants to push their limits in a 24-36 hours sprint to push out marketable products.

The fundamental issue with this approach is its reductionist nature. These rapid-fire development sessions rarely build upon existing knowledge or work in the field. More often than not, they ignore crucial context surrounding the complex issues they attempt to address, distilling multifaceted problems into a simple web app3. This methodology prioritizes speed and novelty over depth and nuance, potentially leading to superficial innovations that fail to address root causes or consider long-term implications.

“Hackers” are makers compelled to create - not for money or fame, but for the pure joy of bringing something new to life. The congregations of craftsmen eventually led to the formation of hackerspaces such as hackathons – a kind of digital-age speakeasy for the intellectually adventurous. These spaces were initially conceived as the “third space” outside the state’s influence and the capitalist market.

Yet, these spaces often struggle to remain true to their vision without intentional intervention. The commercialisation of hackathons can be seen as an unintended consequence of their underlying financial incentives. Hackathons aren’t cheap to run, so organizers, with the best of intentions, turn to sponsorships to keep the lights on and the Red Bull flowing.

But each logo slapped on a banner chips away at the original ethos.

It’s a classic chicken-and-egg problem. Hackathons need money, but the incentive structure to foot the bill slowly morphs hackathons away from their original purposes. It is tricky, right? How do you keep the spirit of innovation and learning while all these other factors are at play?

flowchart LR
A[sponsors trying to maximize the benefits] --> B[organizers increases size and scope of events]
B --> C[Hackers are incentivized to build]
C --> A

I think organizers should emphasize the ethos of hackathons, eliminate the focus on prizes and short-term projects, and replace it with something better.

Reclaiming the design spaces means to cultivate a culture of play - a space for “for unfettered exploration which gives individuals freedom to explore ideas that might not have clear monetary values.”

A hackathon should be the infrastructure layer so that everyone can play.

implications from New Build.

New Build tackled addresses some problems and challenges pretty well, such as the draft mechanics which introduces some entropy, but fell short in terms of prizes incentives.

_K and I were chatting about how New Build felt like extended New Office Hours, which is a good first step in cultivating spaces for play_

New Build represents what Toronto has to offer, a first step to solve the “human capital flight” (often refers as “brain drain”) in Canada.

Looking ahead, I’d love to see New Build create more space for pure play. Maybe even go full retreat-style, similar to rabbitholeathon.

I have faith in the New Build team. They’ve got good people. And good people are the ultimate moat.

going forward with hackathons.

As for me, I keep saying each hackathon will be my last. The 36-hour coding binges aren’t as appealing as they once were. But I said that last time too, so who knows? There’s something addictive about the energy of a good hackathon4

Here’s the thing about hackathons: they don’t have to choose between being recruiting events and playgrounds for innovation. The best ones are both. But right now, the scales are tipped too far towards recruitment. It’s like optimizing for an acquisition instead of building something people want. The real magic of hackathons happens when you put hackers first. Everything else – the jobs, the networking, the sponsorships – that all follows naturally when you get the core experience right.

to my teammates.

    I'm obsessed with your work.
    I'm so blessed to have a chance to work with you all.

    I'm sorry that I couldn't do more,
              but overall it was a net positive.
    I wouldn't trade anything for it.

    Even though we didn't win, I'm glad that we did work on something together.

    I do hope that we would cross path again in the future.

    regards, aaron.

Footnotes

  1. At a conventional hackathon, one can form teams beforehand with friends or pick one team at the event for the unversed. ↩

  2. Hackathons as Co-optation Ritual: Socializing Workers and Instituionalising Innovation in the “New” Economy by Sharon Zukin and Max Papadantonakis ↩

  3. One team built AI agents to solve public policies. Per the demo, it seemed to recommend building “more police stations” to solve Moss Park’s challenges. However, it is not as simple as just “building more police stations”. The judge was pretty firm on this, but the idea was there. ↩

  4. Honestly, I only do this one because of Tommy, tyfe. ↩