Annoyed by “The Peripheral”

November 11th, 2014

I enjoyed reading William Gibson’s latest, as I’ve enjoyed reading nearly everything he’s written, and as I anticipate enjoying seeing him and James Gleick speak tomorrow night.

However as I finished “The Peripheral” the overwhelming sensation I was left with was annoyed.

Below are spoilers.

There were a number of moments that bothered me, but in 3 quick bullets.

  1. The literature didn’t need another implacably evil bearded Arab villain. Even is he is half Swiss.

  2. The literature didn’t need another heroine whose happily-ever-after is signified by getting pregnant.

  3. It goes against everything I look for in a Gibson novel to basely indulge a maybe-the-future-will-take-pity-on-us-and-save-us fantasy. It left me with the sensation that the author is deeply scared, which while reasonable, isn’t what I expect from the typewriting steely eyed prophet of the future.

Lots of good moments, and interesting world building, again the near future work, especially the near future rural poverty in a cheap printing/fabbing future was interesting.

Tagged: Uncategorized

Pumpkin Pudding

October 26th, 2014

Back when my dad drove his big yellow truck, delivering food for the food bank, he sometimes dropped me off at the Live Oak Senior Center industrial kitchen.

And every October I remember peering over the edge into the bowl of an industrial stand mixer taller then I was at a truly giant vat of pumpkin pudding.

And while I’m telling myself this pumpkin flavored Chobani yogurt is kind of a pumpkin pudding, it really isn’t.

Tagged: Uncategorized

“Wolf” narrative considered harmful (also biologically unlikely)

September 2nd, 2014

Rands’ “The Wolf” post floated across my Twitters this morning. My immediate reaction was that it was misguided to the point of being potentially harmful. That was 16 long hours ago, but I’m going to see if I can pull the strands of that thought back together.

Michael mentions he’s had the fortune to work with several “wolves” in his career. I’ve worked with a bunch, including teams compromised of nothing but (I guess you’d call that a “pack”). The problem is the post plays into the fantastical narrative of the lone wolf. But here is the secret. No one is a lone wolf. Or at least not completely. “Wolf” is the story that many people want told about them, and that on good days they tell themselves, but in the dark of the soul, we all need help and have doubts. By celebrating the narrative construct rather then reality you perpetuate the dangerous tendency towards isolation that is inherent in this archetype. I’m playing the long game, and in my perspective sooner or later one of two things is going to happen to your isolated “wolf”: either they’re going to run into a hard enough problem that they’re going to need more help then they know how to ask for, or in their bid to maintain their Harvey Keitel-like facade they’ll eventually isolate themselves from new challenges and dead end their usefulness.

So let’s pull back the curtain a bit and understand the archetype:

  • they’re passionate about solving hard problems, and generally they have a few favorite problems they like to gnaw on. That deep personal investment in the solution is what pushed them to develop their skills past the point of their peers in the first place, and also where they find the personal clarity they need to opt out of the clarifying bureaucratic structure of the larger org. With that passion can come narrowness, often expressed as hyper rationality. Pro move: keep supplying hard problems off center of their primary focus.

  • they’ve developed a toolkit. A preferred language, set of scripts, investigative processes, checklist, whatever. And they come back to it over and over again. That disproportionate impact they have, it isn’t magic, its craftsmanship. They’ve mastered their tools to the point where the tools are an extension of their hands. They might see everything as a problem to be solved in Lisp, or via experimentation or machine learning or wireshark. They might have written their own text editor that lacks features what you and I consider non-negotiable, but doesn’t seem to impair their progress. The best of these folks literally generate tools, turning their own idiosyncratic but highly effective approach into tools that the wider org can use. Pro move: create a space and a culture that celebrates investing in tools. Everyone should hone their craft, and a few great tool builders makes everyone if not a 10x programmer, maybe an 8.5x.

  • they’re convinced they’re right. Or at least, they’re convinced often enough that they’re right that they appear convinced all the time. A banal outcome of this is hill climbing. The toxic outcome is stagnation with a hugely talented individual stuck because they don’t know how not to be right. You owe your high impact individuals to surround them with people who challenge them. If they’re really a “wolf” they’re likely to try to wriggle out of this. Pro move: they care about impact, so make the road to impact littered with smart challenging people.

  • the “well defined IC track for non-managers” is probably the project I’ve found most elusive and difficult to execute on. Rands gave me my first key insight into it late one night after much tequila: you have to make sure the role comes with super powers. Management comes with super powers by default, you have a team to force multiply you, and by convention, most corporations share information with managers at a greater rate then ICs. I haven’t found a one-size fits all approach to super powers, but a thing we’ve done is make sure that while the “senior eng org” (super powered engineers) have their own discussion space, they can also ease drop on manager discussions if they so choose.

