(this is page 39 of 121)





Latest

Arduino is almost the Altair

In a recent blog post "Why the Arduino Matters," Greg argues that the open source Arduino platform is on the cusp of doing for physical computing what the Altair did for PCs 30 years ago— effectively opening up a wealth of grassroots innovation that will serve as the substrate for major industries.

I love Arduino mainly because it serves as a really nice bridge between the Internet and the world of atoms we inhabit. It is trivial to program sensor-based projects with it and it really does work "out of the box" for most applications. And what is more, loads of people are really excited about the platform's prospects for hacking the physical world and are thus contributing all sorts of how-tos to wire up just about anything.

However, I have trouble seeing this really charming microcontroller-on-a-board sparking a huge revolution due to the fact that it's still too far from the network. Any Arduino project that wants to get/send data over the Internet still requires that it be tethered to a PC or that it be complemented with a ridiculously expensive Ethernet, Bluetooth, or WIFI shield which brings the cost of the total package above what a low-end PC would cost and thus limits the scope of applications significantly.

Until someone solves this networking problem in a cost-effective manner, the Arduino platform is going to remain ghettoed to the land of Lego Mindstorms (cute to learn and play but not really useful).

The great news though is that there is all sorts of hardware innovation taking place in the Arduino community; for instance, my favorite form factor for projects is called "Stickduino" because it provides all of the guts of the Arduino in something that is not much bigger than a thumbdrive.

So get hacking you network nerds, and get us a WIFI-capable Arduino board for less than $50. Then we'll have something worth making a run at the Altair.

(And no, the BugLabs stuff is too expensive and "blocky" and the Chumby is too expensive and built around the wrong assumptions. If anyone else had any other kits to mention, please leave them in the comments)

Comments Permalink

Having recently run into a table of profit per employee at different technology companies, I was floored to see the difference between the top (Google, $210k/employee) and the not-so-top (HP, $26K/employee).

While this may not be a super meaningful ratio for Wall Street (it it were mega mergers might be less popular), it does strike me as a pretty good way to gauge how much money the company has as a "cushion" to support the things that are most relevant to employees in tech companies: long term research on high risk projects, working environment spending (both IT and real estate), etc. It stands to reason that a company with high profits per employee has more to spend to keep that employee happy.

Given the large discrepancy between tech superstars, I decided to dig in a little and look across industries. The table to the left shows a random sampling of large companies in other industries which range from basic retail to other intellectual property-heavy industries like big pharma. The results are interesting.

While the bottom of the tech range doesn't quite qualify for burger flipping status, we're right around telephone repairman and significantly lower than the folks who dress up in fuzzy suits or sell sugared water.

This may give me pause the next time I wonder why I work in a veal pen and eat in a cafeteria that finds vintage a perfectly good metric to apply to milk.

Comments Permalink

Grinding sand into processors

There is tons of speculation about what Apple intends to do with PA Semi, the chip company they paid $300 million for last year. Though it varies wildly, one thing that people do agree on is that this means the fruit company is going to push more into CPU design and all of the associated accoutrements (GPUs, custom motherboard chips, compilers, deep OS tweaks, etc.)

In the words of J.J. Abrams's Scotty in Star Trek "that's essitin'" mostly because it puts a company with very deep pockets in a place where fundamental innovation can take place. Back when I was living in California and Steve had recently come back to Apple (and killed the clone business), I remember someone saying that Jobs wanted to be so vertically integrated that trucks full of sand would pull into one end of the building, and full computers would come out the other. With PA Semi they are now practically set to turn sand into chips directly!

In a related note, this past weekend, I saw an Alan Kay talk (at Intel of all places) about how the x86 straightjacket has kept software big, complex, and slow. He seems fascinated with FPGAs, going deep into how it's important for the chip to be able to adapt to the software so that it needs to run more efficiently and with fewer levels of abstraction on top of the hardware. Thanks to an NSF grant, Kay has undertaken a "grand challenge" project of implementing an entire system from the applications to the CPU instructions in 20,000 lines of code which is why he is so obsessed about having control over the individual gates.

The most amazing to me about the prospects of PA Semi inside of Apple products is how this evolution has happened. Steve might have always wanted to pound sand into chips but he started from a bunch of commonly available components glued together with great software (for both the iPhone and the iPod) and only after building a big enough business to justify this kind of vertical integration, has this move taken place. And if it works, it won't matter how many other people can buy capacitive touch displays at Foxconn. With the level of integration that Apple might achieve, they could crack something fundamental enough to stand out in terms of power management, performance, or even programmability in a way that might truly stand out.

