“industry adoption more accurately reflected in 451 Research’s survey data that pegs adoption at 27 per cent. Of those 27 per cent of enterprises that have container religion, just 52 per cent are running containers in production, according to the same survey. In other words, a mere 13.5 per cent (or so) of enterprises are running containers in production.” Link to original

“industry adoption more accurately reflected in 451 Research’s survey data that pegs adoption at 27 per cent. Of those 27 per cent of enterprises that have container religion, just 52 per cent are running containers in production, according to the same survey. In other words, a mere 13.5 per cent (or so) of enterprises are running containers in production.” Link to original

“industry adoption more accurately reflected in 451 Research’s survey data that pegs adoption at 27 per cent. Of those 27 per cent of enterprises that have container religion, just 52 per cent are running containers in production, according to the same survey. In other words, a mere 13.5 per cent (or so) of enterprises are running containers in production.” Link to original

“Vendor lock-in is not the hardest thing to overcome, Architectural lock-in is harder to overcome. If you built your new app components today optimizing for constraints of a VM, you will have a harder time moving to future than migrating an app from AWS to GCP. For example, using Kubernetes for new workloads creates an architecture lock-in that you will have a harder time getting out of it and move to serverless.

“Vendor lock-in is not the hardest thing to overcome, Architectural lock-in is harder to overcome. If you built your new app components today optimizing for constraints of a VM, you will have a harder time moving to future than migrating an app from AWS to GCP. For example, using Kubernetes for new workloads creates an architecture lock-in that you will have a harder time getting out of it and move to serverless.

“Vendor lock-in is not the hardest thing to overcome, Architectural lock-in is harder to overcome. If you built your new app components today optimizing for constraints of a VM, you will have a harder time moving to future than migrating an app from AWS to GCP. For example, using Kubernetes for new workloads creates an architecture lock-in that you will have a harder time getting out of it and move to serverless.

‘between 2011 and 2012, the polling company Gallup conducted the most detailed study ever carried out of how people feel about the thing we spend most of our waking lives doing – our paid work. They found that 13% of people say they are “engaged” in their work – they find it meaningful and look forward to it. Some 63% say they are “not engaged”, which is defined as “sleepwalking through their workday”.

‘between 2011 and 2012, the polling company Gallup conducted the most detailed study ever carried out of how people feel about the thing we spend most of our waking lives doing – our paid work. They found that 13% of people say they are “engaged” in their work – they find it meaningful and look forward to it. Some 63% say they are “not engaged”, which is defined as “sleepwalking through their workday”.

‘between 2011 and 2012, the polling company Gallup conducted the most detailed study ever carried out of how people feel about the thing we spend most of our waking lives doing – our paid work. They found that 13% of people say they are “engaged” in their work – they find it meaningful and look forward to it. Some 63% say they are “not engaged”, which is defined as “sleepwalking through their workday”.

A pretty good moral tent-pole for tech. Link to original