jmervine

Beyond the MEAN stack

Presenter:

@othiym23

github.com/othiym23

MEAN

pjaspers

//
// Expand various image providers, without having a lot of duplicate code.
//
// Install by hand, like an animal, or use [gasoline](https://github.com/pjaspers/gasoline)
//
Campfire.UniversalImageExpander = Class.create({
  initialize: function(chat) {
    this.chat = chat;
    this.services = {
      dribbble: /^https?:\/\/[www.]?dribbble.com\/shots\/([A-Za-z0-9]+)/,

jewelia

General key themes:

• Hiring is really hard. You’re not just hiring a “Rails Engineer” or a “Python Programmer” you’re hiring someone who can help you change the world. Tell them why! Talk about the hard problems you’re solving. 2/3 of these talks give ideas and insight into hiring from sourcing to actual interview processes.

• Rewriting systems is hard. People think they are going to replace their broken down horse and buggie with a bullet train and this often ends up in disaster. Successful rewrites require an incremental approach that takes months/years and often runs way over schedule. 2/3 of these talks go over how to handle rewrites not only from a high level technical perspective but a cultural/management perspective as well.

Two Developers, Many Lines of Code, and A Campaign that Made History

Harper Reed (CTO of Obama for America, now CEO of Modest) and Dylan Richard (Director of Eng of Obama for America, now CTO of Modest)

• http://vimeo.com/104052532

hadley

If you were to give recommendations to your "little brother/sister" on things that they need to do to become a data scientist, what would those things be?

I think the "Data Science Venn Diagram" (http://drewconway.com/zia/2013/3/26/the-data-science-venn-diagram) is a great place to start. You need three things to be a good data scientist:

• Statistical knowledge
• Programming/hacking skills
• Domain expertise

Statistical knowledge