Skip to main content

EWSN 2010 Keynote Video

I've posted the video for my keynote at EWSN 2010 below. You can check out the full resolution version at


  1. Matt, fascinating talk, thanks for putting it up here.
    I was quite amused by the comment about Industry at the end. The funny thing is that some of bulk in sensor networks research is really not important in Industry either. We recently used CC2530 based motes to put together a home automation system , only to realize that we could drive down the cost signficantly by actually not sticking to Zigbee
    or even 802.15.4. One of the fascinating solutions that I believe could be cheap for that application is actually based a generalization of the google meter like concepts.
    Clearly, I am not a big fan of sensor networks being treated as just constrained wireless ad-hoc networks, there is more to it. Ofcourse would be good to see applications, and hence AI getting increasingly integrated with sensor networks research. Off to read your papers on Robobees

  2. hi
    it was very interesting i live in Iran and i want to use this video in my conferans about wsn if you allow to me
    thanks for such interesting thing

  3. ghader- You are certainly welcome to use this video as long as you adhere to the Creative Commons license terms that I have released it under:


  4. Hello Mark,

    Thank you for this very interesting video. Could you please send me the video where the behavior of the bee hive is shown? My e-mail is

    Many thanks

  5. Matt - a very thoughtful and humorous talk. I enjoyed it. Forgive me for being a bit contentious to make a point: you do not appear to have any idea what is going on in commercial wireless sensor networks. A friend of mine in the WSN industry pointed me to your talk with the statement "It's amazing what this guy doesn't know."
    Based on my experience with commercial deployments, I would say that your list of solved and unsolved problems is out of touch with the state of the art in industry.
    I'm astonished that in a talk on the next 10 years of WSN you made no mention of commercial deployments and standards: Zigbee, WirelessHART, IPSO, etc. . There were about $100 million in sales of wireless mesh sensors sold in industrial automation alone last year. The performance and scale of those WirelessHART networks would clearly suprise you. I'm no big fan of Zigbee, but the scale of their deployments is about three to four orders of magnitude above the networks you refer to. I don't think that ABB, BP, Chevron, Emerson, GE, Siemens etc. would agree that security, energy management, fault tolerance, and network management are unsolved problems. So *of course* it appears to you that industry is losing interest in WSN - academics have no idea what industry is really doing, and so academics work on problems that have no relevance to industry, so industry ultimately gives up and ignores academia.
    The reality is that this industry is *finally* taking off in a big way, with almost zero credit due to academic research.
    What really puzzles me is why this has happened in WSN. I've never seen such a disconnect between industry and academia. In MEMS, ICs, and IC CAD, academics still often work on far-out projects, but always with an awareness of where industry is. For some reason, the "inner circle" of academics in WSN does not do this, much to the detriment of the field.


  6. Kris, you hit the nail on the head. I *don't* really know what's happening in the WSN industry, not to that level of detail. I'm not sure that most academics do, and unless they are working closely with companies in this space I'm not sure how they are supposed to find out.

    I don't know how to solve this problem. It might be that the level of competition in the WSN space is so high that companies are not that forthcoming about what they have accomplished. Certainly we see essentially zero paper submissions from industry to the major conferences. Maybe I need to start reading more trade mags, though they make me want to gouge my eyes out when it's impossible to tell what's real and what's marketing hype.

    This problem is not specific to WSNs, of course; only in the last few years has there been more visibility of the "real world" problems from places like Google, Amazon, etc. - brought on largely because they started attending, and publishing in, the major academic conferences. Even so I'd argue that a lot of academics are working on "industrially irrelevant" problems largely because they are unaware of what's out there.

    Can you help us fix this???

  7. Hi Prof. Welsh, great video. The concept of robobee is very interesting. It reminds me of particle swarm optimization algorithm I was once working on. A TinyOS program running distributed particle swarm optimization protocol will be cool.

  8. Matt, thanks for an interesting and inspiring talk, and citing my OASIS volcano project. Also thanks for your good words about us. Regarding your comments whether iMOte2 and TinyOS is a suitable choice, I have some different view: (1) iMote2 is sufficient capable for this application, and also has low energy consumption; it is a good tradeoff, although it has a funny small size comparing to the spider box. We did not see that there is no need to use a more capable board, except that its CC2420 radio has too low power output. (2) We adopted TinyOS platform, because we need to compare our design to other existing approaches in the community (for writing papers :-)) and TinyOS has largest user community and implementations of WSN. In such a real project, we have to consider design tradeoffs and time overhead ...


Post a Comment

Popular posts from this blog

Why I'm leaving Harvard

The word is out that I have decided to resign my tenured faculty job at Harvard to remain at Google. Obviously this will be a big change in my career, and one that I have spent a tremendous amount of time mulling over the last few months.

Rather than let rumors spread about the reasons for my move, I think I should be pretty direct in explaining my thinking here.

I should say first of all that I'm not leaving because of any problems with Harvard. On the contrary, I love Harvard, and will miss it a lot. The computer science faculty are absolutely top-notch, and the students are the best a professor could ever hope to work with. It is a fantastic environment, very supportive, and full of great people. They were crazy enough to give me tenure, and I feel no small pang of guilt for leaving now. I joined Harvard because it offered the opportunity to make a big impact on a great department at an important school, and I have no regrets about my decision to go there eight years ago. But m…

Rewriting a large production system in Go

My team at Google is wrapping up an effort to rewrite a large production system (almost) entirely in Go. I say "almost" because one component of the system -- a library for transcoding between image formats -- works perfectly well in C++, so we decided to leave it as-is. But the rest of the system is 100% Go, not just wrappers to existing modules in C++ or another language. It's been a fun experience and I thought I'd share some lessons learned.

Why rewrite?

The first question we must answer is why we considered a rewrite in the first place. When we started this project, we adopted an existing C++ based system, which had been developed over the course of a couple of years by two of our sister teams at Google. It's a good system and does its job remarkably well. However, it has been used in several different projects with vastly different goals, leading to a nontrivial accretion of cruft. Over time, it became apparent that for us to continue to innovate rapidly wo…

Running a software team at Google

I'm often asked what my job is like at Google since I left academia. I guess going from tenured professor to software engineer sounds like a big step down. Job titles aside, I'm much happier and more productive in my new role than I was in the 8 years at Harvard, though there are actually a lot of similarities between being a professor and running a software team.

I lead a team at Google's Seattle office which is responsible for a range of projects in the mobile web performance area (for more background on my team's work see my earlier blog post on the topic). One of our projects is the recently-announced data compression proxy support in Chrome Mobile. We also work on the PageSpeed suite of technologies, specifically focusing on mobile web optimization, as well as a bunch of other cool stuff that I can't talk about just yet.

My official job title is just "software engineer," which is the most common (and coveted) role at Google. (I say "coveted&quo…