If you’ve been maneuvered into calling someone “a wolf”, then I hypothesize you’ve let someone who could be transformational to your organization off the hook too easily. Imagine instead of a wolf you had a Intrinsically Motivated Full Stack Product Hacker.

Tagged: Uncategorized

AWS Redshift: “Missing newline: Unexpected character 0x4f found at location 3″

July 21st, 2014

I was trying to bulk load some data into Redshift this weekend using the copy command and I got this error message that no amount of Googling turned up a hit for. It was particularly strange given the hex value specified was for that exotic character the capital-O (as is OMG).

stl_load_errors listed the offending raw_line as being “.LZO”.

Anyway, this particular error message is documented here for the next person who forgets to toss lzop on to end of their copy command and tries to Google it

to be explicit you’ve got:

copy some_table from 's3://some_bucket/data.lzo' CREDENTIALS 'some_credentials' delimiter '\s' timeformat 'auto';

and you need

copy some_table from 's3://some_bucket/data.lzo' CREDENTIALS 'some_credentials' delimiter '\s' timeformat 'auto' lzop;

Tagged: Uncategorized

Communication Skills

May 17th, 2014

A great deal of negativity has been directed lately at the practice of hiring for culture fit. I find this troubling because its a central tenet of Etsy’s hiring. This pithy insight was shared with me yesterday by one of our senior most engineers, and I slept better last night.

“As time passes, I focus more and more on interviewing for communication skills over technical skills.

Even the most brilliant engineer can get off course. But a great communicator might move slower, but they will always be moving in the right direction.”

(actually I didn’t sleep better last night, but that was the baby’s fault, not anxiety about contributing to oppression.)

Tagged: Uncategorized

Shell trick for the perpetually distracted

May 12th, 2014

Manager time is the schedule that sub-divides your day into 15 minute blocks. It’s the internal clock in your head that knows when you’ve reached the end of a 30 minute meeting without checking the clock. It’s a trained form of ADHD, and it’s the opposite of maker time.

One of the things I find I need in manager time is a quick way to regain my context. I’m way behind on adopting a proper getting things done framework, but it wouldn’t help with this one thing I wanted to post about today anyway.

I keep two copies of most of the Etsy code base locally. The one I use constantly, which is for quick reference when a technical question comes up, and the one I use almost never which is where my various half hearted attempts to compress a quick hack into a 15 minute block live.

git gives me the tools to make it very painful when I get confused about which directory I’m in.

So in prep for hoping to finish up a quick hack during hack week (didn’t happen) I shaved a small attention starved yak. Namely changing the color of my terminal when I’m in workspace, which is the hacking directory. It’s a parallel to prompt hacks I’ve had for years that change based on host, but it uses osascript (command line AppleScript) for simplicity in scripting Terminal.app

set_bg () {
  osascript -e "tell application \"Terminal\" to set current settings of window 1 to settings set \"$1\""
}

function cd {
  old_wd=$(pwd)
  builtin cd "$@"
  pwd=$(pwd)
  if [[ "$pwd/" =~ /workspace/ ]] ; then
    set_bg "Red Sands"
  elif [[ "$old_wd/" =~ /workspace/ ]] ; then
    set_bg "Basic"
  fi
}

Override cd, if we entering workspace, use the profile “Red Sands”, if we’re leaving workspace switch basic to “Basic”.

Tagged: Uncategorized

Explaining to the phone how to be a CTO

December 5th, 2013

The other morning I was sitting stuck in traffic … which an odd experience in New York, but for a few reasons I’ve actually been driving to work lately, profoundly surreal as a New Yorker, and not recommended.

