Ian Rose

Ian Rose

Division of Engineering and Applied Science
Harvard University

238 Maxwell Dworkin

33 Oxford Street, Cambridge MA 02138

Phone (lab): (617) 496-4510

I'm a third-year computer science PhD student in the Division of Engineering and Applied Science at Harvard University. My research advisor is Radhika Nagpal. I participate in the following research groups: Self-Organizing Systems Research (SSR), Systems Research at Harvard (SYRAH). Here is my slightly out of date resume.

I'm interested broadly in how to build reliable distributed systems. Currently, I'm involved with the CitySense project, which aims to develop and deploy an urban scale wireless testbed and sensor network. I am looking at applying wireless network monitoring techniques to this unique setting. More generally, my current and past research has involved wireless sensor networks, content distribution, bio-inspired systems and game theory.

CitySense: An Urban-Scale Wireless Sensor Network and Testbed. Rohan Murty, Geoffrey Mainland, Ian Rose, Atanu Roy Chowdhury, Abhimanyu Gosain, Josh Bers, and Matt Welsh. In Proceedings of the 2008 IEEE International Conference on Technologies for Homeland Security, Waltham MA, May 2008. [pdf]

Cobra: Content based Filtering and Aggregation of Blogs and RSS Feeds. Ian Rose, Rohan Murty, Peter Pietzuch, Jonathan Ledlie, Mema Roussopoulos, and Matt Welsh. In Proceedings of the 4th USENIX Symposium on Networked Systems Design & Implementation (NSDI '07), Cambridge MA, April 2007. [pdf] [slides]

DESYNC: Self-Organizing Desynchronization and TDMA on Wireless Sensor Networks. Julius Degesys, Ian Rose, Ankit Patel, Radhika Nagpal. In Proceedings of the 6th International Conference on Information Processing in Sensor Networks (IPSN '07), Cambridge MA, April 2007. [pdf]

Diagnosis of breast cancer using elastic-scatting spectroscopy: preliminary clinical results. Irving J. Bigio, Stephen G. Bown, Gavin Briggs, Christine Kelley, Sunil Lakhani, David Prichard, Paul M. Ripley, Ian G. Rose, and Christobel Saunders. Journal of Biomedical Optics, Volume 5, Issue 2, April 2000

Spring '08 - Teaching Fellow for CS 262 ("Introduction to Distributed Computing").

Fall '07 - Teaching Fellow for CS 266 ("Biologically-inspired Distributed and Multi-agent Systems").

Fall '06 - Teaching Fellow for CS 260r ("Special Topics in Computer Systems: Internet Scale Sensor Networking").

Summer 2007: Intern, Sun Microsystems, Project Darkstar (supervisors: Jim Waldo and Karl Haberl)

2005-present: PhD candidate, Harvard University

2000-2005: Senior Software Design Engineer, Alarm.com

1998-1999: Research Intern, Los Alamos National Laboratory (advisor: Irving Bigio)

1996-2000: Undergraduate, Dartmouth College (A.B. Computer Science)

"We will encourage you to develop the three great virtues of a programmer: laziness, impatience, and hubris." -- Larry Wall, Programming Perl (1st edition)

Laziness

The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer. Also hence, this book. See also impatience and hubris.

Impatience

The anger you feel when the computer is being lazy. This makes you write programs that don't just react to your needs, but actually anticipate them. Or at least pretend to. Hence, the second great virtue of a programmer. See also laziness and hubris.

Hubris

Excessive pride, the sort of thing Zeus zaps you for. Also the quality that makes you write (and maintain) programs that other people won't want to say bad things about. Hence, the third great virtue of a programmer. See also laziness and impatience.

Chaos reigns within.
Reflect, repent, and reboot.
Order shall return.

source: http://www.gnu.org/fun/jokes/error-haiku.html