Saturday, January 31, 2015

Unusual Alerts from Twitter

tl;dr: I made for your (and my) enjoyment.

I wasn't the first to mock up imaginary push notifications from Twitter, and I regret that I don't even remember from whom it was that I stole my first base layer (including the "May 2B" typo)

I got hooked on this idea, though, and did a few over the last year. Some of my favorites:

What started off as a manual generation process eventually ended up with a fairly low-effort Pixelmator template… but then other folks wanted to make them easily too. So I made an online generator and put it at

The thing took about 30 minutes to put together, I guess, including setting up the domain and hosting. The most obvious nice-to-have would be the ability to save and/or tweet the image directly… but that would've taken more time than I had to invest in a toy like this. On a Mac, ⌃⇧⌘3 copies a selection of the screen to the clipboard, and you can paste it right into Twitter for Mac.

For me it's nice having the time fixed at 9:32, as a kind of signature of this thing; it's not intended to be a generator of forensically sound fakes. And even though it's primitive it's been gratifying to see the fun others have had with it. @samir is a master

@CaseyNewton got started recently with a winner
and @jazzychad weighed in recently on my leaving Twitter

Friday, October 31, 2014

Chrome and Emoji

Simple question:

It's a well known limitation but the reason for it is, surprisingly, not common knowledge. Maybe it's a licensing issue?
Maybe a strategy tax?
Maybe something darker?

When you think about it, Chrome would need to render Emoji one of two ways: either (a) bundle a set of Emoji with the browser; or (b) use the system set. It's likely true that licensing constraints make (a) difficult. But what about (b)? Apple introduced Emoji to OS X with 10.7 Lion in Summer 2011. Why can't Chrome just render those?

The answer lies in a Chromium bug report from 2010, in which we discover that Apple's Emoji live in a 32-bit (RGBA) bitmapped font… and Chrome's graphics engine doesn't support such things.

A recent comment on the issue from a Chromium developer notes "The priority over the last year has been DirectWrite and Android, but I'll be getting to this soon".

UPDATE 12/15/2014: the fix is in, and should be arriving in Chrome soon.

Saturday, August 23, 2014

In which I get started with a quadcopter drone

It started with this:

and then this:
and my attention was grabbed.

It was @stammy's seminal write-up on the subject of drone photography, though, which pushed me fully over the edge—and I had to get one. And here's what our new Boulder hood looks like from a drone:

Boulder from a drone
and in motion:

To do this stuff, here's what you'll need:

  • a drone
  • a gimbal (think of this as a stabilizing camera mount)
  • a camera
