Hacker News new | ask | show | jobs
by teacup50 4215 days ago
And yet, you're paying those engineers (and every other employee) to waste their time using N different non-integrated services, all of which change at random whenever a new release is pushed out, disrupting your processes.

I've been involved in this side of a startup 3 different times over a couple decades: IT systems are not a full time job for a startup. They're not even a part time job. They're an every-once-in-a-while type job. At <30 people, all you need is one engineer that can also run a single small internal server. Just one.

1 comments

> IT systems are not a full time job for a startup. They're not even a part time job. They're an every-once-in-a-while type job. All you need is one engineer that can also run a single small internal server. Just one.

Soon enough he or she will have to maintain your mail server, CRM, file server, bug tracker, CI service, backup services etc. and woops, your developer is now a sysadmin.

From experience: That level of maintenance only grows to sysadmin proportions at a scale where you can hire a sysadmin.

These systems largely run themselves, indefinitely.

Not to mention there's a lot of SysAdmins out there that will do the job very well for a lot less than $60K a year. You don't need to hire a SysAdmin who used to work on Google sized infrastructure to run your internal startup's IT.