Entries tagged “tech”

Last week, I found this picture of a group dinner at Guero's restaurant in Austin, TX, taken during South by Southwest in 2002.

At the time, most of us at the table knew each other primarily through the web and through the then-nascent blogging community. But in the seven and a half years since then, many of us have gone on to become entrepreneurs or creators, launching dozens of companies and products. I'm still collecting names and companies in the comments on Flickr, but just a cursory glance shows founders from Blogger, Six Apart, Adaptive Path, Flickr, Gawker, Twitter and more.

I point this out not (just) to name drop — you can click through to the Flickr image to see notes about who was there, read what they've done, or add your own annotations. But I also wanted to highlight one of the most important resources that creative people need to truly succeed: A community of peers.

In the business world, and especially in the technology industry, we focus a lot on the functional requirements of raising money, or on the technical requirements of having certain features or technological capabilities. What I've found, though, is that being part of an active, ambitious, supportive and diverse community of peers is just as valuable, if not more so, than any of the more prosaic prerequisites for success. That's even true in this photo — some of the people whom I met in person for the first time that night or that weekend have gone on to become among my closest friends, the biggest supporters of my work, and have ventured their formidable social capital to support my career. An even more diverse community of others whom I met at similar dinners or other events have played a similar role as well. Yet, at the time this photo was taken, I don't think any of these people had ever taken venture capital money for any project they'd ever done — everyone here had bootstrapped their way to the table.

So, it's easy to focus on the money or the little technological accomplishments, but I am glad I found these old pictures as a nice reminder that we should set aside time for a great meal with smart friends every once in a while. If it's not enough enticement that you're just having a good time, you can also justify it as one of the most worthwhile investments you can make in your future success.

Here are some interesting recent blog posts and articles, mostly by friends or acquaintances of mine, all of which add up to an interesting narrative.

• Spencer Ante in BusinessWeek documents Mint's sale to Intuit:

Mint.com owes much of its success to one such investor, First Round Capital, which opted to back the fledgling company at a time when other VCs demurred. Indeed, the Mint.com acquisition is First Round Capital's largest exit, beating out the $100 million sale of portfolio company Powerset to Microsoft (MSFT). And although First Round Capital would not quantify the return on its investment, co-founder Josh Kopelman says the Mint.com deal generated the highest return of any deal the firm has done. Previously its best return came when eBay (EBAY) acquired StumbleUpon for $75 million, which generated more than 14 times First Round Capital's original investment. "I don't think this changes our strategy," Kopelman says. "It is continued validation for our approach."

• Sarah Lacy of TechCrunch reminds startups that they're supposed to be changing the world:

I did interviews with most of the TechCrunch50 experts backstage and there was a common gripe about the companies launching there: Not enough passion, not enough swinging for the fences, not enough trying to change the world. There were too many people building safe businesses, too many companies just trying to make existing things slightly better, and too many people wanting to be the next Mint.com, not the next Google. Nothing against Mint, but Silicon Valley wasn’t built on $170 million exits.

Web visionaries like Reid Hoffman and Sean Parker struggled to come up with positive feedback on stage. Robert “I-get-excited-by-nearly-any-start-up” Scoble was so bored he was playing Hangman via Twitter with Paul Carr. Marc Andreessen praised Udorse—a company that he joked would make the world a worse place if it succeeded—because at least it was a new idea. Tim O’Reilly said he didn’t care whether Cocodot, one of the companies he judged, succeeded or failed because it was so meaningless in the world. And Tony Hsieh just said it blatantly: “I didn’t see anything that was trying to change the world.”

In some ways, I feel like Sarah's post is a direct corollary to my own earlier post where I'd suggested that the U.S. Government is the most interesting tech startup of 2009.

The ever-diplomatic Jason Fried of 37Signals riffs on a topic that he and I were just talking about last night, a lamentation of modest ambitions:

Mint’s sale to Intuit really pissed me off.

Why should I care? Because I think it’s indicative of a VC-induced cancer that’s infecting our industry and killing off the next generation. I don’t know the full backstory, but I’d bet this sale was encouraged by a Mint investor.

Here’s a fresh new company that was gunning for an aging incumbent. And not only gunning, but gaining. They had a great product, great design, and great potential. They were growing rapidly and figured out the revenue game. They were on their way to redefining an industry — one that was left for dead by the current custodians.

They were everything their main competitor, Intuit, was not. While Mint was inventing, Intuit was out of it. People used Quickbooks/Quicken out of habit and legacy. People used Mint because they loved it. Intuit was disgruntled, Mint was disruptive.

But here’s what happened: Intuit, last decade’s leader in personal finance, just became the next decade’s leader in personal finance. Mint had their number, but they sold it for $170 million. A big payday for sure, and if that was their two-year goal then they nailed it, but I can’t believe that was the point behind Mint. It had too much potential.

Mint was a key leader of the next generation of game changers. And now it’s property of Intuit — the poster-child for the last generation. What a loss. Is that the best the next generation can do? Become part of the old generation? How about kicking the shit out of the old guys? What ever happened to that?

• Chris Dixon, co-founder of Hunch, talks about the impending era of interesting new NYC tech startups:

There are a bunch of veteran entrepreneurs actively investing in and mentoring seed stage startups. Google has a big office here and many people seem to be leaving to go start companies.

...

New York City has many of the same strengths as Silicon Valley - merit-driven capitalism, the embrace of newcomers and particularly immigrants, and a consistent willingness to reinvent itself. Silicon Valley will always be the mecca of technology, but now that people here are getting back to, as Obama says, making things, New York City has a shot at becoming relevant again in the tech world.

• And Caterina Fake talks about how the connections in our city will fuel this tech renaissance:

Yes. As someone who goes back and forth between New York and Silicon Valley, I see more companies being started in the Valley. But I am seeing some great consumer internet companies being started out here too. Etsy is a great example. Hunch has to be on this list. And Kickstarter, which just recently launched, and is changing the way that creative projects themselves are funded. A promising beginning. There need to be more startups, naturally, and more seed capital, and a hometown newspaper, as Chris also notes. And the CS grads moving into startups rather than financial services companies. I'm optimistic.

Though Caterina is still optimistic about startups in Silicon Valley, I'll offer up that one of the biggest changes in her perspective since saying three years ago that it was a bad time for a startup is that she's spending a lot more time in New York City these days. Finally, my friend Jen Bekman exemplifies the diversity of NYC's nominal "tech" community, in that her startup and company are squarely focused on the world of fine art. As Jen says:

[T]here’s so much else going on aside from technology — the valley might hold the title of the best place for start-ups in technology, but NYC is the best place for many things.

The diversity of experience on the 20×200 team is incredible and inspiring. Everyone I work with has done a bunch of other things aside from technology, and not one of them set out for a tech career to begin with. Among us are photographers, musicians, artists, writers, lawyers, teachers and wine experts. We all love the internet (a lot! too much?) but what drives us most is our love of art and the people who make it.

Does this happen in Silicon Valley? Perhaps, but my time spent there — which I loved, for the record — was about an immersion in technology. Here in NYC it’s about the thing itself.

...

Then again, if you live too long inside the echo-chamber, it’s easy to forget who’s going to be using all this technology in the end. The reality check is important, almost as important as being able to hail a cab whenever I damn well please.

The thread that ties all of these things together for me is that technology adoption happens now because of culture and media, not simply for its own sake or because certain types of capital are available. It happens because a vision is ambitious enough to capture the attention of artist and writers and creators of all sorts, not just other technologists or people within the bubble of the existing tech community. And cities like Chicago, Boston, Washington D.C. and, particularly, New York City, have a decided advantage when it comes to connecting to those in the tech community to the rest of the world. We also have an unparalleled history of ambition (and, yes, ego) to match that potential.

I hope entrepreneurs learn a lesson from the few underwhelming startups that are out there, and realize that the model of making incremental improvements on companies that already exist is a recipe where, even if you achieve your goals, you may not have achieved much of a success. And if everyone around you has similarly unambitious goals, then maybe you need to be in a place where that's not true.

Note: I use, and like Mint.com, and I'm happy for their success and am hopeful that they have a positive impact on Intuit. I am not arguing that their definition of success should be the same as mine, but rather that they may have defined a different set of goals if they had been part of a different community.

About a decade ago, the web development industry made a decisive shift towards support for web standards. Though the effort encompassed many related efforts around HTML, CSS, the DOM and related technologies, perhaps the signature work of the movement was to encourage CSS-based layouts instead of the then-common practice of using HTML tables to design a page's visual appearance.

The campaign was extraordinarily effective, to the degree that most new sites that launch today use CSS as their primary system for styling and positioning. And the more socially inept web geeks out there still consider those who use tables for layout worthy of their derision, instead of opportunities for education. Tables have fallen so far out of favor that it's not uncommon for people to be reluctant to use them even for the presentation of tabular data.

In short, for front-end web developers, tables are definitely out of fashion.

