While there seem to be a plethora of stories about how "cloud" (private or public) computing is and will revolutionize the way we work and how products are brought to market, has this really affected the way that technical people do their jobs or find new work?
For me, the biggest changes have come in how the systems I'm responsible for are deployed, secured and managed. But aside from changes in some management tools and implementation scenarios, things haven't changed all that much.
So how has the advent of more centralized computing (resource pooling, application/workload partitioning, fluid resource allocation, etc.) affected how and with whom you do your work?
(Score: 2) by sjames on Wednesday November 26 2014, @03:19PM
The funny part about cloud is it's becoming popular and widely available right at the time it's least needed.
I would have loved the cloud at one time (if it was properly maintained...), but these days IPMI typically actually works, expensive fibre channel is replaced by inexpensive AOE, common server class hardware (and a lot of desktop hardware) easily supports VMs with a fairly small performance penalty. It's a long way from the days when a kernel update meant you give the reboot command and then have a few minutes of white knuckles waiting for a ping to return. With all of that, I think of the cloud as primarily useful when temporary capacity is needed.