I'm a programmer who likes games, and wants to make games for a living. At the same time, there are some really cool non-game things I want to work on -- especially if they use C or C++.
While I really do enjoy hackathons, I think this could use some specification. For your first hackathon, I'd recommend something short and fast and low-stakes -- 24 hours straight of coding, laptops closed strictly then, try to get something done. The longer, more productive hackathons are really cool, but it takes some time to build the skills required to develop quickly on a team, and jumping straight into a two-weeker can be really hard.
That said, I totally agree. Everyone should do a hackathon at least once. It's an experience like no other, and a great way to improve your coding.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
While I really do enjoy hackathons, I think this could use some specification. For your first hackathon, I'd recommend something short and fast and low-stakes -- 24 hours straight of coding, laptops closed strictly then, try to get something done. The longer, more productive hackathons are really cool, but it takes some time to build the skills required to develop quickly on a team, and jumping straight into a two-weeker can be really hard.
That said, I totally agree. Everyone should do a hackathon at least once. It's an experience like no other, and a great way to improve your coding.