SoftBank's ARM Deal Reveals Who Really Understands IoT
This post is a back number of a previous entry.
It’s an old topic by now, but the SoftBank/ARM story in the headline gave me the feeling I’d finally found the answer I’d been looking for. Thanks, Son-san.
SoftBank’s original business, true to its name, was banking software — owning it and selling it. Wikipedia has plenty of detailed accounts of how it grew from there, so I’ll skip that part. (I don’t know SoftBank’s inner workings well enough to lecture on them.)
ARM, as everyone knows, licenses out processor IP — it’s fair to call it an “R&D company.” It doesn’t actually make silicon itself; it develops new architectures and earns money by licensing them. It’s a very simple business, and one that’s impossible without real technical strength. The company is based in the UK, and almost all of its development happens there too. The UK government pushes industry-academia collaboration quite hard, and it’s apparently routine for talented Cambridge students to flow into ARM. (I actually know a bit about this, so I can speak to it somewhat. Ha.) ARM’s share of smartphone chips has reportedly gotten quite high recently, but it has long been strong in small microcontrollers too, and most embedded sub-microcontrollers have been ARM-based. It even makes combos like Cortex-M0 and M4 aimed at sensor applications — honestly, for a hardware engineer, it’s a very appealing company that reaches the itchy spots you can’t quite scratch yourself.
In other words, SoftBank bet that ARM’s influence in the IoT space was only going to grow, and that bet drove the decision to go through with the acquisition amid the weak pound at the time. It’s impressive how precisely they nailed the timing. (Apparently $1 million… no wait — of the $31 billion (¥3.3 trillion) acquisition price, about $9 billion (¥1 trillion) was reportedly borrowed.)
Having come this far, you can probably see that some parts of this make sense and some raise a question mark. This is exactly what will be useful for the “way of telling apart” that’s the subject of this post. Exciting stuff.
SoftBank’s business and ARM’s business are worlds apart. In other words, what Son-san has done up to now and what ARM needs to do going forward are worlds apart. Is that a good thing or a bad thing?
Let’s start with the general discourse. It basically splits into two kinds of comments. “They’ve done well in IT, but semiconductors are a different story. The fields are too far apart.” “Superman Son-san will surely pull it off, as expected!” Which one you say is probably determined by your position. The former tends to come from hardcore hardware engineers. The latter tends to come from executives, or from people who are outsiders to both hardware and IoT.
The rebuttal to the former goes like this: “SoftBank has pulled off plenty of things before that people said were ‘a different business, impossible.’” The rebuttal to the latter would be: “People who don’t understand hardware barking about it means nothing.”
The rebuttal to the first rebuttal: “Still, there are plenty of failure cases. ARM’s going to become the biggest one of them, lol.” The rebuttal to the second rebuttal is… “If you’re going to say that, there’s no room for discussion. Back off.”
Exchanges like this actually played out online. Ha. The question of who’s right will become clear in the near future, but I’m not interested in who’s right. What interests me is the “telling apart” I mentioned at the top — I noticed that people on either side of this debate don’t fit into a certain category at all.
That category is “people who can actually drive IoT forward.”
People who casually lump together success in IT and the realities of hardware are bound to run into one hopeless wall after another once they actually start doing IoT. Things move slowly, cost money, take a long time to turn a profit. All of it is depressing and stressful. And conversely, people who can’t picture any connection between success in hardware and success in IT software are themselves part of the reason the word “IoT” gets reduced to a cheapened buzzword. Details here: Not Getting Swept Up by Buzzwords: Let’s Look at the Essence of “IoT” and “Makers” And the thing I feel most strongly while developing IoT products is this: there’s a huge gap in values and ways of thinking between people with a manufacturing/hardware background and people with an IT/software background. A gap in values means a gap in how people understand the process for reaching success and the means for achieving it. And the process for success and the means for achieving it in the IoT space can’t lean entirely toward either side. It has to be a mix — and what the right proportion of that mix is, nobody knows. Or else an entirely new methodology needs to be built from scratch. In other words, almost nobody knows what the right answer actually is.
So you need to be careful about what you say. Put bluntly, the main point I want to make here is that anyone who doesn’t recognize this is being far too naive.
In most cases, when someone makes a definitive statement about a problem that nobody knows the answer to, it’s either because they have a strong need for self-display or because they want attention through contrarian marketing. The more someone actually grasps the essence of a topic, the more their internal radar goes off: “ah, this is dangerous territory.”
For example, it’s obvious that “someone who’s just a football fan” and “the manager of a J.League club’s youth academy” will say different things. “Okazaki really hasn’t been scoring lately, they should swap him for Haraguchi or Osako, guys who are in form at their clubs” — people have probably been saying this all over the place recently. If you’re the former — just a football fan — go ahead and freely discuss it with your football-loving friends: “Yeah, totally!” or “No, Okazaki’s turned it around too, Haraguchi and Osako still lack experience.” Have at it. But suppose the latter, the manager, said this instead. It doesn’t even have to be a first-team manager. What would the players on the team think if they heard (or read) their manager making that kind of comment? “The manager’s planning to swap out starters for whoever’s in form instead of keeping the lineup fixed. Is that okay with a tournament coming up?” “So the manager doesn’t rate our pressing up front much…” “Maybe instead of making runs that draw defenders, I just need to score, period?” It has a bad effect on the team. A team’s concept, tactics, and philosophy are normally built up and stitched together with great care, but one comment like this can shake all of it loose.
This kind of thing happens even to people who aren’t in a position of running a team. Distrust from colleagues, a drop in evaluation from superiors — statements about uncertain matters are sensitive in all sorts of ways.
So when people who have absolutely nothing to do with IoT say whatever they want about it, it’s just “ah, things are lively,” nothing more. But when people who are involved with IoT — especially people who are about to build a product — make careless statements without a “unique perspective” or “firm conviction” behind them, that’s when I find myself doing some “telling apart.”
Originally published in Japanese at https://clazytech.com/2016/07/450/. Translated with LLM assistance and reviewed before publication.