Back to the story.

I was sitting stuck in traffic, and the last thing I’d seen before being stuck in traffic was the question, “How do I learn enough to become a good CTO?”

So below is the first blog post I ever tried to write via Siri. I thought about leaving in all the misidentified words, but the point wasn’t comedy. It still came out quite brief and almost certainly incomplete and incoherent:

It’s a leadership role, which means you need to develop a theory of leadership. It’s a spiritual role which means you need to be able to speak and write. It’s a role that fundamentally trades on credibility, so having been part of a team that did something that actually worked is key both for the reflected credibility but also because it’s important to have the certainty about what something working feels like.

It’s a role we learn by trial and error so you need to find a trusted community to compare notes with. You need to develop an empathy for the customer and interest in the business so whatever interdisciplinary pursuits do that for you is part of your training.

Finally being right more often then you’re wrong helps, but is less critical then you’d imagine.

It isn’t the 1st engineer either literally or metaphorically though that person is sometimes called the CTO. It isn’t the engineering manager in chief, though often you end up doing that job as well (but that’s a VPofE).

Software development scales non-linearly with clarity and excitement so your job is removing unnecessary ambiguity and drag. holding the narrative of what engineering means at YourCompany.

That’s how you learn to be a CTO.

And now that I’m typing this in to a textbox here on web, I’ll add, get good at managing your psychology

Tagged: Uncategorized

Slow Twitter

November 17th, 2013

My brother tweeted recently, “making sure I have a working implementation of Logo is part of setting up the nursery, right?”. I feel the same way about building the just the right photo sharing site and Twitter client. But I’m RESISTING. And I’m very proud of myself for it.

The Twitter client I want (and have wanted for years, but I want it more now) is at least fairly straightforward, and I’m hoping someone has either already built it or will get inspired. I think of it as “Slow Twitter”.

Twitter works great when you’re constantly checking it. Or when you don’t follow that many folks. But once you’re distracted you start missing stuff. In fact you only see the people who tweet constantly. And they’re often the most banal.

What I’m looking for is an app (and I include websites in that word, I’m old fashioned) that shows me who has tweeted since I lasted accessed it, with access to what they’ve tweeted, sorted in reverse order of the likelihood that they would have tweeted during the period of elapsed time aka probably sorted by ascending rolling average tweet frequency.

Anyone?

Tagged: Uncategorized

5 Approaches to Handling Bugs We Tried Before Our Current Approach

November 1st, 2013
  • don’t write bugs
  • once you write a piece of code you own it forever and your top priority is fixing the bugs in it
  • assign teams to own every section of the site, allow them to make sure no unapproved changes happen to those areas
  • have a bug fixing team
  • delete all code over a year old, switch to a new language, rewrite it
Tagged: Uncategorized

A quick knot in a few Flickr threads

October 19th, 2013

Paul Mison’s Maximum Viable Product feels like a more clever (if more cheeky) way to get at what I was trying to say with my notes on Flourishes and Minimal Competence (and Competence found), and threads the needle of recent 4up from Aaron and The Flickr We Lost from Dan.

I don’t have much conclusion as much as a sense there’s a thing there that I’m still trying to get my hands around.

The other piece I wonder at about this is the role of sophisticated testing and measurements and being the user.

I hear that engagement is way up in the wake of Flickr’s changes, and I know I’ve been gone a long time and things have probably changed, but I can’t help but be struck how unsophisticated we were at measuring things at Flickr — in part because we were a tiny team, and in part because we relied on our instincts. It makes me wonder what’s guiding the current work.

Tagged: Uncategorized

Paths to Production Confidence, Part 1 of N

August 8th, 2013

This started out as a short note explaining the unifying theory behind the Etsy development practices. Then it got out of hand (see also, Mark Twain’s “If I had more time…”). As such I’ve made it “Part 1 of N”, where “Parts 2 .. N” will cover the actual practices and how they relate to the philosophy.

Why Write This?

We believe in being as open as possible about how we develop and run Etsy — our current best theories, learnings, practices, and tools. Given that openness I often get questions about the hows and whys of given subsets of our engineering practice, e.g. “How do you do testing? How do you know you have enough testing?”. Or monitoring or deployment or what not.

