Difference between revisions of "Informal programming"

From "A B C"
Jump to navigation Jump to search
(Created page with "<div id="APB"> <div class="b1"> "Informal" programming </div> {{dev}} Much of our programming work is "informal" in the sense that - simply for reasons of practicality - i...")
 
m
Line 12: Line 12:
  
 
__TOC__
 
__TOC__
 +
 +
 +
==Introductory 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)
 +
<section end=reading />
  
  
Line 21: Line 27:
 
* (-) one-off tasks
 
* (-) one-off tasks
 
* (+) agile
 
* (+) agile
 
  
  
Line 35: Line 40:
 
...
 
...
  
 
 
==Introductory reading==
 
<section begin=reading />
 
<section end=reading />
 
  
  
Line 49: Line 49:
 
==References==
 
==References==
 
<references />
 
<references />
 
* http://software-carpentry.org
 
  
  
Line 56: Line 54:
 
==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>
  
  
Line 62: Line 61:
  
 
</div>
 
</div>
 
 
 
 
http://software-carpentry.org/
 

Revision as of 00:08, 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

...


Documentation

...


Testing

...


Exercises



References



Further reading and resources

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