NEWSBYTE: Google hires former Samsung CTO as IoT lead

Google has hired Injong Rhee, former Samsung CTO and head of R&D for software and services, to lead its Internet of Things (IoT) practice.

In a LinkedIn post, Rhee, told his connections that he had left Samsung in December, and that his next role would be at Google as an “entrepreneur in residence”, leading the IoT business.

He will report to Diane Greene, CEO of Google Cloud, and board member of Google’s parent company, Alphabet.

“IoT is a new and exciting space with tremendous potential to transform how we use and deploy technology in our everyday lives,” he said.

Google and Alphabet have released a number of IoT-related products in recent years. For example, in 2016 they launched Android Things, an IoT platform for developers, and in May 2017 added Cloud IoT Core, a managed IoT service.

Rhee said that one of his priorities would be to, “get these efforts coordinated and aligned toward a concerted IoT story of Google”, and in the process, “create distinct consumer and enterprise product lines”.

“With support from Diane and the other members of the leadership team, I hope to grow Google IoT into a sustainable and profitable business line. No journey of this size is possible alone. I seek your continued support and encouragement as I start this new adventure,” he said.

Rhee joined Samsung back in July 2011 as senior VP of enterprise business. He stayed in the role, which was based in Seoul, South Korea, for four years before moving to Suwon, Gyeonggi-do, to take up the role of executive VP, enterprise business and mCommerce. He was promoted to CTO in December 2015.

Google’s new IoT supremo has moved to Mountain View, California, to take up his new position. On his LinkedIn profile, he says that he is “working on revolutionising IoT” at Google.

Internet of Business

For a data-centric business, the implication that Google lacks a concerted, sustainable, coordinated, and profitable IoT strategy is intriguing – but that may be reading too much into Rhee’s opening statements. That Google sees strength in his mobile credentials is clear. We wish him luck.

Read more: Cuckoo! Google flies Nest into its hardware division


IoTBuild is coming to San Francisco, CA on March 27 & 28, 2018 – Sign up to learn all you need to know about building an IoT ecosystem.

IoT Build

The post NEWSBYTE: Google hires former Samsung CTO as IoT lead appeared first on Internet of Business.

Internet of Business

Former Microsoft executive argues that Apple’s decision to slow down iOS development has nothing to do with bugs

iOS 12 Features

Alongside the release of revamped iPhone models, Apple every year also releases a new iteration of iOS, complete with a wide array of new features and system improvements. While not every iOS update is as transformative as, say, iOS 7, Apple over the years has done a solid job of adding enough compelling features to new versions of iOS to convince most users that upgrading is worth it.

With iOS 12, however, Apple will reportedly be taking a different approach. Rather than trying to cram in as many new feature as possible, Apple will reportedly scale back the scope of its annual development cycle as a means to let engineers more properly focus on system performance, bug detection, and more importantly, ensuring that new and ambitious features are properly baked before being released to millions of iOS users.

As the story goes, Apple’s about-face is the direct result of a number of high-profile bugs that have impacted both iOS and macOS over the past few weeks. Just a few months ago, for example, there was a pesky auto-correct bug in iOS 11 that auto-corrected the letter “I” and changed it to the letter “A” followed by a question mark. More recently, and far more jarring, was the discovery of a dangerous bug in macOS High Sierra which essentially allowed anyone with physical access to a Mac to gain root access to the machine.

In short, the narrative that Apple is slowing down iOS development because of a higher incidence of bugs basically writes itself.

Not everyone, though, views the situation from this exact perspective.

In an insightful series of posts on Twitter, former Microsoft executive Steven Sinofsky argues that Apple’s decision to slow down the pace of iOS development has more to do with Apple adjusting to the massive popularity of the iPhone and iPad, as opposed to a new directive to better detect bugs.

What is lost in all of this recent discussion is the nuance between features, schedule, and quality. It is like having a discussion with a financial advisor over income, risk, and growth. You don’t just show up and say you want all three and get a “sure”.

What happens to a growing project over time is that processes and approaches need to re-thought. It just means that how things once scaled—tools like deciding features, priorities, est. schedules, integration test, etc—are no longer scaling as well. That happens. ¯_(ツ)_/¯

Sinofsky further argues that the perception that Apple products are currently more buggy than they’ve ever been before is a far stretch from reality. If anything, Sinofsky posits that Apple’s software and hardware quality remain incredibly high but only seem worse because Apple’s growing and gargantuan user base results in a greater total number of users experiencing software issues, even though the overall rate may be lower than ever before.

