3 ms·
This is the worst advice. You don't want to spend resources on problems that are not yet even problems. Especially extremely early when you don't have any resou
by lmilcin 8y ago
This is the worst advice. You don't want to spend resources on problems that are not yet even problems. Especially extremely early when you don't have any resources to burn.
One super power startups have is being frugal with money, why would you want to throw it away?
- nosseo 8y agoNo engineer taking a role like this is going to expect an onboarding process. Many of them are specifically drawn by the idea they'll get to sit down and solve a problem on day 1.
- phamilton 8y ago> Many of them are specifically drawn by the idea they'll get to sit down and solve a problem on day 1 I don't see how engineer #1 or engineer #100 changes that. When I onboard a senior engineer, they get a problem on day 1.
- PeterisP 8y agoThe difference is that when hiring engineer #1 there's no technical infrastructure to which you'd onboard someone, and nobody who's really qualified to make a decent technical onboarding process - you're hiring a person to create this process (among others) from scratch, make the initial decisions themselves (instead of being told them during onboarding) and onboard others.
- wolco 8y agoOnboarding become here are the bathrooms, there is a great place to eat down the street.
- dasmoth 8y agoAgreed. Even if I’m not #1, or even #10, you’ll stand a much better chance of hiring me if you never, ever, mention the O-word in my presence. shudder