Conn’s HomePlus CIO Todd Renaud spent the early days of the COVID-19 pandemic’s office shutdowns and store restrictions “just trying to get through the next day.” One month later, he’s setting his sights on what the next new normal might be, and what it will mean to the appliance retailer’s IT strategy over the next year.
“I’m going to assume that our remote workforce will be a larger percent than it is today,” he says. “How will that impact the company, assets and data? I’m thinking about the impact in our stores if we continue to have restrictions on the number of people” inside and other safety requirements. For example, Renaud is considering videoconferencing capabilities that could enable customers to virtually walk through the store with a sales rep serving as a guide to simulate an in-store sales experience.
“The unspoken expectation is of me staying as far ahead of the curve from a technology and an impact perspective as I can,” Renaud says.
That same expectation has been heaped onto most CIOs as organizations look to technology to help them pivot quickly. The coronavirus pandemic is affecting IT leaders’ roles and priorities, and forcing them to consider its long-term impact on their IT organizations and on business as a whole.
An IDG survey of 414 IT leaders in April found that most budgets will either hold steady or increase in the next 12 months. They also expect a renewed emphasis on operational efficiency, expense management and cost controls. Meanwhile, business collaboration, hiring and training will take a back seat in the coming months. CIO.com compared these responses to its 2020 State of the CIO Survey, which posed similar questions to IT leaders in September 2019 about their organizations’ IT budgets and priorities for the coming year.
Alexa is always listening but not continually recording. It doesn’t send anything to cloud servers until it hears you say the wake word (Alexa, Echo, or Computer). But listening for wake words is harder than you might think.
Echo hardware isn’t all that intelligent. Without the internet, any request or question you ask will fail. This is because your commands are sent off to the cloud for interpretation and decisions. Amazon doesn’t want every conversation you have in front of a smart speaker to be recorded, but rather, just the commands you give the smart speaker. For this reason, the company employs a wake word to get the smart speaker’s attention. To accomplish this, Amazon uses a combination of fine-tuned microphones, a short memory buffer, and neural net training.
Fine-Tuned Microphones Pinpoint Your Voice
Voice assistant speakers, like Echo and Echo Dot, typically have multiple built-in microphones. The Echo Dot, for instance, has seven. That array gives the devices several abilities, from hearing commands spoken far away, to separating background noise from voices.
The latter is especially helpful for wake word detection. Using its multiple microphones, the Echo can pinpoint your location relative to where it’s sitting and listen in that direction while ignoring the rest of the room.
You see this in action whenever you use the wake word. Stand to the side of an Echo or Echo Dot and say the wake word. Notice the ring lights up in dark blue, and then a lighter blue as it circles and “points” toward you. Now, move several steps to the side and say the wake word once again. Notice the light-blue lights follow you.
By reducing its capability, Amazon not only gives you more privacy (it’s one less place your voice is stored) but also prevents Echo from listening to entire conversations, limiting its focus to finding the wake word.
Imagine you had a three-second cassette and a tape recorder. Suppose after it reached the end, the tape looped back around to the beginning over and over. If you started recording a conversation, everything you said four seconds ago would be wiped and immediately recorded over. That’s what an Amazon Echo does.
It records continuously but wipes everything it just recorded at the same time. That short attention span means all it can hear is the word, “Alexa,” and not much more. Three seconds, though, is long enough for that word to be recorded, examined, and acted upon appropriately.
The idea is to cover every inflection and accent, but also the context. Amazon wants your Echo to recognize the difference when you’re talking to it, when you’re talking about it, or, perhaps, when you’re talking to a person named Alexa. The directional mics also assist with that goal.
With every word the Echo hears, it runs audio through layers of algorithms. Each layer is designed to rule out false positives, looking for sound-alikes or context clues. If one layer check passes, the word goes to the next. Finally, when the local device decides it did hear the wake word, it begins to record and pass on the audio to Amazon’s cloud servers. Amazon employs four algorithms: one for each wake word (Alexa, Computer, Echo), and one for Alexa Guard, which treats specific sounds, such as glass shattering, like a wake word.
But even when a match occurs, Amazon still runs more complicated checks. Have you noticed that when someone speaks the word Alexa on a TV show or commercial, it usually doesn’t elicit a response from your Echo? That’s because Amazon also does a cloud check.
Cloud Checks Rule Out Some False Positives
When companies make commercials that feature Alexa, they can submit the audio to Amazon. The company runs the audio through similar pattern matching algorithms used to identify the wake word. Once that exact instance is fully cataloged, it’s added to a database.
As part of the process when reaching out to the cloud, your Echo includes information about the wake word it heard and checks that database. Whenever it finds a match, Amazon instructs your Echo to ignore the wake word, shut down, and discard any recorded audio.
Additionally, Amazon checks for instances of the wake word spoken simultaneously. Not every company submits audio to Amazon, so the company came up with a novel backup solution. After checking for a database match, the company compares the wake word imprint against any other instances coming in at the same time. It’s unlikely that two people who say Alexa simultaneously would sound exactly alike, so if there’s a match, Amazon knows it’s likely a commercial or TV show and ignores the request.
Despite all the checks, false positives do still occur. You can listen to what your Echo has recorded at Amazon’s privacy hub, and you’ll likely find at least one false positive in the bunch. But the technology is continually being improved and, eventually, Amazon would like it to function without a wake word at all.
DataCamp CEO Jonathan Cornelissen is stepping down “indefinitely” in the wake of “uninvited physical contact” with an employee in 2017. The move comes after an uproar in the R community over what was seen as an inadequate response by the company and no punishment or consequences to the executive.
In an apology posted earlier today, Cornelissen said the company will establish an Instructor Advisory Board, and an independent third party will conduct “a full review of the company’s environment and culture, including its response to the incident.”
Instructors had been working behind the scenes for months to get the company to acknowledge the incident internally and ensure that the executive faced some penalty for his actions. After a letter was sent to management that was signed by 100 or so instructors, DataCamp published a public blog post from “the DataCamp Leadership team.” However, instructors and others in the community viewed that as inadequate.
Among the criticisms at the time: There was no apology to the victim, the victim had not been notified before the public statement, no one at the company took personal responsibility for what happened, and for days the post had a “noindex” tag to prevent search engines from showing the post in its results.
Calls to boycot the platform had been growing, and organizations such as RStudio and satRdays said they were cutting ties with DataCamp, at least temporarily. Numerous instructors went public asking people not to take their courses; and most recently several employees went on social media expressing concerns to the community.
DataCamp’s Board of Directors issued a statement today as well, noting: “Our public response and this first official statement from the Board regarding this incident is long overdue. We are sorry for this delay.” The incident occurred in October 2017; management was made aware of it more than a year ago.
“We have learned a lot from the community over the last several weeks and recognize that the company hasn’t listened nearly enough to you over the last 18 months,” the board said in the statement, noting that Cornelissen will be on an indefinite leave without pay.
The board also said it has hired civil-rights attorney Anurima Bhargava, who has “specific expertise on sexual harassment and climate assessments, to conduct a full review of the company’s environment and culture.”
One of the criticisms of the company’s initial statement was that it said there had been a review “by a third party not involved in DataCamp’s day-to-day business.” That was seen by many as the possibility that an investor not involved in day-to-day activities – but who might be naturally sympathetic to management – could have conducted the review.
The victim, Kara Woo, is a well-known and well-liked member of the R community. She acknowledged on Twitter after DataCamp’s initial post that she had been the target. The company did not name the executive until today, although at least one blog post and one media report did so last week.
Woo told Computerworld last week: “All I have to say currently is that I am very moved by the outpouring of support, and I hope anyone else in a similar situation knows that people in this community will have their back.”