In any absolute sense the quality of Mac/iOS + h/w are at quality levels our industry has just not seen before. Think of the scale of iPhone X release. From zero to 30M in months. That’s just insane. And it works better/more reliable than just about anything else I can buy.

How does that explain general “buggy” feeling w/ so many super smart/skilled people saying products are suffering? It’s because of the depth and scale of usage that comes w/success. A responsibility.

Look, there are bugs. You (and Apple) can make a list of them. But mostly this is about change. I know people say that isn’t the case but it is. On any absolute scale number of bugs—non-working, data losing, hanging mistakes—in iOS/Mac is far far less today than ever before.

I can’t prove this but I’ve also worked on some really big projects where people said the same thing and we had tons of data. Apple has the same data. What is different is that at scale a bug that happens to 0.01% of people is a lot of people. A stadium full or more.

Sinofksy’s full tweetstorm on the matter is well worth a read and can be viewed in its entirety over here.

Apple – BGR

BuzzFeed News just hired a former FBI official to prove the ‘pee tape’ is real


BuzzFeed news intends to fight a pending lawsuit with the White House by proving the infamous “pee tape” exists. According to a report in Foreign Policy, the website has hired a crack team of investigators led by none other than former White House cybersecurity official Anthony Ferrante, the same man who once oversaw the investigation into possible collusion between Russia and the Trump campaign after the 2016 election. Ferrante left the White House in April 2017 to work with FTI consulting. He’s now tasked with verifying the legitimacy of the dossier compiled by former British spy Christopher Steele, and the…

This story continues at The Next Web
The Next Web

Former Apple developer explains why the company’s software is struggling

iOS new features

In recent months, Apple’s software development has been called into question like never before. Between a critical security bug in macOS, a brand-new product being launched late and without half of its features enabled, or a throttling feature being snuck into an iOS update, it seems that something is wrong in Apple’s development process.

Outwardly, the company says everything is fine, while also revealing that it’s going to take a year off from major feature development to focus on bug fixes and performance. But according to one software engineer who worked on iChat and Maps for years, the problems run deeper than just a lack of focus.

Posting on Reddit, the engineer attributed Apple’s software problems to a culture, not a lack of focus:

As someone who used to work on iOS at Apple, what that company honestly needs is a culture not beholden to the whims of their EPMs (project managers). They used to help organize and work with engineering to schedule things across the company’s waterfall style development. However, by the time I left, they essentially took power over engineering. Radar became the driver for the entire company and instead of thinking about a holistic product, everything became a priority number. P0 meant, emergency fix immediately, P4 meant nice to have. You get the idea.

Nothing could be worked on if it wasn’t in Radar with a priority number attached and signed off by the teams’ EPM. No room for a side project or time away from your daily duties because there were always P1s to fix. If you didn’t personally have any left for the day, you’d take one from another engineer who was likely swamped with their own list of P1s.

Software engineers are notorious for complaining about the layers of management getting in the way of their process, but Apple’s culture here doesn’t exactly sound conducive to producing quality code:

P1 P1 P1, everything is always in crises mode. Also why I and everyone around me felt bad for taking any vacation. If we weren’t constantly thinking about fixing those P1s, we were some how letting our team down.

This is how you get bugs in shipping software. EPMs driven to schedule things and over manage engineers would decide on a whim that something was a P2. That was basically always shelved to a follow-up .1 release.

Ultimately, engineers lost the freedom to decide when a feature was ready to ship. So here I see some “leak” about quality and I think, this is just PR spin for a buggy iOS 11. Unless the company is willing to take power away from the all-mighty EPM org, I just don’t see how engineering will really change.

The engineer’s account lines up perfectly with what Apple’s Craig Federighi told software teams recently, according to Bloomberg:

Software chief Craig Federighi laid out the new strategy to his army of engineers last month, according to a person familiar with the discussion. His team will have more time to work on new features and focus on under-the-hood refinements without being tied to a list of new features annually simply so the company can tout a massive year-over-year leap, people familiar with the situation say. The renewed focus on quality is designed to make sure the company can fulfill promises made each summer at the annual developers conference and that new features work reliably and as advertised.

Apple – BGR

Apple’s shift in iOS development pace about evolving scale, not coping with bugs, says former Windows chief

Article Image

Apple’s "cultural shift" towards spacing out new features in iOS is more a natural function of development scale, and not really the revolution some people might perceive it to be, according to a noted former Microsoft Windows president.
AppleInsider – Frontpage News