How We Feel About How We Talk: A Language Attitude Survey ...
Infochimps: How We Do It
description
Transcript of Infochimps: How We Do It
![Page 1: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/1.jpg)
Big Data Made Easy
![Page 2: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/2.jpg)
We use a lot of new-tech tools
![Page 3: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/3.jpg)
We’ve written a lot of new tech tools
IronfanChef specialization for Big Data in the cloud
WonderdogHadoop interface for ElasticSearch
WukongRuby library for Hadoop
SwineherdWorkflow engine for Hadoop jobs
![Page 4: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/4.jpg)
But it’s not about the technology…
… it’s about the culture
![Page 5: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/5.jpg)
Hiring Process
Initial PassTechnical
Phone Interview
Team Interview
Initial Contract
Full Employment
![Page 6: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/6.jpg)
Management Structure
Flat: I regularly talk with C-level folks
Open: Everyone has well-understood roles
Fair: Leadership leads, not orders about
Understanding: Problems are addressed, not blamed
![Page 7: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/7.jpg)
Employee Support
Fully stocked kitchen
Daily group lunches
Employee joy fund and voting
Company outings, both impromptu and formal
Some fun and games, too
![Page 8: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/8.jpg)
Employee Development
Employee’s focus is largely self-directed
Lack of experience is (almost) never a determining factor
Common language for problems and frustration
Make employees awesomely valuable, and totally uninterested in leaving
![Page 9: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/9.jpg)
Technical Culture
Good ideas can come from anyone
Fail forward, not roll-back
Repeatability is your friend
Automate out of boredom or fear, not efficiency
Failure from audacity is better than failure from inaction
![Page 10: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/10.jpg)
Infrastructure Choices
More assumed access for developers
Small, decoupled, late-binding wherever possible
Build anew, rather than repurpose an old
Actively pull unused code and data from production
![Page 11: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/11.jpg)
Beyond DevOps
NoOps +1: everyone technically does part of Ops, it’s just my specialty
AllOps: product & marketing can help Ops, and vise versa
It’s all about removing barriers to being awesome, everywhere
![Page 12: Infochimps: How We Do It](https://reader036.fdocuments.net/reader036/viewer/2022062511/54b6e03c4a795984708b45a1/html5/thumbnails/12.jpg)
What’s next?
How do we handle the impedance mismatch between our model and our clients’ models?
What do we do as the company grows beyond the size of the monkeysphere?
How should we tackle user segmentation and security as we build our Platform out?