Skip to content

Instantly share code, notes, and snippets.

@stefanhoth
Created March 13, 2012 15:11
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save stefanhoth/2029345 to your computer and use it in GitHub Desktop.
Save stefanhoth/2029345 to your computer and use it in GitHub Desktop.
Dos & Don'ts for the perfect developer event

Dos & Don'ts for the perfect developer event

A crowdsourced list compiled by Stefan Hoth and the fine folks at the Droidcon Berlin Barcamp.

How would you describe yourself? (just tags)

  • (Android) developer
  • entrepreneur
  • event-dude/-girly
  • networker
  • influencer
  • consultant

What events are we talking about?

  • Hackathon
  • Conference / lightning talks
  • Barcamp
  • workshop
  • socializing/party/BBQ/etc.
  • regular user group meetup
  • start-up weekend/ elevator pitch/ etc.
  • focus group tests

What motivates you to go to an event? What do you expect?

  • meeting new people & friends
  • learn something/ get experience
  • advertisment for yourself or a product/idea/etc. -> and the conterpart
  • teach something
  • get new ideas/opinions
  • recruiting
  • dating
  • tranining

Which drinks/food do you expect?

  • I want to know beforehand how expensive it will be and where I can get everything .
  • drinks should be always free
  • I'd like to have something special or at least a regional speciality.
  • The value of the food should reflect the ticket price.
  • Fast food is fine. 2K calories per person/day is acceptable (for the one guy)
  • healthy/vegetarian food should be there as an alternative
  • eating in breaks together is better than just a 24h open "buffet"

What leaves a good impression in your book?

  • original/funny host/moderator
  • interesting audience
  • interesting topics/knowledge for real world usage
  • quality & depth of talks should be communicated
  • perfectly balanced schedule/categorization
  • list of attendees
  • documentation (slides/photos/videos/code etc)
  • sponsored talks should be easily recognizable (no "traps")
  • outlook for what's next in the field of interest
  • gadgets/gifts/something useful for the future
  • enough power sockets for our devices

What scares you off?

  • uneasy entry (ticket problems, failed registration, server problems, no confirmation etc.)
  • unprepared speakers
  • non-working wifi for work-mode
  • unclear room plan/schedule
  • missing topic/focus
  • high prices for tickets and food/drinks
  • no value (buzz-word-bingo)
  • event location/setup doesn't fit the audience
  • bad timing (talks too long, breaks to short, not on schedule)

Random tips

  • if you have to print something this should be useful during the event (directions to the location/ room plan/ schedule/ link list / wifi access
  • make signs for rooms (e.g. color coded, specific names)
  • make team members/helpers be easily recognizable (team shirts or sth)
  • info counter
  • badges with context (e.g. what kind of developer/profession) & which languages he/she speaks
  • information channel (e.g. twitter)
  • presentation/invitation for possible partners/sponsors/companies
  • think of the girls who want wear your swag, print GIRLY SHIRTS!
  • think of technical infrastructor (beamer, adpaters, microphone for tje room etc)
  • water for the speakers
  • get/collect feedback; sessions, event in general, location
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment