3 ms·
1) Awful title. This is not really an article about "how you are staffing your start-up", it's an article about "start-ups should hire more sysadmins". 2) Awfu
by swombat 18y ago
1) Awful title. This is not really an article about "how you are staffing your start-up", it's an article about "start-ups should hire more sysadmins".
2) Awful central point (about the sysadmins). Early start-ups are staffed primarily with developers because developers are what start-ups need early on, before the product is launched. Put it this way: if you have a lion running after you to eat you, carrying some extra water and food might be very wise for the later part of your trip, but is completely irrelevant at this point in time, and you're better off throwing it to the ground to run faster. First, you have to escape the lion, or get the start-up off the ground and get users to love it. Until then, every penny spent on "problems that will hurt you later" is wasted.
Start-ups must be super-optimised in that manner, unless they're floating in an ocean of cash - but that's not the case of most start-ups, and that has other problems.
3) More awful points: "They’ve also given very little thought to how to enable their workforce to communicate". If your stealth-mode technology start-up needs to give thought to how to enable its workforce to communicate, you're fucked. Pack your bags and do something better with your time, stop wasting your money.
4) "they’ve either assumed that systems folks’ jobs are so easy that it can be handled by the developers" >> If the 2-3 developers in your pre-launch start-up aren't capable of sorting out their own development environment, you're fucked. See point above. If you've got a lot more than 2-3 at this point in time, you're probably fucked too.
5) Hiring someone that specialises in X isn't the only way to do X. Huge fallacy here that because "start-ups don't hire specialised sysadmins", therefore "they don't care about systems administration". That's utter bullshit. Good start-up developers are generalists and can do anything that needs to be done. Those who can't, aren't good start-up developers.
In short, this article is a fantastic example of premature optimisation applied to start-up hiring strategy.
- russell 18y agoI agree. My advice on the sysadmin problem is to get a hosted development machine. Use it for email accounts and backup or source control. It's cheap and you have solved a bunch of sysadmin tasks in an hour or so. I do think scaling should be a consideration from the beginning, but it is sufficient to have someone on the team who has actually worked on a high volume web site. If your team doesnt have a developer with the experience, ask around. Most developers are willing to contribute a few hours of advice.
- aristus 18y agoI agree -- a 20X jump in traffic or data is almost a different country. If you have someone on the team who's been to that country before, everything goes much more smoothly. Mostly because they can give you earlier warning, suggest solutions that have worked, what not to say in front of the locals, etc. If anyone has questions about architecture or scaling I have built some pretty large (>500 million queries/month) sites and I like helping out. You can find my email in my profile.