You can build this all yourself, of course, and many do, but I took the easy way out and bought finished items: as well as a 64Gb microSDXC card for the camera and propeller guards for the drone (you'll want these).

What you have now is an amazing flying machine with a camera. Here's what you need to know:

  • is it hard to fly?
    Surprisingly not. This thing has a built in GPS, compass, gyroscope, inertial sensors, and a sophisticated flight computer which measures these inputs (along with the inputs from the control transmitter) and can quite capably keep itself hovering in place in a 20mph wind.
  • what's the range?
    Radio range is around 3,000 feet radially. You probably want to check your local FAA regulations if you want to fly more than 400 feet above ground level, though.
  • can I see what the drone's seeing?
    Not with this equipment. To do that you'd need to upgrade with parts for "FPV"; it's covered in @stammy's post.
  • how long does the battery last?
    About 25 minutes' flying time. You can buy extra batteries for about $130 each.
  • can I control the camera while flying?
    The gimbal will keep the camera perfectly level with respect to the horizon. Remotely you'll be able to control whether it faces directly forward or straight down, or any point in between.
  • so how can I trigger photos?
    With this equipment you can't; you'll set the GoPro to record before the drone takes off, and it'll do its thing. I use a mode where it takes 1080p video continuously and grabs a high-res photo every five seconds. When the thing lands you can review what it's captured.

Some things which have surprised me:

  • the ease of flying; seriously, the flight computer does most of the work
  • the effectiveness of the gimbal; it's just unreal how smooth the video is, even flying choppily
  • the noise; i can see why people get annoyed by these things flying nearby or overhead. Be considerate!

Number one top tip: don't descend too fast. Vortex ring state, where your drone becomes engulfed in its own downwash, is real—and you will plummet out of the sky like a stone. The worst crashes I've had have been a result of this.


Thursday, August 14, 2014

Moving to Boulder, epilogue

On the fifth day of our trip we drove 42 miles in a perfectly straight line.

It made me wonder about the longest perfectly straight section of road in the US; where it would be and how long. I asked on Twitter, and so far nobody's come up with anything longer than this:

If you know of anything longer, holler.

Wednesday, August 13, 2014

Moving to Boulder, day 9

15 July 2014: early start in Glenwood Springs; Wendy and I had decided that the best strategy to conclude our journey to Boulder was to carry sleeping kids to the car at the crack of dawn and get going—maybe breakfast in Vail as we traveled down from the mountains.

And so it was, at maybe 6.30am in the hotel parking lot, sleepy and not concentrating, on the very last day of our trip, I lifted the U-Haul trailer to hitch it to the car… and completely fucked my back up.

Onward, though. I cranked the heated car seat to maximum, sweet relief!, and all other parts of the plan went great: calm kids, no traffic, easy trip down to Boulder. We arrived about lunchtime, and here's the overgrown garden:

The garden which greeted us
Here's Wendy outside the new place:
Arrival at the new house
Here's Lux, still in her PJs, enjoying the garden:
Arrival at the new house
Here's Cecilia, also in pajamas, clutching a find from the playhouse:
Arrival at the new house
and here's everyone munching raspberries from the bush in the back yard
Arrival at the new house

We had lunch, and I went to work at @TwitterBoulder—for the first time as a Colorado resident.

A month on my back is still a mess, but it's great here.

Arrival at the new house

Tuesday, August 12, 2014

Moving to Boulder, day 8

14 July 2014: we woke up in Glenwood Springs, CO, voted in 2011 the "Most Fun Town in America" by Rand McNally and USA Today. It's perfectly nice but in my limited experience I'd say that designation probably goes too far. Our hotel was also overrated; "Feel The Wonder" says its homepage, whereas all we really felt was cramped in a tiny room and frustrated with elevators which didn't work properly.

Onwards nonetheless. We headed out for breakfast and to buy hats and sunglasses for the kids. Lux's choice:

Buying sunglasses
and Cecilia's:
Buying sunglasses
I got sunglasses too; I lived in San Francisco nine years without feeling the need, but within a day of arriving in Colorado knew I couldn't last without any.

We took the cable car up the mountain; Lux was unsure at first

Unsure about the cable car
but quickly got into the spirit. The view from the top was pretty lovely
Glenwood Springs, Colorado
and the 15° drop in temperature was very welcome.

That night we went out for our final road trip dinner. After a week on the road the kids were clearly on their last legs.

Tired kids

Tomorrow we'd arrive in Boulder.

Sunday, August 10, 2014

Moving to Boulder, day 7

13 July 2014: we woke up in Moab and it was hot. And not just "gosh isn't it warm outside" hot, but "oh look parts of the car are shutting down" hot:

Well played Moab
We figured we'd splash in the pool for the morning, grab some lunch and then get out (here's Lux at lunch having arranged the sugar packets just perfectly):
Perfect arrangement

Our next stop was Glenwood Springs, but we had a brief pause for dessert in Grand Junction. Wendy with the ice cream sandwich:

Dessert break in Grand Junction
Lux with a popsicle:
Dessert break in Grand Junction
and Cecilia too:
Dessert break in Grand Junction

It's a spectacular drive into Colorado, and my phone doesn't do it justice… but it's all I have:

