what developers should do with data

37
Poornima Vijayashanker October 9, 2014 @poornima What Developers Should Do with Data 1

Upload: poornima-vijayashanker

Post on 01-Dec-2014

738 views

Category:

Software


3 download

DESCRIPTION

Developers rely on manipulating data to create an engaging product for users. But in the early stages of a product, there is a dearth of it, which can make the user experience dull. Then as the product ages, the amount of data increases, and can become too noisy if not properly organized. In this talk, Poornima Vijayashanker will provide some strategies for dealing with data life cycles, and how to understand what stage you're at to guide product development.

TRANSCRIPT

Page 1: What Developers Should Do With Data

Poornima Vijayashanker

October 9, 2014@poornima

What Developers Should Do with Data

1

Page 2: What Developers Should Do With Data

Background• R&D Engineer @ Synopsys• Founding Engineer @ Mint.com• Founder of BizeeBee• Duke University• EIR @ 500 Startups• Founder of Femgineer

2

Page 3: What Developers Should Do With Data

Agenda• Not enough data• Noisy data• Too much data • Secure data

3

Page 4: What Developers Should Do With Data

BIG data

4

Page 5: What Developers Should Do With Data

Process.

No Data

Lots of

Data

Noisy Data

Secured Data

Growth Product Launch

Some Customers

Traction

5

Page 6: What Developers Should Do With Data

User Experience

6

Page 7: What Developers Should Do With Data

make it compelling

7

Page 8: What Developers Should Do With Data

Why would I allow a 20-something to access my financial data?!

8

Page 9: What Developers Should Do With Data

build trust

9

Page 10: What Developers Should Do With Data

make it frictionless

10

Page 11: What Developers Should Do With Data

delight!

11

Page 12: What Developers Should Do With Data

12

Page 13: What Developers Should Do With Data

Noisy data.Data streams

Third-party

User actions

13

Page 14: What Developers Should Do With Data

Process.

No Data

Lots of

Data

Noisy Data

Secured Data

Growth Product Launch

Some Customers

Traction

14

Page 15: What Developers Should Do With Data

parse it

15

Page 16: What Developers Should Do With Data

aggregate it

16

Page 17: What Developers Should Do With Data

mash it up!

17

Page 18: What Developers Should Do With Data

18

Page 19: What Developers Should Do With Data

19

Page 20: What Developers Should Do With Data

Process.

No Data

Lots of

Data

Noisy Data

Secured Data

Growth Product Launch

Some Customers

Traction

20

Page 21: What Developers Should Do With Data

mo’ data.mo’ problems!

21

Page 22: What Developers Should Do With Data

Vocal minority or is it a major bug?

22

Page 23: What Developers Should Do With Data

Analytics

23

Page 24: What Developers Should Do With Data

Storage & Files

24

Page 25: What Developers Should Do With Data

Hosting

25

Page 26: What Developers Should Do With Data

Retrieval

26

Page 27: What Developers Should Do With Data

Warehousing

27

Page 28: What Developers Should Do With Data

Process.

No Data

Lots of

Data

Noisy Data

Secured Data

Growth Product Launch

Some Customers

Traction

28

Page 29: What Developers Should Do With Data

Privacy

29

Page 30: What Developers Should Do With Data

Unsecured data

30

Page 31: What Developers Should Do With Data

Secure it!User

Employee

Outsider

31

Page 32: What Developers Should Do With Data

32

Page 33: What Developers Should Do With Data

Various hats

White hat

Black hat

Grey hat

33

Page 34: What Developers Should Do With Data

responsibledisclosure

34

Page 35: What Developers Should Do With Data

Review• Not enough data• Noisy data• Too much data • Secure data

35

Page 37: What Developers Should Do With Data

q&a

37