Comments Permalink

To fulfill what seems to be a minimum quota of Twitter pieces (and proving once again that the Nytimes prefers to lead from the rear by picking up on timely web events a month after they happen), Miguel Helft has a piece on Doug Bowman's very public break with Google and subsequent escape to Twitter, a fairer place not dominated by the drudgery of data-driven interface design.

While it seemed like a fun argument to have (data versus art and instinct), it's overly simplistic as any great interface designer will use a full spectrum of tools to push the man-machine interface in creative and interesting new ways.

Interestingly enough, it has been a recently renewed interest in gaming (reignited by the iPhone and games like Rolando and Doodle Jump) that has gotten me thinking about interfaces again. Most of us have spent far too long locked in the relatively limited box model of the standards-based web for information display, and it's good every once in a while to pause and reconsider what that and the relatively crude forms-based way of interacting with the computer via a thin HTTP-powered straw have done to hold us back.

If you feel that way as well, I'd highly recommend reading Bret Victor's "Magic Ink," a long essay on the challenges in software interface design. Victor works at Apple which should give him some street cred in most people's eyes, but more significantly, he comes to the problem of interface design as a systems engineer turned design aficionado. As a result he does more to advance the thinking on interaction and interface design in the 75 pages of his essay than all of the hoopla over whether A/B tests are good for making decisions on interface elements.

Essentially, Victor calls for an end to thinking of the problem from the perspective of interactivity first and foremost, drawing a distinction between "manipulative" software, that the user uses to make something, and "information" software which is is mostly employed by users to acquire knowledge. He argues that most of the software out there today falls into this latter camp and that as a result we should invest more time, energy, and tooling into building what he calls "context-sensitive information graphics" which you can think of as Tufte on steroids— or at the very least, infoporn that takes advantage of the dynamic nature of computer displays. As he writes:

I suggest that the design of information software should be approached initially and primarily as a graphic design project. The foremost concern should be appearance—what and how information is presented. The designer should ask: What is relevant information? What questions will the viewer ask? What situations will she want to compare? What decision is she trying to make? How can the data be presented most effectively? How can the visual vocabulary and techniques of graphic design be employed to direct the user’s eyes to the solution? The designer must start by considering what the software looks like, because the user is using it to learn, and she learns by looking at it.

It's a great piece with a wealth of footnotes embedded throughout. More importantly, as computer companies everywhere race to build their visions of a "fourth computing screen" a.k.a., a tablet (the first 3 being the PC, the TV, and the smartphone), we ought to all stop to consider the ways in which we might better be able to move towards Victor's proposed information software design discipline.

Comments Permalink

David sent me a fantastic survey that provides a whole lot of good data about the who, how, where, and why of smartphone usage in the US. The most intriguing part of the study is that they dig into the "why" behind the various different choices people make and discover that iPhone owners are overwhelmingly choosing a portable web surfing experience while Blackberry owners are picking a portable email/messaging experience. By contrast the G1 phone (which I have been disappointed with) does some of everything but nothing exceptionally well and is thus hard to choose.

It's good to stop for a second while we are in the middle of AppStore mania and think about this: according to this survey, the iPhone is the best hardware representation of a web browser that you can put in your pocket out there, and this, more than any of the hype around the 3rd party ecosystem, is what drives the massive adoption.

One outstanding feature.

As we get more sophisticated in what we buy (thanks to the information tidalwave the web enables), I think that the "one outstanding feature" approach to building products and services is going to become more and more important. Think of Asus and its diminutive and cheap laptops unseating Dell and HP. Or the Flip's ease of use crushing Sony and Canon.

Another way to put it is that one amazing feature is what makes the beachhead and that everything else just solidifies that position. This is a good mental model for the apps in the AppStore— as the 3rd most important feature, they can still contribute to stickiness, but they just aren't in and of themselves that one killer thing you've gotta have.

In a related post, Mike Speiser has a nice post of diversification of products and entrepreneurs which gets at the same dynamic. In a nutshell, his post argues that being awesome at one thing demands incredible focus, and focus is the friend of success, while the opposite leads to mediocre mush. It's true of design-by-committee in big companies, but increasingly, even among the startup crowd, I've noticed this new trend for previously successful entrepreneurs to claim to want to "diversify" by taking on multiple projects at the same time. I totally get the intellectual appeal of the diversification, but at a gut level it just doesn't feel right, and Mike nails exactly why in his post.

Comments Permalink