Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

"Designing for Truth, Scale and Sustainability" - WSSSPE2 Keynote

3,357 views

Published on

Keynote for WSSSPE2 in New Orleans.

Published in: Technology
  • Be the first to comment

"Designing for Truth, Scale and Sustainability" - WSSSPE2 Keynote

  1. 1. kaitlin thaney @kaythaney ; @mozillascience WSSSPE / 16 nov 2014 designing for truth, scale and sustainability
  2. 2. doing good is part of our code
  3. 3. help researchers use the power of the open web to change science’s future.
  4. 4. (0)
  5. 5. power, performance, scale
  6. 6. our current systems are designed to create friction. despite original intentions.
  7. 7. current state of science articles data patents
  8. 8. some have a firehose articles data patents
  9. 9. traditions last not because they are excellent, but because influential people are averse to change and because of the sheer burdens of transition to a better state ... “ “ Cass Sunstein
  10. 10. downside of output-driven recognition systems
  11. 11. “There’s greater reward, and more temptation to bend the rules.” - David Resnik, bioethicist
  12. 12. let’s look at an example
  13. 13. 2004-2010 $350 million spent $60m+ for “management” 70+ tools created
  14. 14. (1)
  15. 15. the culture of the specialist is changing. lowering barriers to entry.
  16. 16. - access to content, data, code, materials. - emergence of “web-native” tools. - rewards for openness, interop, collaboration, sharing. - push for ROI, reuse, recomputability, transparency. “web-enabled research”
  17. 17. what do we mean by “open research”? community technology practices collaborative interoperable open review participatory discoverable data management recognition open tools sharing / reuse mentorship designed for reuse documentation / versioning
  18. 18. we’re facing a perception crisis. at the sacrifice of scientific progress.
  19. 19. Source: Wolkovich et al. GCB 2012.
  20. 20. “... up to 70 percent of research from academic labs cannot be reproduced, representing an enormous waste of money and effort.” - Elizabeth Iorns, Science Exchange
  21. 21. http://xkcd.com/1445/
  22. 22. instill best (digital, reproducible) practice “research hygiene”
  23. 23. (2)
  24. 24. shifting practice takes a multi-faceted approach. designing for scale.
  25. 25. research social capital capacity infrastructure layers for efficient, reproducible research open tools standards best practices research objects scientific software repositories incentives recognition / P&T interdisciplinarity collaboration community dialogue training mentorship professional dev new policies recognition stakeholders: universities, researchers, tool dev, funders, publishers ...
  26. 26. our systems need to talk to one another. focus on environments that foster reuse, progress.
  27. 27. code as a research object what’s needed to reuse ? http://bit.ly/mozfiggit
  28. 28. (community driven) metadata for software discovery: JSON-LD http://bit.ly/mozfiggit
  29. 29. http://softwarediscoveryindex.org/report/
  30. 30. Instead of cancer driving the development of technology, it was the development of technology that drove caBIG moving into position where this technology could be adopted by individuals who were interested in cancer. - Andrea Califano Columbia University “ “
  31. 31. [Their] approach to fulfilling [their] mission was upside down. - Andrea Califano Columbia University “ “
  32. 32. (3)
  33. 33. our practices are limiting us. how to further adoption of open, web-enabled science?
  34. 34. “web-enabled science” - access to content, data, code, materials. - emergence of “web-native” tools. - rewards for openness, interop, collaboration, sharing. - push for ROI, reuse, recomputability, transparency.
  35. 35. “web-enabled science” what’s missing? - access to content, data, code, materials. - emergence of “web-native” tools. - rewards for openness, interop, collaboration, sharing. - push for ROI, reuse, recomputability, transparency.
  36. 36. current activity: 235+ instructors (60+, training) 4000+ learners
  37. 37. rethinking “professional development”
  38. 38. lowering (not exacerbating) barriers to entry
  39. 39. fostering a (sustainable) community of practitioners
  40. 40. (4)
  41. 41. we need to create safe spaces for our software. designing with sustainability in mind.
  42. 42. “nested sustainability” KTucker, CC-BY-SA-3.0
  43. 43. We are used to billion-dollar software, and it’s not what we can afford. I am worried that unless we rein in our expectations, we will do this experiment again and we will get the same result ... - Joe Gray Oregon Health + Science University Center “ “
  44. 44. 1. design with the audience, not individual, in mind. (be careful of the snowflake syndrome.)
  45. 45. 2. design to unlock latent potential of our systems. (and keep in mind engagement.)
  46. 46. 3. rethink how we reward researchers and support roles.
  47. 47. 4. be mindful of jargon/ semantics traps.
  48. 48. we’re here to help. teach, contribute, learn. http://mozillascience.org sciencelab@mozillafoundation.org
  49. 49. kaitlin@mozillafoundation.org @kaythaney ; @mozillascience special thanks:

×