At times, it can be tricky to do the questions and answers justice when taking them piecemeal, because underlying them all is a single shared philosophical premise, that isn’t necessarily obvious. And while I tend to be a pragmatist, favoring the rough and ready over the theoretical, without understanding the theory you can’t reason correctly about trade offs. This post is an attempt to surface that underlying philosophy and the practices it informs.

The theory is a theory of change, and the philosophy is about finding paths to move from risk to confidence.

A Theory of Change

Etsy is in the change business. As are, definitionally, all startups, nearly all businesses, and most human projects. We’re attempting to add new capacities to the world, and influence behavior around them. And we’re attempting to do it in an uncertain and complex[1] environment; we neither know the exact recipe for success, nor we do expect that recipe to stay the same over time. In fact, as a startup, we believe that our ability to respond to a changing environment is the key success factor for our engineering organization. It’s natural to read that sentence and think of change in terms of product changes, but more prosaic examples might include the ability to add new server capacity when the site slows down, or to replace a hard drive when one fails.

But change is risky. This is something most of us believe intuitively, and it’s worth examining the sources of risk in change.

Why is change risky?

As humans and practitioners why do we associate change with risk? Doing new things inherently contains the risk of doing the wrong thing.

We may for example have reached a ready state in our project. Through a combination of good luck and planning we find ourselves running a system that we understand sufficiently to keep running indefinitely, while a change would implicitly contain the risk of moving from a state of working to a state of not working. Steady state systems are so rare and so often illusory, it’s almost not worth mentioning except we’re fervently entranced with the possibility. Generally the illusion of steady state simply means the needed changes are non-linear, and often the cost of ignoring them will be high.

More practically, very few of us are employed to maintain systems in a stable environment. Even if we hold the pieces we control constant it’s unlikely that our systems will remain stable forever, at which point action is required. Still change is often associated with surprise in a system that hadn’t previously surprised us, and surprise is definitely risky.

The second reason change is risky has to do with how we think about causality, intention and culpability. While we can agree that the ability to choose not to make a change is an illusion, often fear leads people to approximate avoiding change, by avoiding making choices. If I personally avoid making changes to a system and instead wait for outside pressure to force change, or if I simply play the odds and hope that disastrous failure happens rarely enough that it won’t happen on my watch then I can avoid the personal risk of being labelled the root cause of failure. Forced choices avoid the necessity of stating a hypothesis before acting, thereby reducing significantly the opportunity to be personally wrong.

Software development is a complex system existing as it does at the intersection of people, systems, good intentions, confused and changing goals, and overly literal state machines. Past behavior isn’t always an indication of future behavior, and humans are terrible at reasoning about complex systems. As such we’re unlikely to know or have good visibility into whether we’ve reached a steady state and our hypotheses are likely to be wrong. In this uncertain and complex environment we initiate change only when the cost of not making a change overcomes the fear of making it. (e.g. “The server is down” or “You’ll be fired if this feature isn’t done by April 1st”)

As an industry this means though we’re in the change business, often we aren’t very good at it, and we avoid it out of fear.

Different groups attempt to address this tension by:

  • raising the cost of not making change (“you’ll be fired”)
  • distributing those costs broadly (this is one of the key functions bureaucracy and process serve)
  • gaining confidence by addressing the fear

We see Etsy’s engineering practices as spectrum of tools for increasing our confidence in our ability to make change.

Going back to the opening idea of this post, the attempt to answer a question like, “How much testing do you do?”, the answer becomes, “Enough to gain confidence. But testing is just one of the tools we use to gain confidence, so less then a strong testing shop might.” Similarly if someone asks, “How much monitoring is enough?”, the answer is, “We add monitoring until we feel like it gives us confidence, and we’re comfortable striking an 80/20 balance, particularly upfront, because we’re confident if we don’t have the balance right we have other ways of finding out.” In fact how many and how much confidence boosting techniques you need is situational, and depends on how risky your change is. Which speaks to another fundamental piece of our process, small and iterative changes.

Hopefully that starts to explain why, while I think our testing infrastructure (with its try-servers, “Bobs”, static analysis, integration tests, and quality metrics) is awesome, just telling you how we do testing isn’t necessarily going to be useful. Or perhaps it just speaks to my personal penchant for holistic post-modern explanations.

