User login

Duck Programming

http://unspace.ca/blog/duck-programming/

Duck programming is manageable. It starts with recognizing that while it may be designed to be carried out by people who are not professional coders, it is still programming, and must be managed with the same processes you use to manage code:

  1. Document requirements for the duck programming using the same system the team uses for programming in code.
  2. Stage changes through testing and/or staging environments, then deploy the validated changes to production.
  3. Build a system that allows users and analysts to write and run automated tests for the duck programmed functionality.
  4. Do not allow live changes to duck programmed systems.
  5. Build reversions and change management into the duck programming system.

Very relevant to Drupal, with its large proportion of UI-based development. And Drupal's making it more possible to do all of that listed above.

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.