More recently, web architects and developers have adopted a new generation of storage technologies for data, such as BigTable and SimpleDB. While these systems still use tables to store data, it's common to have a far smaller number of columns in these tables than were used in older systems. And their advantages in areas like scalability and partitioning, have encouraged lots of developers to consider adopting these new data storage systems despite their unfamiliarity.

In short, for back-end web developers, fat tables are rapidly going out of fashion.

Now, I don't mean to suggest that these technological trends are merely about geeks following what's faddish or popular amongst their peers. In fact, in both cases, the shift away from traditional tables might reflect the fact that our data has to be more nimble in both how it's stored and retrieved and in how it's presented and styled. These accommodations are necessary because the applications being built are more social and human-centric in nature, which means they have to be able to adapt and evolve as relationships and communities mature.

But part of me can't help but feel sad for the tables. I'm sorry, tables! I hope you come back in favor soon.

(Thanks to Mo for the image.)

I often lament the lack of perspective in tech reporting, so it's always a delight to find a story that typifies what I'd hope technology reporting could be like: Smart, informed, and with a good sense of history. Take Caroline McCarthy's look at the allure of Fake Steve Jobs. Now, CNET's not known for being the most circumspect tech news venue around, but this is a brililiant dissection of why Fake Steve Jobs is so appealing.

Fake Steve, as a concept, is downright old-school. Think about it. In a culture captivated--obsessed, even--by the antics of high society, an anonymous satirist starts publishing over-the-top missives purporting to be from an insider in that privileged niche. In the process, the faux-mogul skewers political elites, entertainers, business titans, and ordinary people in a way that's at once outlandish and provocative, hilarious and appalling. It reeks of Swift or Dickens or Twain (although a friend of mine who's better-schooled in 19th-century literature informed me that the most apt comparison is likely Edgar Allan Poe). Were it the 19th century, or heck, the 1990s, the satirist's medium of choice likely would've been a serial or set of letters in a major news outlet.

And she's absolutely right. The fact that tech culture has become so pervasive as to merge with pop culture, and that personalities are so well-known that they can be used as a springboard for social criticism, is a milestone for the technology industry. It also points out why unmasking Fake Steve would be a little bit like telling a kid the truth about Santa Claus: You may be factually correct, but you'll have ruined all the fun and lost the little bit of magic that we have left.

From the comments on one of my recent posts, here's a perfect example of the challenge of explaining technology. I'd provided a set of links for subscribing to my site.

From "AbC":

I hate something about this whole feed business. I see techies falling over themselves trying to use the simplest possible language to help the rest of us understand what feeds really are and how they work. It's like a lot of people dumb down the definitions and try to use terms they think we'll understand and be able to internalize.

Hell no.

Tell me exactly how these things work ... tell me a feed is like an HTML file that has the address/URL of where a site's latest content is posted and that you can specify exactly how you want to see the new content - snippets or full blow-by-blow.

I maybe wrong ... because techies are really muffling the real definitions with their softened, purpotedly easy to understand definitions.

I think AbC's wrong. Here's why, courtesy of Joanne:

Thanks for posting this. I've heard of RSS before, but it all seemed like black magic until I tried out bloglines. Your post inspired me to get started!

No offense, but somehow I find the argument (and potential readership) of the Joannes of the world more compelling.

I guess I'm not the only one thinking about copy and paste. Ray Ozzie is way, way ahead of me. In a development that's clearly been brewing for some time, Ray responds to the demand for better data interoperability:

And what was the most fundamental technology enabling “mash-ups” of desktop applications?

The clipboard. And a set of common clipboard data formats.

Before the clipboard, individual applications (such as Lotus 1-2-3 with its Copy and Move operations) enabled intra-application data transfer – in a world largely designed around a single running application. But the advent of the multi-application user environment, combined with the simplicity of the Select/Cut/Copy/Paste/Clear model, suddenly empowered the user in ways they hadn’t previously experienced.

More on this later, but for now it seems like the only official Microsoft resource on Live Clipboard is this mailing list. I'm sure there will be more discussion on MSDN later.

There's been a lot of conversation lately about reinventing desktop office applications on the web. The first (and sometimes second) versions of all the stalwarts are out there: Word processors, spreadsheets, databases. I can think of Writely and Writeboard and NumSum and JotSpot and of course there's dozens of others if you go out and do some research. (Good roundups and good analyses abound.)

But I spent a lot of time watching, learning about, and customizing office applications the first time they were rapidly evolving and picking up steam. I even made a living for a few years building on top of them. And there's some mistakes being made by this generation of web apps that I hope get corrected.