Coming in to Glenwood Springs

We arrive in Glenwood Springs and checked into our hotel. Cecilia found God in the top drawer

Cecilia discovers The Word
and we all went swimming.

Tomorrow would be the last full day of our road trip.

Saturday, August 09, 2014

Moving to Boulder, day 6

12 July 2014: we woke up in an Airbnb in Mapleton, UT. This seemingly unassuming place, under $150 for the night, turned out to be our most lavish accommodation of the entire journey. You read "basement apartment" and you don't necessarily think of a lush 3,000sqft palace underneath a 10,000sqft house, with a 70" plasma TV and a fitness room. And yet here we were.

It was also filled with kids stuff, and had a trampoline on the ample grounds, so we figured we'd stick around for a while in the morning. Let's make a pot of coff… oh, wait.


Nothing in the cupboards, and even driving around the area we couldn't find anywhere which sold coffee. Wendy and I looked at each other, held hands, and tried not to panic. We left around lunchtime.

By late afternoon we were in Moab, UT. Our hotel had a pool, so we did some more splashing when we arrived; it's seriously *amazing* what endless joy and fascination the kids find in water. In the evening we went to a cliff-top place to watch the sunset. It did not disappoint.

Sunset in Moab

Tomorrow we'd cross the border into Colorado.

Friday, August 08, 2014

Moving to Boulder, day 5

11 July 2014: we wake up in Elko, NV, with a target of Mapleton, UT. That's 280 miles, with 42 of them in a perfectly straight line. The kids both love swimming right now, and the hotel in Elko has a pool, so the first thing we do after a hotel breakfast is splash about for an hour or so.

After that it's on the road, and more of the same:

Nevada plains
and then
Utah salt flats
and then
Utah desert

After miles and miles of this we decide to stop at a park in Salt Lake City on our way through—to let the kids run around and let off some steam. Liberty Park turned out to be perfect for this, and we ended up staying a couple of hours enjoying the late sunshine:

Arrived in Salt Lake City
At Wendy's request we then drove just a few blocks to the Old Spaghetti Factory, a staple of family road trips from her own childhood.

With our dawdling—and a critical closed road on the way to Mapleton—we ended up not arriving at our Airbnb until 11pm. We also didn't yet fully appreciate what being in suburban Utah meant.

Thursday, August 07, 2014

Moving to Boulder, day 4

10 July 2014: Thursday morning we wake up in Tahoe City, CA, with our next night's lodging in Elko, NV. That's a 350 mile journey: in England terms Southampton to Newcastle; basically most of the length of the country. I've been in the States over ten years now so UK comparisons are mostly moot, but for me growing up this was an inconceivable distance for a day's drive—you'd get the train if anything, probably.

While we're on these comparisons, though, it's worth noting that Elko—a town of fewer than 50,000 people—is the largest town for 130 miles in any direction. There isn't a single town like that in England. It's on drives like this when the vast scale of the US (again, relative to where I grew up) becomes most apparent.

Roads like this:

On the road in Nevada
and this:
Your Ad Here, in the middle of nowhere
and this:
go on and on and on (the video covers ~16 miles).

In the UK or the US or probably anywhere else in the world, 350 miles is a long drive relative to the patience of a 2-year-old and a 4-year-old. The kids were pretty fed up by the time we got to Elko, but enjoyed reading Frederick on the iPad at bedtime:

and sharing a bed in the hotel
Sharing a hotel bed
(in fact so much that we ended up having to separate them).

Tomorrow, onwards from Nevada into Utah.

Wednesday, August 06, 2014

Moving to Boulder, day 3

9 July 2014: it's nice to wake up in Tahoe. We went for breakfast in Tahoe City, with a lovely view of the lake

Lovely day in Tahoe City
Lake Tahoe

After breakfast we grabbed towels from the house and went to the beach for a while.

(Not) skipping rocks
Cecilia at the lake

