Good coding-practices-for-scientists-jan-2014
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Good coding-practices-for-scientists-jan-2014

  • 297 views
Uploaded on

Motivating why scientists need to think about coding quality. A small introduction to test driven development as a way to enhance code quality in scientific projects.

Motivating why scientists need to think about coding quality. A small introduction to test driven development as a way to enhance code quality in scientific projects.

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
297
On Slideshare
297
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Siv Midtun Hollup
  • 2. ”I know exactly what code I need to write”
  • 3. ”Coding is easy.”
  • 4. ”I’ll just add another function instead of changing the existing one.”
  • 5. ”Don’t fix it if it ain’t broken.”
  • 6. As little code as possible Results as fast as possible Correct results Efficient code Extendable code
  • 7. ”A scientists’ nightmare: Software problems leads to five retractions” G. Miller, Science (2014)
  • 8. ”Deriving chemosensitivity from cell lines: Forensic bioinformatics and reproducible research in high-throughput biology” KA Baggerly et al, Annals of Applied Statistics (2009)
  • 9. ”Scientific software development is not an oxymoron” SM Baxter et al, PLOS Computational Biology (2006) ”Publishing scientific software matters” C. Pradal et al, Journal of Computational Science (2013) ”Best practices for scientific computing” G. Wilson et al, PLOS Biology (2014)
  • 10. To rewrite existing source code in order to improve its readability, reusability or structure without affecting its meaning or behaviour
  • 11. ”Testing takes too much time.”
  • 12. ”It’s too hard to test.”
  • 13. ”I can’t possibly test everything.”
  • 14. ”Test-Driven Development: An Empirical Evaluation of Agile Practice” Lech Madeyski
  • 15. As little code as possible Results as fast as possible Correct results Efficient code Extendable code
  • 16.  Clean Code, Robert C. Martin (Uncle Bob)  Test Driven Development, Kent Beck  Refactoring, Martin Fowler  Working effectively with legacy code, Michael Feathers
  • 17.  Introcing TDD and why it’s a good idea, Evan Dorn http://www.youtube.com/watch?v=HhwElTL-mdI  Estimation and deception, Linda Rising http://chariotsolutions.com/podcast/ete-2010session-9-linda-rising-deception-and-estimation/  TDD in action (Roy Osherove) http://www.youtube.com/watch?v=xX9hfPkA800
  • 18.  Practice coding and get feedback: http://www.exercism.io/  Online courses (subscription): http://www.pluralsight.com/