Hacker News new | ask | show | jobs
by jpdoctor 4738 days ago
> I’m scared.

Congratulations: You're normal. Look at it this way: You are commanding on a battlefield, there are a helluva lot of guys about to die. If you freeze up, they all die.

So make some fucking decisions, save as many as you can. Throw some into the line of fire for the sake of the others. It's what battlefield commanders do. The gods have chosen you for this role, rise up and do your best. You will make some bad calls, and don't sweat it. Focus on making the right calls, then course correcting the bad ones.

Good luck.

1 comments

I think commanding on the Battlefield is the wrong metaphor, we use it a lot but its not a battle, its a sport. When you tell your developer you can't afford to pay him any more it isn't that he (or she) "dies" its that they move on to their next job. Is it painful? Of course. But it isn't death.

Sports analogies work better since there is always next season with some of the same and some different players. You decide to go for the touchdown for the win instead of the field goal to tie on 4th down. Its a choice, it works or it doesn't, you go on to the Superbowl or your don't. The decisions tomorrow will be affected by today but you will still have decisions to make.

Start-ups (and I think this is one, and I think pizza stores are start-ups too) are sprouts of a business. Sometimes they grow into bushes, sometimes trees, sometimes they can't develop enough to stay alive and they die after a while. But a start-up "dying" isn't people dying. Its people going on to do something else. For non-founders their work day may proceed pretty much unchanged other than office environment and neighbors in a new job somewhere else. As for founders? Well it demands reflection and inspection to glean the maximum amount of understanding about what worked and what didn't. Sadly its the only way to learn some of those lessons.

> Is it painful? Of course. But it isn't death.

No, but firing somebody who is the head of household and has major medical issues at home, is a helluva lot more serious than 4th down.

Absolutely it's serious. But if we're talking laying someone off because you can't make payroll, that is quite different than dismissing them for cause. Generally the latter is what I think of as 'firing'.

There are scenarios one can construct that are quite painful, the person you convinced to move out of their home town away from an ok job and family to work for you who, due to the high cost of living, had a really long commute and got into a vehicle accident their first week, because they had been putting in 80 hour weeks to come up to speed quickly, that put them into the hospital but they they hadn't worked long enough to qualify for California Disability Insurance. Can we make it any worse? Perhaps their girlfriend found out she was expecting that week and so that was why this poor guy was rushing home? And your startup goes out of business because the lead investor pulled out just before the round closes, so now they don't have a job.

I'm sure we could pile more on.

My point is that the common case, the general case, is that people have multiple jobs throughout their lives. Sometimes it is wonderful, sometimes it sucks, but when they are 60 looking back at their 20's it will be part of a much larger tapestry of experience. If for the majority of people it isn't the end of their world.

The head of household with major medical issues shouldn't be working at a tiny barely-funded startup.