Code for science (rev 2)

72
{Code} for Science Andrew Lenards December 6, 2010

description

 

Transcript of Code for science (rev 2)

Page 1: Code for science (rev 2)

{Code} forScience

Andrew LenardsDecember 6, 2010

Page 2: Code for science (rev 2)

slideshare.net/lenards

Page 3: Code for science (rev 2)

Andrew Lenards • iPlant Collaborative– on Core S/W team

• University of Arizona– CS Grad, 2001

• Experienced developer, former consultant, instructor, & technical trainer

• Domain experience:– Motor Vehicle Domain– Phylogenetics / Bioinformatics (sort of)

Page 4: Code for science (rev 2)

Andrew Lenards - Activities• Learning about:

– Requirements, User Stories, etc. – S/W Design/Architecture, Patterns, SOA– Molecular Biology, Phylogenetics, Phyloinformatics, Genetics, and

Genomics

• Active in:– Tucson Java Users Group

• Semi-active in:– Tucson Startup Drinks– Ubuntu Arizona Local Community / TFUG

Page 5: Code for science (rev 2)
Page 6: Code for science (rev 2)
Page 7: Code for science (rev 2)
Page 8: Code for science (rev 2)

Hybrid Vigor

Page 9: Code for science (rev 2)

Computational ___________

Page 10: Code for science (rev 2)

Computational _Thinking_

Page 11: Code for science (rev 2)

Computational _Biology_

Page 12: Code for science (rev 2)

Computational _Gardening_

Page 13: Code for science (rev 2)

Computational _Gardening_

Page 14: Code for science (rev 2)

Bio________

Page 15: Code for science (rev 2)

Biofuels

Page 16: Code for science (rev 2)

Biochemistry

Page 17: Code for science (rev 2)

Biophysics

Page 18: Code for science (rev 2)

Bioinformatics

Page 19: Code for science (rev 2)

Page 20: Code for science (rev 2)
Page 21: Code for science (rev 2)
Page 22: Code for science (rev 2)
Page 23: Code for science (rev 2)
Page 24: Code for science (rev 2)
Page 25: Code for science (rev 2)

What do you expectwhen you graduate?

Page 26: Code for science (rev 2)

… for the computer sciencemajors

Page 27: Code for science (rev 2)
Page 28: Code for science (rev 2)
Page 29: Code for science (rev 2)
Page 30: Code for science (rev 2)

Myth of the Lone

Developer

Page 31: Code for science (rev 2)
Page 32: Code for science (rev 2)

in-practice: lots of interaction w/ technical& non-technical people

Page 33: Code for science (rev 2)

Communication is amajor challenge

Take Away:

Page 34: Code for science (rev 2)

What might help?

Page 35: Code for science (rev 2)
Page 36: Code for science (rev 2)

Software projects #fail.

Page 37: Code for science (rev 2)

… quite often

Page 38: Code for science (rev 2)

Why?

Page 39: Code for science (rev 2)

P00R (0/\/\/\/\U|\|1(4710|\|

Page 40: Code for science (rev 2)

Speaking in tongues is not allowed

Page 41: Code for science (rev 2)

Adaption

Page 42: Code for science (rev 2)
Page 43: Code for science (rev 2)

{Code} for Science

Page 44: Code for science (rev 2)

I wasn’t always interested in

science/biology

Page 45: Code for science (rev 2)

Biology is an interesting domain

Page 46: Code for science (rev 2)
Page 47: Code for science (rev 2)

I know too much aboutAuto titling & international trucking fees

Page 48: Code for science (rev 2)

I know knew too much about Auto titling &

international trucking fees

Page 49: Code for science (rev 2)

Conclusion: Act I

Page 50: Code for science (rev 2)

Miscellaneous Info

• Contact Info– Traditional: • [email protected][email protected]

– Hipster:• @alenards

• Slides are posted here:– http://www.slideshare.net/lenards

Page 51: Code for science (rev 2)
Page 52: Code for science (rev 2)

… of the community, by the community, for the community

Page 53: Code for science (rev 2)

Empowering the next generation of biologist

Page 54: Code for science (rev 2)

Why?

Page 55: Code for science (rev 2)

The world faces tough problems

in the future

Page 56: Code for science (rev 2)

Fuel/Energy

Page 57: Code for science (rev 2)

Food

Page 58: Code for science (rev 2)

Water Supply

Page 59: Code for science (rev 2)

Page 60: Code for science (rev 2)
Page 61: Code for science (rev 2)

Cyberinfrastructure

Page 62: Code for science (rev 2)

“In scientific usage, cyberinfrastructure is a technological solution to the problem of efficiently

connecting data, computers, and people with the goal of enabling

derivation of novel scientific theories and knowledge.”

Page 63: Code for science (rev 2)

Large systems designleads to diverse,

interdisciplinary teams

Page 64: Code for science (rev 2)

With the direction of Computational Biology &

Bioinformatics…

Page 65: Code for science (rev 2)
Page 66: Code for science (rev 2)

Software Development

as aCollaborative Game

Page 67: Code for science (rev 2)

Soft skills are important

Page 68: Code for science (rev 2)

Speaking in tongues is not allowed

Page 69: Code for science (rev 2)

Working in pairs, not just for

pair-programming ordebugging

Page 70: Code for science (rev 2)

Impromptu design discussions

(they often include more than just technical folks)

Page 71: Code for science (rev 2)

Image Acknowledgements• “Mad Scientist Photo” of Andrew by Alex Yelich• http://www.flickr.com/photos/sskennel/4496534369/• http://upload.wikimedia.org/wikipedia/commons/3/32/Charles_Darwin_by_Elliott_and_Fry.j

pg• http://en.wikipedia.org/wiki/File:Koeh-283.jpg• http://jitterypenguin.com/images01/SWG%20Screenshots/Zoee/Master%20Commando%20

Skill%20Tree.jpg• http://www.flickr.com/photos/tonivc/2283676770/• http://www.flickr.com/photos/designbyfront/3428784075/ • http://www.flickr.com/photos/lorelei-ranveig/2294093649/• http://www.flickr.com/photos/mathoov/4040824373/• http://www.flickr.com/photos/thatgrumguy/402041540/• http://www.flickr.com/photos/freya_gefn/2777209147/• http://www.flickr.com/photos/pkmousie/2652404430/• http://www.flickr.com/photos/sklathill/479528238/• http://commons.wikimedia.org/wiki/File:Babel_fish_badge.jpg• http://www.teachforamerica.org/assets/images/img/logo_tfa.gif• http://www.flickr.com/photos/roadsidepictures/389828793/• “Take Away” font: http://www.dafont.com/mailart-rubberstamp.font

Page 72: Code for science (rev 2)

The content of this work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike License. Your use of this material constitutes acceptance of that license and the conditions of use of materials on this site:

http://creativecommons.org/licenses/by-nc-sa/3.0/