Informal programming

From "A B C"
Jump to navigation Jump to search

"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.