Wendy stayed mostly dry but Lux, Cecilia and I all went swimming. "Bracing" is directionally correct but really doesn't even come close to describing the temperature of the water. We dried off in the sunshine on a wooden jetty.

We had a quiet dinner that evening, in the back yard of our place. Hungry Cecilia:

Hungry Cecilia
Happy Lux:
Hungry Lux

Tomorrow we'll be leaving California.

Tuesday, August 05, 2014

Moving to Boulder, day 2

8 July 2014: Wendy and Cecilia wake up in Colorado. Lux and I wake up in California for her last day at pre-school. Here she is waiting to be picked up to be taken there by a friend

Last day of school

The conversation in the car on the way to pre-school, from what I'm told:

Tessa (Lux's best friend): this is our last day together we should hold hands the whole way, I love you
Lux: I love you too Tessa
It breaks your heart.

Later, picking Lux up from school, there were fond goodbyes with favorite teachers:

Goodbye Mary

By 5pm the truck's filling up

Now it's real
By 7pm we're headed out of town:
Goodbye San Francisco
Goodbye San Francisco

We grab dinner in Emeryville and arrive in Tahoe City a little before midnight. The Airbnb we're staying at has a dog barking machine; it scares the crap out of me.


Monday, August 04, 2014

Moving to Boulder, day 1

7 July 2014: Before we know it: first thing, early, Wendy's flying to Colorado with Cecilia and Chaucer. Lux and I took them to the airport, Chaucer crying in his carrier the whole way.

Back from SFO I take Lux to school and await the movers:

This one dude arrives and starts putting things in boxes kind of desultorily. Helpers are arriving soon, I'm told, and I make myself scarce.

By the end of the day we've got a smattering of boxes

And so it begins with the boxes
and a relaxed Lux
Lux is chill
but wow there's a lot still to go.

Sunday, August 03, 2014

Moving to Boulder

Things moved quickly after that date night at the top of Bernal:

And so the move began.

Saturday, August 02, 2014

Date Night

Wendy and I moved from Denver to San Francisco in 2005. Unmarried, childless, we found a little place for rent in the Mission, rented it and moved in.

In 2006 I started working for Google. In 2007 Wendy and I got married. In 2008 we took our honeymoon. In 2009 we got pregnant. In 2010 I started working for Twitter and we welcomed Lux. In 2011 we bought our first home, and in 2012 we had another kid.

We instituted weekly date night in 2012 too.

Each week we'd usually meet at Blondie's after work, and after a drink or two go either to a movie or to dinner. 2 April 2014 was different, though: after the bar we grabbed a slice of pizza across the street, some dodgy liquor from a corner store, and headed up to the top of Bernal hill:

On a beautiful evening, overlooking our beautiful city, I said to Wendy: "you know what we should do? We should move to Boulder".

Saturday, April 19, 2014

Dropbox and Google Drive

UPDATED 4/21: update below from Scott Johnston, Product lead for Google Drive.

I figured it was time to move from Dropbox to Google Drive. On the face of it, it's deceptively easy

I have a little over 100Gb sync'd with Dropbox across three Macs. I figured it'd be a simple matter of

  1. ensure all three machines are fully sync'd with Dropbox
  2. quit the Dropbox app on each
  3. on Mac #1, copy the Dropbox folder to the Google Drive folder
  4. on Mac #1, fire up the Google Drive client, and sync (ie. upload the 100Gb)
  5. on Mac #2, copy the Dropbox folder to the Google Drive folder
  6. on Mac #2, fire up the Google Drive client, and sync (which should be a no-op)
and then the same for Mac #3.

Everything was looking good to begin with. Even step 4, which some had said would be troublesome, worked just fine in practice—speedy upload, no problem. The real surprise was step 6:

because Google Drive was downloading an entire duplicate copy of everything, not noticing that I already had a complete copy in the local folder already.

Obviously this is fucked up. It's also, apparently, a known issue. And while I can probably live with the lack of LAN Sync, and the general unpolishedness of the Google Drive client, basic functional brokenness like this is a deal-breaker.

From a number of people I've heard great things about the Insync client for Google Drive—including its support for multiple Google Accounts. For now, though, I'm heading back to Dropbox.

UPDATE: To my surprise the Google Drive Product lead tweeted an acknowledgment of the issue. Sounds like a fix is in the works.

Monday, December 30, 2013

Disabling Wi-Fi on a Comcast Xfinity Cable Modem

Judging by traffic and comments, my last technical "how-to" post was a moderate success, and was found by folks Googling for the solution—so I'm back with another quickie.

A few months ago Comcast sent me an Arris TG862G cable modem, an upgrade from the previous Motorola device to enable higher speed internet access. On the upside it did the job more than handsomely:

On the downside it insisted on being a firewall, DHCP server, and Wi-Fi access point—when I already have something I'm perfectly happy with for those functions. And while some aspects could be tweaked via the admin console, the Wi-Fi couldn't be disabled.

I wanted it disabled.

So if, like me, you want to disable Wi-Fi on your Xfinity Arris TG862G cable modem (how about that for SEO), here's what you need to know: just call Comcast and ask them to put your device into "bridge mode". I did, it was painless, it took them a minute or two, and the box became exactly what I wanted: a transparent bridge between co-ax cable and my Asus router. The N16 now has a the public IP and does its job as firewall, Wi-Fi access point, ssh tunnel endpoint, DHCP server, and so on.


Saturday, November 23, 2013

Working at Twitter

I find myself interviewing a lot of people for positions at Twitter. In my time here I've been on panels for Product Management, Business Development, Engineering, Product Counsel, Country Director, Brand Strategy, Data Scientist, Corporate Counsel, Media Partner Manager, Business Operations, Program Management, Corporate Development, Marketing & Communications, Procurement, Finance, Product Specialist, and likely a few others—I've interviewed hundreds of people in all.

Most of these interviews are 30 minutes. I try to leave five minutes at the end of each for a candidate to ask me questions, and the one I most often get is "what do you most like about working here?".

The answer I give comes in two parts.

This is the big thing for me even though it's not even Twitter, Inc., which makes the ultimate product—it's Twitter users who make Twitter the experience so educational, addictive, moving, thought-provoking, hilarious, informative, and entertaining. To be a part of the team which enables something so amazing, though, is a tremendous source of joy and pride.

But there's also this:

It was February this year that Twitter acquired Bluefin Labs. A few months later I was talking to Deb Roy, one of its founders, and as a new Twitter employee at the time he shared with me the observation that “credit flows very freely at Twitter”, with the result that the organization is less political than most.

That resonated with me, and I've thought a lot about it.

It's not that Twitter, Inc., is devoid of internal politics but it is the case that—in my experience at least—it's a uniquely collaborative environment where credit is shared willingly, genuinely, sincerely, and amazing things are accomplished as a direct consequence. It's refreshing and energizing to work at a place with such a unified sense of purpose and, for the most part, lack of ego.


If the above sounds appealing, join us! As of today, there are 260 open positions at Twitter worldwide.

Thursday, July 18, 2013

Twitter Hackweek, July 2013

I'm pretty proud of this, which I produced during Twitter's most recent hackweek:

It's a map of verified users of Twitter. The layout is calculated according to the mutual follow graph connecting these users, ie. relationships where @x follows @y and @y follows @x. The coloring is determined by user category (eg. sport, music, etc).

The Twitter Media blog post has some good information about how to think about the visual and what we can deduce from it; what follow here are the gory details behind how it was built—for data visualization dilettantes and cargo-culters like myself.

What on earth

First of all: what exactly is this thing? In technical terms it's a force-directed layout of the largest connected component of the verified user mutual follow graph. That single large connected component happens to contain over 99% of verified users; a handful are off on islands of their own, not connected to this clown hairball by mutual follows, and they're not shown.

How it came to be

Here's how it looked at the beginning of hackweek; this is a first quick pass at the force-directed layout of a random sample of verified users:

(More detail below on the tools that I used to make this image but for those already wondering, the hard work was done by Graphviz, specifically sfdp and neato)

This was looking promising (and attractive in its own way, I thought) but as I added more and more users it just became a big dense white blob with no apparent structure. I figured I'd have a go at coloring the nodes by user category (sports, music, news, and so on) to see if some structure would reveal.

I started off by just highlighting TV-related accounts, which you can see in this graph of a 10% sample:

Verified user mutual follow graph, early cut
and this showed enough promise to add colors for other high-level categories.

I liked the way colors clustered together, but now my diagram was looking a bit drab:

Verified user mutual follow graph, early cut
The density of the gray edges was just sucking the saturation out—and their uniformity was obscuring further structure, I figured.

So I colored the edges: any edge connecting two nodes of the same color would be colored accordingly: a yellow line to connect two sports people following each other; a red line to connect two musicians following each other; and so on.

Now the clusters were really clear. I liked this a lot, and I rendered a really large version:

The result is what you see in the Twitter Media blog post. Not quite a gigapixel, but near enough.

The generation process in detail

Obviously, the process starts by capturing the follow relationships between verified users on Twitter. You can do this yourself easily enough using the Twitter API:

  • find verified users by looking at who @verified follows;
  • for each, find who they follow;
  • filter this dataset down to mutual follows.
A good place to end up is with a tab-separated file of two columns, of users who follow each other:
screen_name_1 [tab] screen_name_2
screen_name_1 [tab] screen_name_3
screen_name_4 [tab] screen_name_5
to the tune of a few million lines.

Once you have this you can use your favorite awk or perl or bash one-liners to turn this into a bare graph in DOT format:

digraph my_graph {
    screen_name_1 -> screen_name_2
    screen_name_1 -> screen_name_3
    screen_name_4 -> screen_name_5

At this point I used Graphviz's comps utility to extract the largest connected component of the graph:

cat graph.gv | ccomps -zX#0 > graph-cc0.gv

Now we have the core data of interest in graph-cc0.gv and we can iterate on the following:

  1. layout: I used sfdp to produce a force-directed layout of the graph;
  2. coloring: I wrote a handful of lines of Python to color the laid-out graph according to the category of user;
  3. rasterization: I used neato to render the graph to a PNG.
  4. presentation: I uploaded to to share the result.

I used a MacBook Air to do this work. Step (1) typically took a few minutes, (2) was 20 seconds or so; (3) was 10–120 minutes depending on the output size; (4) was actually the slowest step—a few days to process and present the final version. The graphviz tools are single-threaded and tend to be CPU-bound; you can get some wins with better hardware on (3), but only very modest ones.

Here's how it all adds up into a single script:

Saturday, March 09, 2013

Zero-Width Space

Since Buzzfeed picked up my post about stealth fanout on Twitter a few people have asked me how one can best produce a "zero-width space" on a Mac.

Here's how you do it.

On a Mac, pretty much any time you're typing text (including when you're composing a Tweet) you can hit ⌥⌘T to bring up the "Special Characters" window, and from here you can find (and use) pretty much any Unicode character out there. Try typing "zero width space" into the search field:

Image 2013 03 06 4 06 09 PM
and you'll find the elusive character… by definition it's kinda invisible. But you can add it to your favorite Special Characters, insert it into what you're typing directly from here, or copy it to the clipboard.

If you want to make it super-easy to use a zero-width space you can create a global text shortcut in the "Language and Text" area of the Mac's System Preferences. Here below I'm setting things up so that every time I type "zws" a zero-width space is inserted:

Image 2013 03 06 4 08 40 PM

Tuesday, March 05, 2013


My dad has heart failure. My mom has opinions on the matter.

A few weeks ago my dad posted one of the most beautiful and moving pieces I've ever read, about his own father.

My head spins, my heart trembles.

Friday, March 01, 2013

Stealth Fanout on Twitter

Sure, on Twitter you can use the ".@" convention to start a Tweet with a username but still have it delivered to all your followers. Like this:

Turns out, though, that instead of a "." you can use a zero-width space. It has the same effect—your Tweet is delivered to all of your followers—but the leading character is by its nature invisible:

A side effect which you may or may not enjoy is people's surprise:

Wednesday, February 13, 2013


I was on the lookout for something special for Wendy's birthday. And then Josh tweeted

Josh went to high school with Alessandra, now a freelance illustrator in Brooklyn. Alessandra, it turns out, does some truly delightful drawings. I thought I'd get in touch.

Based on a set of photos I sent over, Alessandra drew this picture of me, Wendy, Lux and Cecilia:

Wendy's Birthday Gift
and I'm thrilled by it (Wendy was too). It's framed on our wall and it makes me smile.

Thursday, January 10, 2013

Working at Twitter

I did a little Q&A recently about what it's like working at Twitter. They published the piece this week but included only my answers, not the questions, which makes it read a little incoherently. I thought I'd put the Qs as well as the As here for the record.

If you could describe the essence of Twitter's culture in one word, what would that be? Explain.
Open. We're open in the sense that we have transparent internal communication and discussion. Open in the sense that the platform is open to all: from everyday individuals to news organizations to governments to entertainers and so on. Open in the sense that people at Twitter are always open to new ideas and perspectives. Open in the sense that Twitter employees Tweet freely and fearlessly about their lives and opinions.

Describe your favorite part of the office/campus.
The roof deck at Twitter is very special. It reminds us all that we're in the middle of a wonderful and vibrant city. Provides views of Twin Peaks and—often—the sunset.

How would you describe the best day you ever had at Twitter? What made it so great?
I've thought a lot about this. At Twitter I feel incredibly privileged to work at a company which makes a product that I so deeply love. I'm besotted with the thing which is Twitter, and that makes every day here special. If I had to choose one in particular, it'd be meeting Barack Obama at the White House while organizing the first ever presidential Twitter Q&A in 2011.

Describe your workspace—what does your immediate (desk) and/or surrounding work area look like? Have you done anything to customize it?
It's pretty minimalist. A laptop stand and 27" Dell monitor, wireless keyboard, wireless mouse. I've been at Twitter coming up for three years and have had 13 different desks since I've been here. I travel light.

My desk at Twitter

How would you describe the quintessential Twitter employee?
Passionate; humble; smart.

Describe one unique/goofy/crazy/weird/quirky thing your team does for a little fun.
The work in the Twitter Media team is unique and crazy enough on its own! Every week team members are meeting and hosting visits from heads of state, world-famous athletes, mega-star musicians, religious leaders, award-winning journalists, best-selling authors and media companies. We work with them to help them use Twitter ever more effectively to connect with their fans and followers, and to create unique interactive experiences on and off the platform.

If there was one thing you could describe to an outsider to make them feel like a Twitter insider, what would that be?
There's an incredible unity of purpose here at Twitter: every Twitter employee works here because they want to make Twitter the best it can be. From making the site faster to improving search algorithms, from testing new features with users to making sure our office feels like home, everyone is working passionately toward a common goal, eagerly looking toward the future and constantly amazed by the creativity of our users.

CES 2013

I went to the Consumer Electronics Show in Las Vegas once. I flew in for a single meeting, in January 2006, and remember that after that I spent over an hour waiting in a line for a cab back to the airport. In the end a dozen people in the cab line pooled resources and rented a stretch limo to the airport between us.

In 2013 I went to CES only in my imagination and on Twitter: