Facebook’s notion of a friend has a 1-bit depth. True or false. A social graph of line-art, if you will. This is in stark contrast with much higher resolution social graph that exists in our everyday lives. There are varying strengths and hues to to the sorts of social connections that describe our interaction with the world.

Smartphones capture the nuances of our really existing social graph.

We’ve begun carrying devices around that capture a wealth of information about where, who and what we’re seeing. If you’re in close proximity with a group of a dozen folks at a business address from the hours of 9 to 5, Monday through Friday, they’re almost certainly your co-workers. If you go from there to a bar with several of them a few times a week, they’re your work buddies. And those bars are probably your work-buddy bars. And at your home, a residential address where you’re in close proximity with another 1 to 5 souls who most likely share your last name; those are your family. The people you meet with on weekends, the restaurants you eat at, the parks you visit or clubs where you go dancing are the places that you go with your friends. When you travel across the country at Christmas, every year to the same place, to visit the same people, those are your extended family.

Your location, and those in your vicinity, produces a high-resolution social network. One that actually captures the intricacies of the way we really interact with people. There’s power in that idea. A lot of it. And if Facebook’s social graph is line art, the real world one is color.

A billion dollar idea?

When Color announced raising $41 million pre-launch, it triggered much second guessing of Sequoia and talk of bubbles. Are we in a bubble? Honestly, I don’t care. But if there’s anyone that I’m willing to give the benefit of the doubt to on spotting big ideas, it’s Sequoia, who have been at the top of that game for decades.

The internet peanut gallery immediately zoomed in on photo sharing not being a billion dollar idea. It’s probably not. But I’m pretty sure there’s more than meets the eye unfolding here.

What’s the data team for?

Color is putting together a top-notch data team, having recruited LinkedIn’s chief scientist. Taking the next step in the evolution of the social web is the sort of thing that top-notch data teams salivate over. More than photo sharing anyway. Heck, making sense of the way that information is connected was a big part of the spark that led to founding my own company, Directed Edge. If I were to put my chips on the table, I’d bet this isn’t about photos, but about transitioning into a high resolution social web, one that analogously, is in color.

A couple days ago I released a Wikipedia Beautifier for Chrome inspired by Readability. It was my first exploration into the world of Chrome extensions (which turned out to be surprisingly straightforward). There’s still a rough corner or three to round out, but it makes Wikipedia much easier on the eyes. The internet loves it, and I’m sure you will too.

Or, “Why using send doesn’t work as exptected”

So, I’ve been banging away at a Rails plugin the last few days.  One of the things that I initially did was to add an initializer that extended the models from the app to avoid needing to muck-up the model, e.g.:

[project root]/config/initializers/acts_as_foo.rb

SomeModel.send(:acts_as_foo, :bar)

It seemed so clean and elegant. But I noticed that my class variables were being trashed when I tried to access them and was befuddled for a day or so.

It turns out what happens is that Rails reloads all of your models (and, in fact, all classes) for every request while in debug mode. At some level in my brain I knew that, but it didn’t click that when that happens initializers aren’t fired as well, so anything that’s being fired from an initializer that will be trashed on reload won’t be there after the first request. (Though it works in production mode.)

Eventually, after much debugging, it clicked what was happening. But I wasn’t quite content to just burden plugin users by modifying each model. I stumbled across this StackOverflow entry which suggested you could achieve the same by modifying environment.rb’s config block. But really, that just shifted the inelegance around. However, the to_prepare bit set me along the right path.

The elegant solution that I eventually found comes from using the dispatcher:

require 'dispatcher'

Dispatcher.to_prepare do

  SomeMode.send(:acts_as_foo, :bar)

end

And there friends we have it: a way to send something to a model from an initializer that will be reloaded every time classes are loaded, or only once during production mode, and every request in development mode.

I’d been looking for an excuse to create a Cocoa app for a while. Even though I still switch hit between Ubuntu and OS X, I spend most of my time on OS X these days. I’d gotten Cocoa Programming for Mac OS X a while back, but had been missing that real-but-simple app idea to give it a whirl on. Until Localghost.

You see, I edit my /etc/hosts litearlly a dozen+ times a day when I want to test things in their production configuration, but with my development version. Localghost adds / removes a set of selected hosts from /etc/hosts with a system tray applet. There’s more info here:

Localghost page.

I’ve finally succumbed to the Github bug and have been slowly offloading small projects that I’ve created mostly for work stuff. The latest of these is a relatively small hack to produce an RSS fit from a Git repository, which I’d wanted to have posted in our intranet.

Usage is simple and includes a command line thinger so that uses sinatra, so you can get it all in one go.  The source and docs are here.

Additonal hacks that have now been thrown into the wild:

• fooq — a little wrapper around GCC that lets you write C / C++ one-liners or small script like thingers, and automatically includes and links Qt, without having to futz about with a make file or a main function, etc.
• QActiveResource — a hack for work since we make heavy usage of ActiveResource to pull data. This one’s a lot faster than ActiveResource for reading data — basically a C++ implementation of the find method. Details in the company blog, or naturally on Github.
• ShoParTender — Greasemonkey script to make the Shopify partners panel less unweildy. Details in the Shopify developers forum.
• Chuckery — A bunch of my utility classes and my preprocessor for the ChucK audio synthesis language. Finally got around to converting this old CVS repo to git.
• Quebec — A graphical (Qt) frontend to the standard command line calculator, bc. Includes history copy-paste and all that jazz.

I’ve realized that slowly I’m becoming a Ruby-ist. I still feel mediocre at the language, but more and more I’m finding it my go-to language for quick hacks. Drinking the Github Kool-Aid just brings me one step closer to the fold.

TagLib, which I wrote way back in the day and has since been through many releases had another bug fix release that went out today, handled by Lukáš Lalinský, whom I handed over the reins to a bit back.  There are more details in his blog post.

There’s one funny bit in the history of starting up Directed Edge: I have no idea when I decided to do it. I don’t really know when the idea first crept into my head seriously to start a company. I did a little reconnaissance on my e-mail and file archives and put together some of the critical moments:

• October 25th, 2005: Mailed Paul Graham asking about books on startups
• July 1st, 2006: Moved from working at the SAP LinuxLab in Walldorf, Germany to Native Instruments in Berlin
• January 29th, 2008: Ordered “Competitive Strategy” and “Harvard Business Review on Entrepreneurship”
• February 5th, 2008: Joined Hacker News
• February 19th, 2008: Ordered “Founders at Work” and “Fundamentals of Database Systems”
• February 28th, 2008: Last edit to list of 31 possible startup ideas
• February 29th, 2008: Asked Valentin if he’d like to co-found
• April 3rd, 2008: Notified boss at Native Instruments that I’d be leaving at the end of June
• April 16th, 2008: Ordered “Art of the Start”
• April 23rd, 2008: Went to first local founders event (Business & Beer)
• March 4th, 2008: Started our intranet wiki to begin organizing thoughts
• March 8th, 2008: Registered directededge.com
• March 13th, 2008: Sent mail to LUG where I’d gone to college asking if any other alums had founded companies
• March 13th, 2008: Got German permanent residence (meaning I didn’t need a normal job to continue living here)
• May 23rd, 2008: Went to TechCrunch Meetup Prague
• June 11th, 2008: Went to TechCrunch Meetup Berlin
• June 20th, 2008: Attended Mini-Seedcamp Berlin with Valentin
• June 27th, 2008: Full-time on Directed Edge

It was a little surprising to me that I’d apparently thought over starting a startup as early as 2005.  That was, notably, only a few months before I quit at SAP, and getting the itch to move on was presumably the trigger. That went into remission once I was settled in Berlin and working for Native Instruments.  I don’t remember when, exactly, I started entertaining the idea seriously. Certainly for most of my time at Native Instruments, I was not. It would appear that circa January 2008, with the prospect of German permanent residence at hand, that I began the motions of learning more about what it would take.

It’s also hard to self-evaluate and say if I moved slowly or quickly — obviously I’d been toying with the idea for 3 years by the time I went full-time, but from starting real research to giving notice at work was only two months.

Having done the research, I thought I’d make it here, both to preserve it for memory-lane and on the odd chance that it’s interesting for anyone else.

I’ve traveled a good bit in my day; I’ve been to some 20-odd countries, 4 continents, you know, the works.  And if there’s one thing that I hate more than airports, it’s booking travel online.

The problem is this:  my goal is not to book flights at specific airlines, at specific airports, with specific ticket classes — it’s to book a trip.  Trips have different goals.  For example:

“I want to visit Albany and New York City next week.  I have to be in Albany on these days; NYC is flexible.”

or

“I want to go to central London next week, and need to be there for at least 3 days.”

I don’t care about the details.  I want to know:

• What are the options?
• How much do they cost?
• How long do they take?

I don’t want to have to know that Airport X is actually 30 miles from London, so I’m going to have to get a bus that costs me another £30 and takes an hour.  That should be worked into the equation.  I don’t care that renting cars is twice as expensive in Manhatten as it is upstate.  If it turns out that a high-speed train is almost as fast as a plane, I want to know that.

See, travel sites create the illusion of providing the information that I cite above, which is what makes them so infuriating.  In practice, it almost invariably takes me several hours of looking at options just to figure out how I effectively can get from point A to point B, and what the costs and logistics involved will be.

In my dream world:

Here’s how it works in my dream world:  I pick two places on a map, just like I do on Google Maps, and I get back options for how to get from point A to point B, with all variable covered.  I get nearly exact amounts of time, total costs and when I can get started.  I can chose to optimize for speed, comfort or price.

So after Fred’s post caused a little bit of a stir in the blogosphere by downplaying some of the advantages for startups being in Silicon Valley, and being from a Berlin-based startup that’s out exploring the Silicon Valley vibe this month it set me to wondering — just where have most of the “great” software companies been started?

Forbes has a list of the 2000 largest public companies, so I went through and picked out the top 20 and noted their locations.  Here’s the list:

1. IBM, New York
2. Microsoft, Washington
3. Oracle, California
4. Google, California
5. Softbank, Japan
6. SAP, Germany
7. Accenture, Bermuda
8. Computer Sciences Corporation, Virginia
9. Yahoo, California
10. Capgemini, France
11. Computer Associates, New York
12. Tata Consultancy Services, India
13. Infosys Technologies, India
14. Fiserv, Wisconson
15. Wipro, India
16. Symantec, California
17. Adobe Systems, California
18. Affiliated Computer Services, Texas
19. Activision Blizzard, California (non-Valley)
20. Intuit, California

Notably, 7 are based in California (all but one in the Bay Area).  On the one hand, it certainly is far and away ahead of any other location (Bangalore, interestingly, being its closest competitor); on the other it shows a wider distribution of companies than one might assume.  I’ll leave further conclusions as an exercise for the reader.

Update:

I realized after publishing this that I’d used the 2007 numbers rather than those from 2009.  The number of companies in Silicon Valley remained the same.

2007 Numbers:

1. IBM, New York
2. Microsoft, Washington
3. Oracle, California
4. Google, California
5. SAP, Germany
6. First Data, Colorado
7. Electronic Data Systems, Texas
8. Softbank, Japan
9. Yahoo, California
10. Symantec, California
11. Computer Sciences Corporation, Virginia
12. Capgemini, France
13. Tata Consultancy Services, India
14. Fiserv, Wisconson
15. Adobe Systems, California
16. Infosys Technologies, India
17. Computer Associates, New York
18. Wipro, India
19. Affiliated Computer Services, Texas
20. VeriSign, California

I’m not one of the sort of folks that gets irritated when people unfollow me on Twitter, but I do like to keep track of it.  Qwitter used to provide that service, but it’s been absent without leave for a good long while.

So I hacked together a little Ruby script that when run shows me the folks that have unfollowed me since the last run and a little info on them.  Just add your username / password right up there at the top and let the disgruntledness begin! Enjoy.