Startup Systems Εngineer's Instruction Manual
summary
Jumping in as the sole systems engineer at a startup means owning the full stack: Salt Stack and Fabric for provisioning, Jenkins for automated deploys, a handful of VMs (five servers, some on DigitalOcean) and a single database server to plan for scaling. Key actions are: enable configuration management day one, add monitoring/alerts, validate backups by restoring, stop everyone logging in as root, document templates and runbooks, iterate rather than overengineer, and train developers so deployments become routine.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:29Configuration Management and Registration
- 7:37Backups
- 8:09Security
- 15:12Common Mistakes
- 15:47Over Engineering
- 16:10Failure To Decode Information
related talks
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration
48mDevops@Scale
33mDeveloping for Multi-Component Environments While Keeping Your Sanity
55mDevOps @Scale (Greek Tragedy in 3 Acts)
05mDevOps for Startups
08mGetting started with DevOps
42mPlatform Engineering in practice — Why and How to start
52mDevops @Scale