So given a theory(-ish) of risk, change and confidence, what’s the philosophical premise we derive to underly our development practices:

To be able to consistently deliver the kind of resilient and ongoing change the business requires, we deploy a spectrum of confidence gaining techniques.

Or jokingly what we call, “Making failure cheap and easy.”

Before moving on it’s worth calling out that the goal is NOT to be careful. The goal is to be confident. Careful would imply we’re trying to avoid the risk which is fundamental to the change we’re trying to make. Attempting to avoid risk often leads to paralysis, favoring the short term risk avoidance while compromising long term goals. Instead confidence implies you believe to the best of your ability that you understand and have mitigated the risk involved in your change, and are now going to act.

Now, with a little shared theory and philosophy, what does that spectrum of confidence gaining techniques look like?

Our Paths to Confidence:

  • Small and Frequent (and Iterative)
  • Testing
  • Ramp Ups
  • Controls
  • Default Access to Open
  • Monitoring, Metrics and Anomaly Detection
  • People / Culture / Brains

Each of which I’ll talk about in subsequent future posts.



1. Complex systems as defined as something that has many diverse, interdependent, adaptive and connected parts points to the uncertainty. Small perturbations can produce large results, and those results could be failures or successes, but in either case: the potential for surprise is high.

Tagged: Uncategorized

Surviving being senior (tech) management

July 16th, 2013

I’ve got a short list of things I tell people they need to do to survive being senior management. This list has come up a bunch in the last week talking to different folks. So I’m writing it down so I don’t actually have to remember it. That’s sort of unfortunate because there are some alternate versions that exist in a super-positional state, but I think having it written down outweighs the flexibility.

I’m sure the list isn’t especially unique to being senior management but there are a few things that are unique to being senior management, that makes it particularly relevant:

  • it’s a job where your ability to cope with your demons is critical to the success of everyone who works for you. See also Ben Horowitz’s, “What’s The Most Difficult CEO Skill? Managing Your Own Psychology”

  • most people doing the work (at least in tech) are transitioning from maker to manager, and while a few special people are both good at management and enjoy it (and also a few sociopaths), most of us find it a really difficult transition to feel good about consistently and on an ongoing basis.

It’s a simple list. It shouldn’t surprise. This is the minimum. This is my list from having done the job, managed folks doing the job, hired, promoted, and fired folks doing the job, and perhaps most importantly drank with folks doing the job. Your mileage may vary. (But I’d be kind of surprised.)

1. Get some exercise

The ways most of us cope with stress are toxic. They lead to sickness, injury, and reduced cognitive clarity and elasticity. Small amounts of regular exercise help. This is not about getting in shape, this is not about living longer, that’s between you and your work-life balance. But to be an effective manager you need to healthy, functioning, and present, exercise will help with that.

2. Have someone to talk to

There are two variations of have someone to talk to on this list. That’s how important it is. Management brings shit up. It’s a psychological job. Your relationship with your parents is unfortunately relevant, as are just about every other aspect of your personality. Knowing what triggers you, and why, and having someone you trust to talk through it is the only way to do the job well.

It can be a coach, a therapist, a good friend, potentially a very patient and saintly spouse (not recommended). Ongoing, trusted and good at listening are the characteristic you’re looking for.

3. Talk with peers

As distinct from #2, find some folks in your industry, with similar job scope. Get together regularly. Talk shop. But the real shop. The stuff you don’t talk about when the people you work for or the people who work for you are around. This should be off the record. This isn’t a meet up. Start with a small group. Intimacy is the name of the game. Alcohol can help. Ask people, they’ll say yes, everyone needs to talk.

What you’ll find out is everything is fucked up everywhere. And you feel better about your own job. Your problems suck, but boy are you super glad you don’t have their problems. And they’ll feel the same way about you, and your problems.

Perspective is the thin line between a challenging but manageable problem, and chittering balled up in the corner.

4. Have a personal mastery project

