2 ms·
My experience with Hackathons has often been that in the days immediately following the hackathon you have to invest a LOT of time to clean up the mess. Everyt
by LogicX 14y ago
My experience with Hackathons has often been that in the days immediately following the hackathon you have to invest a LOT of time to clean up the mess.
Everything that was done post-haste, not documented, not version controlled, so on and so on.
To make the project usable, manageable going forward, requires plenty of effort to now redo or improve upon the messy state left from the hackathon.
Certainly I can agree that there are some gains made from the hackathon environment that are lost working in a normal business environment and pace (lets say iterating faster on product while its in infant stages). However, I'm not sure that many of the principles apply after that, when having to continue maintaining and collaborating on a more mature product.
- pzaniewicz 14y agoThe hard truth is that 9 of 10 applications (commercial or start-ups) are just mistakes. So whats the point of delivering well documented and beautiful designed app that nobody use? That is why i think that hackatons in order to deliver good enough product and test your hypotesis does make sense. If it`s a market fit, then i agree - lets clean up the mess and develop it in normal way
- LogicX 14y agoCertainly agree on high failure rate. Unfortunately for most, that is not achieved in the span of a hackathon, or using the style of hackathon development, which cannot be sustained. It often takes months to reach product-market fit... and if you have a team of people working on an app together, and you are having customers sign up and use your app, you need it to look beautiful, and your ability to collaborate with colleagues over those months needs to be functional.