Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My Failure Resume

dare.fail

Post reply on HN
Print view View original

61–70 of 132 posts

Re: My Failure Resume

#61

Post by cornholio »

hyperpape wrote: post #50

One of the items on this website contains very personal information about an another person you dealt with. I don't want to assume this is violation of privacy. Perhaps you're on terms with them and they're public about it. But are they? Because if they're not, I believe you should remove it. (I'm speaking vaguely, because I don't want to repeat that bit of information here and make it more immortal).

If somebody tried to screw you then backed out of it and you have proof, seems fair game to post it online, complete with the scammer's real name and affiliation. It might not be tactically prudent since that person might sue you in retaliation, by you are squarely within your rights to do it if you want, no "violation of privacy" here.

Re: My Failure Resume

#62

Post by xigency »

I like this. It’s a bit cheeky but the point still lands. Even if you have the greatest startup idea, there are myriad ways it can fail, many of which are totally outside a founder’s control.

Fail early, fail often still seems to be the best wisdom.

Re: My Failure Resume

#63

Post by dennis_jeeves1 »

jimhi wrote: post #59
notmindthegap wrote: post #58

What drives you? Is it money, general problem-solving? I must be wired differently because I cannot understand how someone can try so many things in so many different industries without being driven by a mission beyond financial wealth. I have friends who are like this and I don’t get it.

If you couldn't tell, I literally couldn't get a job...

That tells me more about our industry (and the low life, shitty developers who interview you) than you.

BTW, thanks for posting and opening up.

Re: My Failure Resume

#65

Post by Joel_Mckay »

"They ghosted me"

This is unfortunately modern culture, and most seem unconcerned how rude they are to strangers. Very foolish policy unless you already have over a Billion market cap, and can attract a steady stream of junior staff more willing to take flippant abuse.

Rule #23: Don't compete to be at the bottom, as you just might actually win.

This also means respecting the content medium, and knowing when to bail. =)

Re: My Failure Resume

#66

Post by cube00 »

overthrow wrote: post #57
ipaddr wrote: post #31

"CTO at Loyalsnap (02/23/2017): The CEO rejected me then used the code I wrote in the interview in production. When I pointed this out and said an estimate of the hours I worked on that if he wanted to use it, he told me I would have to sue him to get it. 20 minutes later he venmo’d me the amount and said don’t sue him." Happens more often then you think. Get 200 approaches on something that team can't get right. Use…

I can't wrap my head around why companies do this. If you find a competent programmer whose work is good enough to use, wouldn't your team be better off if you hire them full-time? That seems more efficient than interviewing 200 people every time you need some code written.

If the culture is that rotten that this behavior is accepted (as it requires multiple people in the hiring process to be complicit) I doubt anyone would want to stay for very long if they were hired.

Re: My Failure Resume

#67

Post by sebastianconcpt »

overthrow wrote: post #57
ipaddr wrote: post #31

"CTO at Loyalsnap (02/23/2017): The CEO rejected me then used the code I wrote in the interview in production. When I pointed this out and said an estimate of the hours I worked on that if he wanted to use it, he told me I would have to sue him to get it. 20 minutes later he venmo’d me the amount and said don’t sue him." Happens more often then you think. Get 200 approaches on something that team can't get right. Use…

I can't wrap my head around why companies do this. If you find a competent programmer whose work is good enough to use, wouldn't your team be better off if you hire them full-time? That seems more efficient than interviewing 200 people every time you need some code written.

Desperate strategy to steal developer code done by people that is as immoral as ignorant on how tech isn't reusable or modularly scalable like they imagine and how obviously bad it will all invariably end but they are "just giving it a try"?

Re: My Failure Resume

#69

Post by silvertaza »

I love the spirit!

Practically speaking, having a backlog of vast amounts of similar data to you, the true way to get out of the loop is to try something different. To do the things that wouldn't fit as a data point in that list format.

Post reply on HN