31
Hello

Why You Should Be Fixing Bugs

Embed Size (px)

DESCRIPTION

A short talk that I gave to the CS2103 class.

Citation preview

Page 1: Why You Should Be Fixing Bugs

Hello

Page 2: Why You Should Be Fixing Bugs

Jason Yeo my name is!

Page 3: Why You Should Be Fixing Bugs

i squash this

Page 4: Why You Should Be Fixing Bugs
Page 5: Why You Should Be Fixing Bugs

Bugs Checklist

•  Bug 1 – Fixed Reply-To Explanation

Page 6: Why You Should Be Fixing Bugs

Bugs Checklist

•  Bug 1 – Fixed Reply-To Explanation

•  Bug 2 – Fixed Attachment Reminder

Page 7: Why You Should Be Fixing Bugs

Bugs Checklist

•  Bug 1 – Fixed Reply-To Explanation

•  Bug 2 – Fixed Attachment Reminder

•  Bug 3 – (WIP) Attachment Reminder Not Noticing Some Keywords

Page 8: Why You Should Be Fixing Bugs

Bugs Checklist

•  Bug 1 – Fixed Reply-To Explanation

•  Bug 2 – Fixed Attachment Reminder

•  Bug 3 – (WIP) Attachment Reminder Not Noticing Some Keywords

•  Bug 4 – (WIP) Allow Attachment Reminder To Recognize More File Types (NEW)

Page 9: Why You Should Be Fixing Bugs
Page 10: Why You Should Be Fixing Bugs

Reasons Why You Should Be Fixing Bugs

Page 11: Why You Should Be Fixing Bugs

Real Software work  on  

Page 12: Why You Should Be Fixing Bugs
Page 13: Why You Should Be Fixing Bugs

used by millions of people

Page 14: Why You Should Be Fixing Bugs

I want to put a ding in the universe

Page 15: Why You Should Be Fixing Bugs

hg.mozilla.org

Page 16: Why You Should Be Fixing Bugs

hg.mozilla.org

Page 17: Why You Should Be Fixing Bugs

People around you impress    

Page 18: Why You Should Be Fixing Bugs

Future Employers

Page 19: Why You Should Be Fixing Bugs

Software Engineering learn  many  things  related  to  

Page 20: Why You Should Be Fixing Bugs

mozmill   tests   xpcshell   tests   python   make  makefiles   javascript   jquery   java   c++  objec=ve   c   coding   style   readable   code   xul  localiza=on   source   code   cross   reference  sta=c   analyzing   making   patches   applying  patches   revision   control  mercurial   cloning  upda=ng   rever=ng   QA   techniques   filing  bug   reports   finding   regression   window  combaAng   javascript   weirdness   regular  expression   web   workers   irc   contac=ng  mozilla  developers  blogging  UI  UX  ccache  

Page 21: Why You Should Be Fixing Bugs

Coding Standards conform  to  

Page 22: Why You Should Be Fixing Bugs

Code Review

Page 23: Why You Should Be Fixing Bugs

Code Review

Page 24: Why You Should Be Fixing Bugs

Code Review

Page 25: Why You Should Be Fixing Bugs

Work On Real Software

Impress People Around You

Learn A Lot More

1 2 3

Page 26: Why You Should Be Fixing Bugs

Squashing Those Bugs don’t  just  sit  there!  start  

Page 27: Why You Should Be Fixing Bugs

Resources you  will  definitely  need  these  

Page 28: Why You Should Be Fixing Bugs

mozilla.org/hacking

Page 29: Why You Should Be Fixing Bugs

mxr.mozilla.org

Page 30: Why You Should Be Fixing Bugs

all that I have done in  fact  I  have  shared  

Page 31: Why You Should Be Fixing Bugs

Questions? thank  you.  are  there  any  

follow me @jasonyeojs

follow my blog technotroph.wordpress.com

ping me :jyeo