Exactly why I absolutely love/hate PaaS.
“Hey developer, hosting is broken, we have solved all the SysOp tasks for you, so that you can focus on code now!”
“Hey PaaS, thanks i am already fine with my own setup.”
“But your setup sucks! Look, ours is much smoother!”
“Shut up PaaS.”
What really still sucks – heroism
I recall my life as an ops/admin and I remember what I loved to do. I loved to deploy good stuff for my users and then a few days later follow up with them to see what they liked/hated and needed. I tell myself this. But it’s not honest. I loved being the Hero, the Firefighter, the Op of Great Sacrifice For Greater Glory. The movie “300” always appealed to me. But ultimately heroism sucks.
Ops Heroism Sucks
Ops heroism sucks because when fighting fires, we’re not creating anything new of value. We’re keeping things that worked before running as before. Commitment to mission, great sacrifice, getting off the plan to keep things afloat are all laudable in times of emergency. But the real non-hero prevents outages.
The real non-hero has automated themselves out of a job, so they can do another job – bring in NEW business opportunities and new cost efficiencies by thinking creatively about their infrastructure.
From “Shut Up” to “Thank You.”
PaaS removes a whole lot of our Heroism. It just works. It scales. It has automation built in. It manages storage and networking. It gets developers working QUICKLY. OpenShift and Cloud Foundry are doing great things to make the SysOps and DevOps life VERY easy. What’s left for us to do? Am I out of a job? Well, at least I still have the onsite gear and backups to take care of. But the folks at RackN would also like to help you lose your job rolling out crash carts and deploying new hardware. Check them out, and help them out at http://rackn.com.
So, what’s my new job? Well, a lot of my old job just got more interesting. I’m still specifying hardware. I’m still overseeing shipments and rack and stack. I’m still working the networks hard. I’m still watching growth and usage and supplying my users with the best system to meet their needs. But now they’re free to hate the choice they made and change quickly. You’re free to tell them, “it’s OK to change your mind.” And my users say, “I’m free to choose something else? Some other language? Some other database? Some other software package? Some other app server?” And I can say, “Yup, no big deal.” And they say, “Thank you.” And I say, “Thank You, onsite PaaS.”
Of course I left out..
I left out Networking, Storage, and lots of other aspects of the complete IT picture. But it’s my contention that we have the same egoistic resistance to change in bringing in PaaS as we do so many of the other tools and processes that make our businesses agile.
Don’t get stuck to the same way you’ve always done things.
“Our deepest fear is not that we are inadequate. Our deepest fear is that we are powerful beyond measure.”
– Marianne Williamson A Return To Love: Reflections on the Principles of A Course in Miracles