I won a month-long hackathon in 3 hours(onmattersconcerningmyexistence.com)
onmattersconcerningmyexistence.com
I won a month-long hackathon in 3 hours
https://www.onmattersconcerningmyexistence.com/p/how-i-won-a-month-long-hackathon
19 comments
This has to be a record for the most number of times someone plugged their startup in an article supposedly having nothing to do with their startup.
“Organic content” baby.
Joking cynicism aside, I think it was well done. I read the post to the end even though they gave the answer up front (good practice despite what’s”growth hackers” will tell you) and their mentions of the company seem authentic (i.e. they don’t tell you what they do, just that it was his main focus and made some legitimizing progress).
Joking cynicism aside, I think it was well done. I read the post to the end even though they gave the answer up front (good practice despite what’s”growth hackers” will tell you) and their mentions of the company seem authentic (i.e. they don’t tell you what they do, just that it was his main focus and made some legitimizing progress).
The takeaway being that Google should publicize its events more if they want more than a single digit number of submissions.
Ultimately, these events are entered either for the money or for the fame - the submitter finding a way to get a bit of both. Since Google didn't give out a large amount, they could rely mainly on fame, and that requires more than a post in a single reddit community (and a post removed by the moderators!).
Ultimately, these events are entered either for the money or for the fame - the submitter finding a way to get a bit of both. Since Google didn't give out a large amount, they could rely mainly on fame, and that requires more than a post in a single reddit community (and a post removed by the moderators!).
It was a fun read, thank you!
Your submission is the real-world example of "work smart, not hard"
Your submission is the real-world example of "work smart, not hard"
Thanks, glad to hear you enjoyed it!
Umm, yeah. But if I found this while doing background research on a job candidate I'd have to think twice about if this guy was really someone I wanted on my team... be careful what you brag about cheating on, lest you let people see the real you.
Or it shows that he's open and honest. And that's definitely someone I would want on my team.
The use of cheating here is pretty tongue-in-cheek. I'd say the thought process exhibited in this is the exact kind of person you want to hire. Somebody who keeps their old work organized in such a way they can leverage it rather than start from scratch over and over again is hugely useful.
What cheating?
All he did was a really low-effort submission.
All he did was a really low-effort submission.
Low effort submissions are what wasted most of my time code reviewing at one job...
Not sure I would consider this cheating. At most if I was reviewing a resume from the person I'd think "coder reused old code, built on it to fulfill a new set of requirement. okay"
He called it cheating, not me.
I'd call it more taking advantage of the situation (he did too), which I like in my sales colleagues, and less in my engineering colleagues.
I'd hire him for sales.
I'd call it more taking advantage of the situation (he did too), which I like in my sales colleagues, and less in my engineering colleagues.
I'd hire him for sales.
Talk about not wanting to hire someone: this person used the word playfully, not in the literal negative doing-something-wrong sense: but you're actually saying you ::like:: cheating in some of your staff as long as it makes you money
I wouldn't want that comment associated with my name.
Not to mention the endless amount of false expectations and customer complaints that causes, wasting engineers or devs & post-sales support staff endless hours dealing with the fallout. And nothing good happens to a company's culture when cheating in one area is fully embraced.
I wouldn't want that comment associated with my name.
Not to mention the endless amount of false expectations and customer complaints that causes, wasting engineers or devs & post-sales support staff endless hours dealing with the fallout. And nothing good happens to a company's culture when cheating in one area is fully embraced.
Keep that in mind when asking developers to estimate how long it will take.
Could be next month, could be tomorrow.
Could be next month, could be tomorrow.
Hah, yeah. I've certainly had to explain why a seemingly simple request would take a while. And I have also looked like a genius more than once when I whipped out something I'd developed years ago that took me a month, tweaked some parameters and other simple changes, and had it a few hours later.
Unfortunately, the more of the later you have, the more people seem to get frustrated at the former.
Unfortunately, the more of the later you have, the more people seem to get frustrated at the former.
Ok i was gonna hate the author for stealing money from people thata need it but buzzword bingo is a really good idea.
It seems there is nothing in the rules that the submission must be your work. Since the Buzzword Bingo was under an Open Source license, anyone could simply submit it...
Keep it in mind for next hackathons!
Keep it in mind for next hackathons!
TL;DR: Yet another hackathon is won by someone submitting a project based on prior work. This (in my opinion) is equivalent to cheating.
Impact over effort in spades. Congrats!