> Six days before the interview, my laptop crashed and we lost our entire demo.
Not exactly a ringing endorsement of the qualities of the poster as a software engineer. You'd think that for a project that might change the rest of your life, you'd spend some time reading up about back ups or source control.
This comment adds nothing to the discussion, because absolutely no one reading HN is unaware that that was preventable, and serves no purpose other than to mock someone building things. That should be anathema here.
> Everyone thinks that backups aren't necessary until something happens to them.
On the contrary, everybody knows backups are necessary, the problem is bothering to actually do it regularly, especially on a high-intensity time of pre-launch. Personally I forgot to eat at times when working on our Kickstarter campaign video...
Agreed! I'm surprised of the number of comments of this ilk, as if it was the main point (or even a point) of this story.
If the OP had walked onto dog poo just before entering YC's offices and had brought an awful smell to the interview (which would belong to the same category of small catastrophes), would people point out that you really should watch your steps??
Besides, isn't it possible (not necessary, just possible) that successful entrepreneurs are the kind of people who don't have time to backup their stuff, make their bed in the morning, store 10 days of food in the fridge and buy stuff in pairs in case one breaks?
I guess that comment was cynical, but just to be sure: http://blog.backblaze.com/2013/11/12/how-long-do-disk-drives.... Especially in the beginning there is a higher failure rate for disk drives. So it is actually the opposite: backups should be one of the first things to arrange for new machines.
Not exactly a ringing endorsement of the qualities of the poster as a software engineer. You'd think that for a project that might change the rest of your life, you'd spend some time reading up about back ups or source control.