Introducing new technology in the workplace is making the majority of people – three in five – feel anxious while the same number have concerns over whether their job is safe when it comes to tasks being automated.
And half of staff express such fears about change when businesses introduce any “digital transformation” projects, the study by Goldsmiths University and YouGov found and more than a quarter of business leaders said they meet “resistance” from employees.
The report also identified that only 53 per cent of business are investing in digital transformation, despite the same amount saying their industries faced disruption over the next two years.
More from another article:
One of the more significant findings from the research is that younger workers are more fearful of digital disruption affecting their jobs than older staff are.
The study found that the people most fearful of workplace change fall into the 18-24 age range. Employees who said they feared the least about their jobs being disrupted was the 55-plus age group.
Commissioned by Microsoft, but, whatever.
Source: The way businesses are adopting technology is totally spooking staff, Microsoft study finds
According to Telstra, in some cases, its software development time has decreased from 6-8 months to 10-12 weeks through its work with Pivotal,
More on how widespread it is:
Telstra has moved 100 of its internal teams to Pivotal’s agile software development platform since partnering with the enterprise software company two years ago, with the telco saying this accounts for around 25 to 30 percent of its business.
Under the partnership, Telstra’s teams have been trained in Pivotal Labs to build software using agile methodologies on Pivotal Cloud Foundry, with an end goal of shifting 400 teams encompassing around 4,000 to 5,000 staff members to the cloud software-development platform.
Source: Telstra, Pivotal get up to speed with partnerhip
SLOs are objectives that your business aspires to meet and intends to take action to defend; just remember, your SLOs are not your SLAs (service level agreements)! You should pick SLOs that represent the most critical aspects of the user experience. If you meet an SLO, your users and your business should be happy. Conversely, if the system does not meet the SLO, that implies there are users who are being made unhappy!
Source: Building good SLOs – CRE life lessons
The developer of cloud-agnostic solutions has raised $74 million in total since its founding in 2012.
Source: HashiCorp Secures $40 Million In A Funding Round That Will Boost Its Channel Program
How all these unprofitable companies sustaining high valuations:
bending reality today has three elements: a vision, fast growth, and financing.
A few firms other than Amazon have defied the odds. Over the past 20 years Las Vegas Sands, a casino firm, Royal Caribbean, a cruise-line company, and Micron Technology, a chip-maker, each lost $1bn or more for two consecutive years and went on to prosper. But the chances of success are slim. Of the current members of the Russell 1000 index, since 1997 only 37 have lost $1bn or more for at least two years in a row. Of these, 21 still lose money.
Source: SchumpeterFirms that burn up $1bn a year are sexy but statistically doomed
It happens to be the case that CF — because it’s an app platform and wants to let the user focus on their code — provides a way to convert code in to containers inside the platform without having to start messing around with Dockerfiles and the like. And this functionality even does some cool things for you like keeping your container OS automatically patched so you don’t have to build CI pipelines to monitor your base images and rebuild stuff.
That’s why I love Cloud Foundry’s Application Runtime. Of course, because of these constraints — the constraints that are why I love it — the App Runtime can’t possibly work for complex stateful services: the whole point is for it not to. And that’s why it’s fantastic that there’s now a Container Runtime (which I wish we’d called a Stateful Services Runtime because that’s how I think of it).
Source: CF vs Kube: Is the difference who creates the container?
There’s a new survey out from the Cloud Foundry Foundation, looking at the users of Cloud Foundry. Here’s some highlights and notes:
- Another ClearPath joint, n=735.
- It’s important to keep in mind that this is covers all distress of Cloud Foundry, including open source (no vendor involved).
- “The percentage of user respondents who require over three months
per app drops from 51 percent to 18 percent after deploying Cloud Foundry Application Runtime”
- “…while the percentage of user respondents who require less than a week climbs from 16 percent to 46 percent.”
- “Nearly half (49 percent) of Cloud Foundry Application Runtime users are large enterprises ($1+ billion annual revenue).”
- This chart is hard to read, but it shows a reduction in time to deploy across various time periods:
- Uptake is early, but there are definitely mature users: “A plurality of Cloud Foundry Application Runtime users (61 percent) describe their deployments as somewhere in the early stages—trial, PoC, evaluation, or a partial integration into specific business units. Meanwhile, 39 percent have deployed Cloud Foundry Application Runtime more broadly across their company, from total integration in specific business groups to company-wide deployment.”
- “Comcast, for example has more than 1500 developers using Cloud Foundry Application Runtime daily. Home Depot reports more than 2500 developers.”
- “Comcast has seen between 50 percent and 75 percent improvement in productivity.”
- “Half of Cloud Foundry Application Runtime users are currently using containers, such as Docker or rkt, with another 35 percent evaluating or deploying containers.”
- Container management – there’s a wide variety of tools that people use for container orchestration, including DIY (14%). There’s a lot of interest in having CF do it: “Nearly three-quarters (71 percent) of Cloud Foundry Application Runtime users currently using or evaluating containers are interested in adding container orchestration and management to their Cloud Foundry Application Runtime environment.” Hence, validating the Cloud Foundry Container Runtime.
- Of course, the surveyed are already CF users, so they’re biased/driven by what they know.
- Almost half of respondents say that getting started with CF. But people end up liking it: “An overwhelming majority of users (83 percent) would recommend Cloud Foundry Application Runtime to a colleague, including 60 percent who would do so strongly.”
- “As more companies roll out Cloud Foundry Application Runtime more broadly, the footprint continues to grow. Currently, 46 percent of users have more than 10 apps deployed on Cloud Foundry Application Runtime, including 18 percent with over 100 (and eight percent with over 500).” 4% have over 1,000 apps.
- CF’s uses: “The primary use is for microservices (54 percent), followed by websites (38 percent), internal business applications (31 percent), Software-as-a-Service (SaaS) (27 percent) and legacy software (eight percent).”
- Validating multi-cloud: “60 percent say this is very important, and another 30 percent describe it as somewhat important.” Meanwhile, 53% are using more than one type of IaaS.
I assume this is across distros, and including use of just the ope source stack,
Source: Cloud Foundry adds native Kubernetes support for running containers, TechCrunch