Maybe you used to be a coder. Now you’re management overhead. But you really loved coding (and probably because you loved it so much, you spent a lot of time analyzing how folks could do it better, and that’s how you ended up in this mess). You’ve admitted to yourself that you can’t really spend your time writing much code anymore, but you like to keep your hand in the game, carve off a small project here or there for yourself, something that you can look back on after day and say, “Hey, I actually accomplished something today, not just go to meetings.”

You’re almost certainly doing it for the wrong reason. Cut it the fuck out.

There are lots of good reason to stay close to the day to day work (including, but not limited to, you’re an early stage startup, and everybody has to pitch in), and even more failure modes in that directions. But none of those good reasons are about you feeling better, or more in control, or like you “did something real”.

But that doesn’t mean the need you felt to learn, grow, acquire new skills, and generally stretch yourself that were hopefully key traits to getting you this far just go away, or that the sometimes vanishingly abstract accomplishments of your team can be swapped in for that personal satisfaction. For that you need a personal mastery project. Something, quite probably not related to work, where you can prove to yourself that you aren’t actually getting dumber every day (just older), but can still think, reason, and learn.

A side coding project might be it, learning a language, taking a class, practicing classical piano. Something. Something that stretches you, and you can master. By yourself.

Put your own oxygen mask on first, before assisting others

Time is tight, and your schedule is the buckshot mess of manager time. Maybe you’ve mastered time management (block off time, use Google’s auto-reject I’m-busy feature), maybe you haven’t. You’re certainly too busy with work + life to add anything new to your schedule. After all the company depends on you (as does your family). Get over yourself.

You aren’t useful to anyone if you aren’t taking care of yourself. There is an unbound set of things you could be doing better in order to help insure the success of your team that will constantly expand to fill up all the time, but the most important thing you need to be doing is making sure your own oxygen mask is on first.

(hopefully first in a series of posts turning the emails, and chats I have with folks about this work into something public. Keep an eye out for, “Help, I’m a CTO now what do I do?” and “Confidence in the face of risk”)

Tagged: Uncategorized

Novels, Yes And Improv Comedy

May 25th, 2013

So, here’s the insight I’m currently tossing around in my head: The problem is that software isn’t built; it’s written. The final product is not like the Bay Bridge. It’s like a novel. – Don’t build. Compose. – Kurt Leafstrand

No, that’s not right.

As appealing as it is. You see novels, modern novels, are a particularly peculiar form of creativity primarily characterized by being the point of view and output of a single individual. Most software, and most bridges, aren’t like that.

Maybe you’re writing novels, but most of us are doing improv theater.

Mr Chaturong Nakmamee – Koh Tao, Thailand

March 18th, 2013

I met Mr. Chaturong this morning. It was 6:30am and he was waiting with his taxi and his 7yr old son to drive us to our dive spot. It was a peaceful morning, up a small mountain, some dew still on the broad green leaves, away from much of the bustle of Thailand (if Koh Tao can be said to have any bustle at all). He might have been about 40 years old, I didn’t ask. I did ask if he was from Koh Tao, I hadn’t yet met someone from Koh Tao in the 4 days we’d been here, but I kept asking, here is what he answered.

“I’m from Koh Tao, people come from lots of places, all over, to find work with the tourists, but it was different when I was young. When I was young there were only 700 people on the island, it was quiet, no trucks, no motor bikes, we walked everywhere, it was nice, my dad was a fisherman, sometimes made coconuts, everyone was a fisherman or made coconuts. It was quiet.”

If you need a taxi in Koh Tao his number is 089 0049117.

Going on a honeymoon, be back soon

March 4th, 2013

Happy

Tagged: Uncategorized

The one thing that’s worked so far

February 10th, 2013

I gave a talk last October at the First Round CTO Summit on what we’d learned at Etsy about hiring great engineers and in particular great women engineers for our team, and a little bit about the promising results we’d seen from the Etsy + Hacker School program.

The video went up last week, it’s 18 minutes long, it was given in a venue that was originally off the record and aimed at CTOs, and talks primarily about the work that Marc led. Folks seem to find it interesting, which is deeply gratifying.

NB: also when I say “81 of them were women”, obviously I meant “81 of them were men”. This is the problem with giving talks on back to back days on different topics in Tokyo and San Francisco, you aren’t at your most polished.