We can all learn a lot of lessons from the history of DDE/OLE/ OLE3/COM /ActiveX/DCOM /COM+ (you can start reading up on Wikipedia to get some background) and how we went from everyone using best-of-breed standalone apps to one integrated, nearly monolithic Office.

It basically all started with copy and paste. People who never spent a lot of time in singletasking, character-mode operating environments like the DOS command line don't recall that simply copying-and-pasting information between apps was difficult at the time. And part of the revelation of Windows for mainstream users (or Mac, for leading-edge tech fans), was being able to easily share data in that way. This was different than what Unix users were used to with the command-line pipe, or from what most applications do with feeds today, in allowing structured information flows between applications.

There's a desire to combine data from different sources in an arbitrary way, and to have the user interface display the appropriate tools for whatever context you're in. The dominant model here, probably because of the influence of the early PARC demos, is to have toolbars or UI widgets change depending on what kind of content you're manipulating. Microsoft was really into this in the early 90s with OLE2, where your Word toolbars would morph into Excel toolbars if you double-clicked on an embedded spreadsheet. It was ungainly and ugly and slow, especially if you had less than an exorbitant 8MB of RAM, but the idea was pretty cool.

And it still is. People are so focused on data formats and feeds that they're ignoring consensus around UI interoperability. The Atom API and Metaweblog API give me a good-enough interface if I want to treat a discrete chunk of information (like a blog post) as an undifferentiated blob. But all the erstwhile spec work around microformats and structured blogging (I forget which one is for XML and which one's for XHTML) doesn't seem to have addressed user experience or editing behaviors.

All of this is a long winded way of saying, we don't have much beyond copy and paste right now. If I want to put a NumSum or JotSpot spreadsheet into a Writeboard document, I basically can't do it. Maybe I can do it if all the apps are made by the same vendor and are made available as part of a suite, but we had that with Halfbrain seven years ago.

Now, nobody really adopted the interop specs for embedding rich objects between apps when there was the chance to do this on the desktop fifteen years ago. And this was part of the reason Microsoft Office was able to so completely dominate on the Windows platform by the mid-90s. Nobody else would interoperate in a way that let you easily swap in, say, Quattro Pro for Excel, and nobody else had a consistent way of scripting actions between apps. Of course, the point is moot, because Microsoft used bundling, some brutal and possibly unfair pricing, and an almost pathological underdocumentation of the specs to solidify their lead anyway. And that gave them the time to standardize around VBA as a cross-app scripting language, which took years longer than they had planned.

I can't even imagine trying to debug cross-app scripting on Ajax apps. If it's possible, it sure can't be pretty.

But the battle for office app supremacy on the desktop may have actually been a fight instead of a rout if all the also-rans had added up to something more than the sum of their parts. What was needed was not just mixing and matching at the monolithic suite level, but more granular control over which components would edit particular types of information. It took Microsoft until Windows 2000 for apps to stop just grabbing each other's file formats indiscriminately, and most regular computer users still probably aren't sure what the hell application is going to start up if they click on an MP3. And if you want to automate the simple act of copying and pasting from Lotus 1-2-3 to WordPerfect today, more than 20 years after those applications launched? It's basically just as difficult as it was when Windows 3.1 came out.

So, I'd love to see, as a user, a way for real rich data exchange to happen between the new wave of online applications. I'd like to see some efforts by (at least!) this group of vendors to make it possible to make compound documents between their applications, and then to choose from one or more tools for editing the discrete objects that make up those documents. And I'd like to be able to automate actions between these multiple tools without resorting to Greasemonkey hackery or convoluted browser tricks.

What can I offer in exchange for these features? Well, I'd pay to use the apps that are useful, of course, and I'd help promote the apps by sharing those documents with people. But I can also offer some tiny bit of defense over being completely obviated by the inferior, less open web office applications of the future that have better distribution due to the bundling that will inevitably come to this space. And scriptability means you can get features for free that you haven't even thought of, which is a nice way to combat the bundled single-vendor suites that sacrifice flexibility for consistency and integration.

My theory is that the current wave of web office application developers, like the last one during the dot com bubble, has ignored the lessons of the desktop office suite battles. I'm hoping to be proven wrong.

Other links: Some pieces on this and related topics from the past couple years include my own stories and tools, an overview of web-app tech so naive it makes me wistful for my more innocent days. It's remarkable how similar it is to Dave Winer's What is a Web Application?, which predates it by two years. I found Dave's piece as a link from his review of the state of the art in web office apps six years ago. It reads an awful lot like Richard's review, only now we have feeds on everything and there actually seem to be some users.