The Drupal Developer's Road To Server Hell

SO. YOU'RE GONNA BUY SOME HOSTING.: - THE DRUPAL DEVELOPERS ROAD TO SERVER HELL. STEP 1 Development Server? This could be fun! I'll just spin up a LAMP stack and add some of my favorite debugging tools. HOURS :5 SERVERS:1 STEP 2 Version Control. 'll just need to set up a git repository and wire it up to deploy whenever we push code. HOURS : 10 SERVERS: 1 STEP 3 Production Server. We'll start out with a big VPS and set it up like before. HOURS : 20 SERVERS: 2 STEP 4 Deployment. Time for a git workflow and some shell scripts. HOURS : 40 SERVERS: 2 STEP 5 Testing. I guess that means we'll need a staging server. Sounds like eveyone uses Jenkins. Something new to learn. SCRIPTS HOURS : 60 SERVERS: 3 STEP 6 Performance. It looks like I need to optimize these environments. I guess you need to tune Linux for Drupal. HOURS : 80 SERVERS: 3 STEP 7 Scalability. Looks like we need some cache servers to make it work. Redis & Varnish seem like the standards. HOURS : 100 SERVERS: 5 STEP 8 I High Availability? Oh man.. Too many single points of failure I'll need double the servers, I guess. HOURS 200 SERVERS: 10 STEP 9 Security. Looks like there is a security patch. I need to make the updates, reboot the servers, and make sure nothing crashes. HOURS : 250 SERVERS: 10 STEP 10 On-Call. Great!, Now l'm carrying the pager for a cluster, and responding to problems 24x7. What happend to my job building websites? HOURS: 250 SERVERS: 10 TOTAL HOURS HOURLY RATE LABOR COST 250 S125 S31250 IS THIS WHAT YOU'RE DOING INSTEAD OF YOUR JOB? MAYBE YOU SHOULD SEND THIS TO YOUR BOSS E PANTHEON #HOSTINGISDEAD GETPANTHEON.COM