Difference between revisions of "Informal programming"

From "A B C"
Jump to navigation Jump to search
m
 
(3 intermediate revisions by the same user not shown)
Line 16: Line 16:
 
==Introductory reading==
 
==Introductory reading==
 
<section begin=reading />
 
<section begin=reading />
<div class="reference-box">[http://software-carpentry.org/articles/how-scientists-use-computers-2009.pdf How scientists use computers] (PDF at software-carpentry.org)  
+
<div class="reference-box">[http://software-carpentry.org/articles/how-scientists-use-computers-2009.pdf How scientists use computers] (PDF at software-carpentry.org)</div>
 
<section end=reading />
 
<section end=reading />
  
Line 30: Line 30:
  
 
==Development==
 
==Development==
...
 
  
 +
* scripting vs. compiling
 +
* Perl
 +
* Python
 +
* PHP
 +
* The LAMP stack
  
 
==Documentation==
 
==Documentation==
Line 54: Line 58:
 
==Further reading and resources==
 
==Further reading and resources==
  
<div class="reference-box">[http://software-carpentry.org/ The '''Software Carpentry project] based on the excellent course and other activities of Greg Wilson at UofT and elsewhere.</div>
+
{{#pmid: 18287711}}
 +
{{#pmid: 21370093}}
 +
<div class="reference-box">[http://software-carpentry.org/ The '''Software Carpentry''' project] based on the excellent course and other activities of Greg Wilson at UofT and elsewhere.</div>
  
  

Latest revision as of 11:57, 27 January 2012

"Informal" programming


This page is a placeholder, or under current development; it is here principally to establish the logical framework of the site. The material on this page is correct, but incomplete.


Much of our programming work is "informal" in the sense that - simply for reasons of practicality - it does not respect the well-established paradigms of software engineering. Some sources refer to end-user programming to contrast this with programming by developers. Here we discuss parameters of such informal programming and how to avoid a number of potential problems.



Introductory reading

How scientists use computers (PDF at software-carpentry.org)


Parameters

  • (+) domain knowledge
  • (-) knowledge of tools, theory, and best practices
  • (-) infrequent tasks
  • (-) one-off tasks
  • (+) agile


Development

  • scripting vs. compiling
  • Perl
  • Python
  • PHP
  • The LAMP stack

Documentation

...


Testing

...


Exercises



References



Further reading and resources

Stajich (2007) An Introduction to BioPerl. Methods Mol Biol 406:535-48. (pmid: 18287711)

PubMed ] [ DOI ]

Mühlberger et al. (2011) Computational analysis workflows for Omics data interpretation. Methods Mol Biol 719:379-97. (pmid: 21370093)

PubMed ] [ DOI ]

The Software Carpentry project based on the excellent course and other activities of Greg Wilson at UofT and elsewhere.