Our new episode is up, from this past Friday:
There’s tell that some people just look at containers as a cheaper way to virtualize, eschewing the fancy-lad “cloud-native stuff.” We discuss that idea, plus “the enterprise cloud wars,” and also our feel that Slack is actually a really good tool and company.
Listen directly, subscribe to the podcast feed, and go check out the full show notes, which has a web player as well.
It’s a sore point for many shoppers, who are ready and eager to spend more on designer clothes if only they were available: 78% of respondents in a recent survey of plus-size shoppers said that they’d be willing to spend more money if designers offered more options, and 80% said they’d likely purchase an item from their favorite designer if that designer made plus sizes.
File under “if anything, more money. Plus, bonus: morals!”:
More and more designers and retailers seem to be waking up to that fact. The market for plus-size women’s clothing is over $20 billion, by some measures
From Snap’s S-1, via Ben:
In a world where anyone can distribute products instantly and provide them for free, the best way to compete is by innovating to create the most engaging products. That’s because it’s difficult to use distribution or cost as a competitive advantage—new software is available to users immediately, and for free. We believe this means that our industry favors companies that innovate, because people will use their products.
Less than 5% of white men surveyed said they considered a lack of diversity a top problem. Three-out-of-four respondents were unaware of any initiatives to make their companies or portfolios more diverse. And 40% of male respondents were sick of the media going on and on about it.
Meanwhile, in political land:
the more privileged you are, the less that oppression personally affects you, the less urgency you perhaps have to get involved in the fight.
According to Shireen Mitchell, activist and founder of Digitalsista, much of the reason women of color are so often on the front lines is because it’s work that needs to be done, and they don’t see anyone else stepping up. “Women of color are always taught to build community to get things done, and in my opinion, most white men are taught that they can only succeed if they are the ‘savior’ for the community. With this mindset, they know they can’t really do that job when it comes to inclusivity because of their inherent bias.”
As those stats on hiring above show, there’s plenty of room for white men to try new ideas out, e.g.:
That leads to white people, especially white men, waiting to act until they feel they will be acknowledged and congratulated for their work. “What we need is for them to take initiative, grow from being uncomfortable and making mistakes. Use their privilege to elevate those who are taking the lead and not add to taxing or using their labor,” says Mitchell.
At first, you’re like, “oh, another piece where someone makes fun of us nerds and misunderstands our damagingly sarcastic way of saying everything that belies the privilege we all live under.” Then you’re like, “oh, this is actually a good piece.” E.g.:
Human rights work attempts to prevent the abusive deployment of power against those who have little of it. While technology might disrupt some power structures, it might also reinforce them, and it is rarely designed to empower the most vulnerable populations. Human rights defenders are innovative, and they have used software to do work it wasn’t designed to do, such as live-streaming police violence against civilian populations to press for government accountability. But perpetrators of mass violence are innovative too. Software alone is unlikely to provide clear human rights victories.
Assuming that adopting the tool is feasible, do the benefits this tool provides outweigh the cost of disrupting your existing workflow?
People rarely consider that, in all walks of life.
Source: Tech folk: ‘Move fast and break things’ doesn’t work when lives are at stake
Whether it’s “DevOps,” “digital transformation,” or even “cloud” and “agile,” middle-management is all too common an issue. They simply won’t budge and help out. This isn’t always the case for sure, but “the frozen middle” is a common problem.
With a big ol’ panel of people (including two folks from RedMonk), we talk about tactics for thawing the frozen middle.
Check out this talk on “cloud-native”:
We’ve got all your answers to “what exactly is ‘cloud-native’?” in this episode with special guests Pivotal’s Kenny Bastani and RedMonk’s James Governor. Kenny gives us a good overview of what cloud-native is, as Coté summarizes it: handling the configuration and automation for your applications along with all the supporting frameworks and platforms to do that. We then discuss the process (“culture”) angle, the origin of Spring Boot, the concept of “lock-in,” and if public cloud is needed or not. Bonus: serverless talk!
In this week’s episode, Richard and I talk with Dino about the work Pivotal does to help companies quickly start migrating applications to Pivotal Cloud Foundry. Check it out, and subscribe if you haven’t already.
That chart is in millions, i.e., 260m in 2016; the write-up on Quartz is a little wonky in that respect.
From IDC: “Annually, shipments of traditional PCs slipped to 260 million units, down 5.7% from 2015.”
Source: Worldwide PC sales are exactly where they were in 2008 — Quartz