What Developers Should Do with Data 
Poornima 
Vijayashanker 
October 9, 2014 
@poornima 
1
Background 
• R&D Engineer @ Synopsys 
• Founding Engineer @ Mint.com 
• Founder of BizeeBee 
• Duke University 
• EIR @ 500 Startups 
• Founder of Femgineer 
2
Agenda 
• Not enough data 
• Noisy data 
• Too much data 
• Secure data 
3
BIG 
data 
4
No 
Data 
Growth Product 
Process. 
Lots 
of 
Data 
Noisy 
Data 
Secured 
Data 
Launch 
Some 
Customers 
Traction 
5
User Experience 
6
make it 
compelling 
7
Why would I allow a 20-something to 
access my financial data?! 
8
build trust 
9
make it 
frictionless 
10
delight! 
11
12
Noisy data. 
Data streams 
Third-party 
User actions 
13
No 
Data 
Growth Product 
Process. 
Lots 
of 
Data 
Noisy 
Data 
Secured 
Data 
Launch 
Some 
Customers 
Traction 
14
parse it 
15
aggregate it 
16
mash it up! 
17
18
19
No 
Data 
Growth Product 
Process. 
Lots 
of 
Data 
Noisy 
Data 
Secured 
Data 
Launch 
Some 
Customers 
Traction 
20
mo’ data. 
mo’ problems! 
21
Vocal minority or is it a major bug? 
22
Analytics 
23
Storage & Files 
24
Hosting 
25
Retrieval 
26
Warehousing 
27
No 
Data 
Growth Product 
Process. 
Lots 
of 
Data 
Noisy 
Data 
Secured 
Data 
Launch 
Some 
Customers 
Traction 
28
Privacy 
29
Unsecured data 
30
Secure it! 
User 
Employee 
Outsider 
31
32
Various hats 
White hat 
Black hat 
Grey hat 
33
responsible 
disclosure 
34
Review 
• Not enough data 
• Noisy data 
• Too much data 
• Secure data 
35
Get samples of the book: 
http://femgineer.com/ 
transform-ideas 
36
q&a 
37

What Developers Should Do With Data