hackathons

This isn't limited to hackathons, and to be fair the title is fairly click-baity.

And college hackathons are the ones the dashboard is about.

The problems the author describes aren't limited to just hackathons.

Interestingly enough though, college hackathons are the only hackathons I've seen actually reward implementation over concept and the actual technical work done by teams over future potential.

We looked at & ranked project tags from a sample of 13,281 student hackers who participated in 160 student hackathons and submitted 9,898 projects, either in hackathons or on their Devpost portfolios.

But to me, a big part of hackathons is learning something new, and MongoDB is apparently just not worth learning.

Essentially you are bringing the benefit of hackathons & sprints to internal projects, using the structure of a conference for framing.

I can see it because trolls are on the rise in general and might start pulling crap with hackathons.

We hold a yearly developer retreat, as well as regular company-wide hackathons.

I used to attend the weekly brewpup hackathons she organized, and which are still going strong.

Very interesting to see how much more popular Android is for hackathons.

As someone who's spent a lot of time with both developer relations and Hackathons in general, here are my top 5 insights from this analysis.

To be fair, the title was a (not-so-subtle) "twist" in that you thought it was going to tell you not to go to hackathons, but it flipped it by saying "Don't attend a hackathon...

It might be a very naive idea but I've got the feeling that setups like hackathons (where all kinds of interested people can participate, people people, idea people, technically inclined people, etc) can be more beneficial to learning than a traditional "school" like environment but maybe that's just me (and my inherent learning style).

I also believe that is actually the main objective of most Hackathons.