Skip to main content

A Summary of Talks I've Attended Recently

I've been to a lot of talks and a conference recently. These included:

I thought I would blog about ideas that were either:

  • New and interesting.
  • Not new, but came up a lot.


  • Be passionate or go home.
  • Be a pain killer, not a vitamin.
  • Be pragmatic; working code is better than beautiful code.
  • What's in it for the user?

Startups Should Keep in Mind

  • Big, bloated companies are good targets.
  • There is lots of room for passion-centric communities.
  • We consistently see the pattern of boom, correction, lasting change.
  • Amateurs are becoming really powerful.

Getting Started

  • Keep talking to real users, not just your techie friends.
  • Don't go beta with something that sucks.
  • Raise less money, spend less money, hire slowly, fire quickly.
  • Developers should be in the same timezone.
  • Use specialists; for instance, don't waste a good engineer fighting XHTML/CSS browser issues.
  • Don't cut corners; take care of the details.

Attracting and Keeping an Audience

  • Make it dead simple to use.
  • Do your own support.
  • Make contacting you really easy; an email address is not enough.
  • Declaw your customers by being polite and apologetic when they are rude.
  • Groups begin to fail when there are more than 150 people.
  • Don't break APIs.
  • Support CSV.

User Experience and Design

  • Put off forcing people to sign in as long as possible.
  • It's all about discoverability, recoverability, context, and feedback.
  • Make it pretty.

Production Environment

  • Plan for maintenance.
  • Graph and measure like crazy; create a dashboard.
  • Do one touch deploy; automate everything.
  • It's all about process.
  • Don't be special.
  • Design for debugability.
  • Embrace cheap hardware; expect hardware failure.

User Contributed Content

  • Most people won't contribute--that's okay.
  • Spam is a deep problem.
  • A self policing community is necessary, but not sufficient.

What's Cool

  • flickr
  • digg
  • Web APIs
  • Second Life
  • Creative Commons
  • Agile software development
  • Interoperability between Web and desktop
  • Adobe Apollo
  • memcached
  • Newsvine
  • Techcrunch

The most popular and impactful talks did not use traditional bullet point slides. Rather, they were mostly verbal, without reference to notes. Nonetheless, they were extremely well focused and structured. Slides often consisted of images licensed under Creative Commons found on flickr. The images set the mood. Also popular were slides that showed a single word or phrase. These slides were synchronized perfectly to the speech.


Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p