So you don't have a sysadmin yet...*
Many startups underestimate the importance of a systems administrator very early on in the company's development. But maybe you're just not there yet. If you don't have a sysadmin, what is the minimum you should know to squeeze by in the meantime?
Many startups underestimate the importance of a systems administrator very early on in the company’s development. This person not only can make sure your systems are up, but can create the policies and toolsets that your developers, and even your non-techies, will use from the start, avoiding a whole bag of pain and woe down the road when your ad-hoc systems become untenable.
But maybe you’re just not there yet. If you don’t have a sysadmin, what is the minimum you should know to squeeze by in the meantime?
- What are the “hot spots” on a web server that are going to need attention?
- What are some good ways to protect yourself against data loss?
- What are some easy things you can do to avoid getting hacked?
- How should you go about finding a sysadmin when the time is right?
- What kinds of things should they be working on when they get started?
Justin began the mobile efforts at Mapbox in 2010 and today helps lead development of the iOS and Android SDKs, works on experimental prototyping, and assists with teambuilding efforts. He’s been working in Apple’s programming environments for fifteen years, programming professionally for twenty, and has a background in systems administration, web development, and building startups. He ran a solo consultancy for five years during the early days of the app stores, creating apps for clients and for himself. In his free time, Justin enjoys world travel, photography, hiking, and baking pies.