3 ms·
This is horrible: among other head-scratchers, author advocates "saving time" by blatantly cheating. A "clever (sic) rehearsed demo" that "covers up" the fact t
by lostmypassword 12y ago
This is horrible: among other head-scratchers, author advocates "saving time" by blatantly cheating. A "clever (sic) rehearsed demo" that "covers up" the fact that you didn't actually write the application code you say you wrote isn't saving time, it's cheating. The point of a hackathon demo is to show how much progress you made towards an idea in a given amount of time, not to put on a smoke & mirrors show.
- bbody 12y agoIn defence of the author, I think he means take some short cuts if time is short to show your business logic. It makes more sense in pitch-a-thons where the pitch is central and the demo is usually only given a short window of time.
- lostmypassword 12y agoI'm going to continue operating under the assumption that Author intended his advice to apply to traditional hackathons, since that's the language he used. > I think he means take some short cuts if time is short to show your business logic. Even if that is the case, covering up the fact that you took a shortcut is still cheating. It's fine if, during your demo, you say something like "this is a mockup modeling the backend, we plan to implement xyz functionality using abc stack". At a hackathon, people get that, and if you show good effort and use of time otherwise you're not going to be dinged on that alone. But faking it to look as if you did more work than you actually did isn't right, and isn't fair to the other hackers.