37
1 MY JOURNEY TO GO

My Journey To Go

Embed Size (px)

Citation preview

Page 1: My Journey To Go

1

MY JOURNEY TO GO

Page 2: My Journey To Go

2

ABOUT ME

Page 3: My Journey To Go

3

I SPENT MOST OF MY LIFE OUTSIDE OF THE UNITED STATES

Page 4: My Journey To Go

4

I USED TO BE A PHOTOGRAPHER

Page 5: My Journey To Go

5

I MAKE GOPHERS

Lots and lots of gophers…

Page 6: My Journey To Go

6

ALSO, GOPHERIZE.ME

Page 7: My Journey To Go

7

THIS IS MY FIRST KEYNOTE

Page 8: My Journey To Go

8

ART & PIZZA

Page 9: My Journey To Go

9

THE DECISION TO CODE.

Page 10: My Journey To Go

10

TFW YOU GO TO A BOOTCAMPAND SUPER REGRET IT.

Page 11: My Journey To Go

11

Page 12: My Journey To Go

12

ACCIDENTAL GOPHER

Page 13: My Journey To Go

13

BLAME STEVE FRANCIA

TWITTER: @SPF13

Page 14: My Journey To Go

14

NOBODY SUCCEEDS ALONE

Page 15: My Journey To Go

15

WE NEED PEOPLE TO BE INVESTED IN OUR SUCCESS

@GOINGGODOTNET@MATRYER@MARKBATES@DAVECHENEY@MBBROBERG@BRADFITZ@JBEDA@FRANCESC

@SPF13 @LITTLEIDEA@BKETELSEN@KELSEYHIGHTOWER@JESSFRAZ@KRISNOVA@ERIKSTMARTIN@CARLISIA

Page 16: My Journey To Go

16

JUST SAY YES.

WHAT’S THE WORST THAT COULDHAPPEN?

Page 17: My Journey To Go

17

CONTRIBUTING & ELIMINATING EXCUSES

Page 18: My Journey To Go

18

I’m not a very good programmer.“

Page 19: My Journey To Go

19

I don’t have a lot of time.“

Page 20: My Journey To Go

20

I don’t know what project to work on.“

Page 21: My Journey To Go

21

MYTH: YOU HAVE TO BE A PROGRAMMING WIZARD TO CONTRIBUTE

Page 22: My Journey To Go

22

THREE THINGS

Projects need contributions from people of all skill levels & expertise

Page 23: My Journey To Go

23

A SMALL CONTRIBUTION IS BETTER THAN NO CONTRIBUTION

Page 24: My Journey To Go

24

THE BEST PROJECT TO START WORKING ON IS ONE THAT YOU USE ALREADY.

Page 25: My Journey To Go

25

WHERE TO START

Page 26: My Journey To Go

26

WHAT ARE YOU GOOD AT RIGHT NOW?

Page 27: My Journey To Go

27

LISTENING

Listening is the best way to knowwhat the project needs.

Page 28: My Journey To Go

28

SHHHH... WE’RE LISTENING

IRC,REDDIT..

BLOGS

MAILINGLISTS

3

1 2

Page 29: My Journey To Go

29

WORKING WITH TICKETS

Code is the heart of anyopen source project, butdon’t think that writingcode is the only way tocontribute.

Often bugs are fixed inthe codebase but ticketsreported about them don’tget updated in theticketing system.

Close fixed bugs2

Bugs are often poorlyreported. Diagnosing andtriaging a bug can helpsave developers time.

Diagnose a bug1

Page 30: My Journey To Go

30

WORKING WITH CODE

Programmers of allexperience levels canhelp with the code inthe project. Don’t thinkthat you have to be acoding genius to makereal contributions toyour favorite project.

This is normally wherepeople want to start.

Fix a bug2

Any project that’s designed torun on multiple platforms canhave all sorts of portabilityproblems.

Test a beta or releasecandidate1

Write a test

Moar tests, please.

3

Add a comment

Are you confused? So issomeone else.

4

Page 31: My Journey To Go

31

DOCS, DOCS, DOCSIT’S AS THOUGH THIS MANUAL EXPECTS THAT I ALREADY KNOW HOW TO USE THE PACKAGE

Page 32: My Journey To Go

32

WORK WITH COMMUNITY

Open source is only partly about code. Community makes open sourcework. Here are ways you can help build it up.

If you’ve got ablog, write aboutyour experienceswith the projectthat you’re using.

Most programmersdon’t havedesign talents.

The best way tohelp build thecommunity is byhelping others.

WRITE A BLOG POST IMPROVE A WEBSITEANSWER A QUESTION

Page 33: My Journey To Go

33

PAY IT FORWARD GIVE MORE THAN YOU RECEIVE.

Page 34: My Journey To Go

34

DON’T BE TOO PROUD TO ACCEPT HELP WHEN IT’S OFFERED.“

Page 35: My Journey To Go

35

IT’S OKAY TO FAIL

WE ALL DO IT, AND ANYONE THATSAYS OTHERWISE IS LYING.

Page 36: My Journey To Go

36

WE ARE A COMMUNITY OF CODERS, BUT IF ALL WE DO IS CODE THEN WE'VE LOST THE COMMUNITY

Page 37: My Journey To Go

37

@ASHLEYMCNAMARA

THANK YOU