The slides are on slideshare.

The Atlantic wrote up their interpretation of the talk.

Tagged: Uncategorized

Competence!

February 10th, 2013

When I first started sketching out the “Minimal competence” blog post in my head, I imagined it as part of a series. The series had three real functions:

  1. To layout a theory about our obligations as builders of services and consumers of those services
  2. To selfishly hilight the hard problems that Flickr and Etsy had tackled and others had shied away from
  3. To contextualize my frustration that Twitter’s search lacked two features that, while hard, were core to the way I wanted to use it, and the retreat from which felt like cowardice.

On point #3 those two missing Twitter features were:

  1. The ability to search over all time, not just a fluctuating window of 12 – 72 hours.
  2. To scope those searches to people you follow

Now I’ve built both of those features for much smaller, slower moving corpuses (after all Flickr is only up to photo id 8 billion and something, and most of Etsy’s items expire after 4 months), so I both knew it was possible, and also could only speculate on how you’d do it on top of a corpus like Twitter.

Which is all a long way of saying, Twitter now has both of these features, socially scoped searches that go back over years of tweets. Plus the ability to download your archives.

Good fucking work Twitter! (here’s hoping others follow)

Tagged: Uncategorized

Are you here? A feature on the side

February 3rd, 2013

I was talking with Aaron and Blackman a week or so ago about the state of reverse geocoding. This is the business of turning a lat/long into a named place. Besides a neat party trick it turns out that named places have a few benefits over floating point pairs.

  1. while technically the space is infinite and the lat/long space is finite, in practice the names we use to call places converge rapidly to a very small set (in any given region), and for whatever reason (natural or historical) seem to have an affinity for being hierarchical. Both good properties for clustering, compression, and discovery.

  2. humans don’t tend to think in floating point pairs.

At Flickr we spent a while working on turning the point where a photo was set on map (or whose GPS coordinates were shoved into the EXIF) into a place. The work of reverse geocoding is about taking a point, and finding out which polygon its in. This is a well solved problem. With two caveats:

  1. places don’t have neat boundaries, but overlap all over each other. And people disagree about the overlaps

  2. even if places had neat boundaries, and people agreed on them, availability of information about those boundaries is variable at best.

Also it turned out not many people cared, and the ones who did tend to care extraordinarily when we got it wrong. And they cared most passionately about the things that were hardest to get right, points near borders, contested neighborhoods, etc.

Most folks dealing with geo presently bypass this whole problem, and instead go straight to human places, named things, a bar, a restaurant, a rest stop on the side of a highway. And Foursquare has done an amazing job of aggregating and sorting out human attention (and intention) around these places.

But that doesn’t mean the problem is solved, merely deferred. Not all of life’s interesting moments take place in bars (just most), and when aggregating information across multiple steams collapsing onto human labelled places is challenging.

Plus, it’s just dumb that a 100mil+ people carry GPS device in their pockets and we have to buy expensive proprietary data to find out about the shape of where we live.

Anyway, here’s the pitch

Are you shipping a location based mobile app? Would you like to increase engagement? Consider adding a quiz to your app asking people whether they’re in Williamsburg or Northside? Are they in the Bay Area or the East Bay? Is this the Burlingame or the Pennisula? And then publish that aggregated data. People love quizzes, Flickr released a piece of software for turning those answers into shapefiles, the answers change over time, and paying someone for this info is silly. But seriously, if you’re presenting people geographic data, ask them sometime if you’re getting it right.

Tagged: Uncategorized

entrepreneurship, it’s also not just hacking up a website

December 8th, 2012

“People think entrepreneurship is about sitting in a dreamy studio gazing out at nature whilst sipping a latte. In reality, it is a place like your studio, or sitting in your dining room in your pajamas at 10 am looking for something better than a crayon to write shipping weights on your packages with. ” – Caroline of Pease Blossom Studio regarding No Sleep Till Christmas: Etsy Sellers’ Haggard Holidays

remembrance engines, from the comments

December 8th, 2012

“I’d like to find a site that invites you to populate your own archive – a bit like Facebook does for you on its timeline, but in a more customisable way, and in a way that allows you to share with people you choose. Anyone know of such a thing?” – from the comments