The SPRUCE Mashup Manifesto

Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

This a rough collection of approaches, working practices and mindsets for developers participating in a SPRUCE Mashup:

  • Be agile
    • Develop in short bursts, demo, and get feedback from your user(s) and practitioner(s)
    • Practitioner+Developer=Success^2
    • If you don’t achieve results within a few hours, you are probably doing it wrong. Try a different approach
    • Get crude results quick, perfect and polish later
    • Scripting languages can be useful for delivering quick results
  • Re-use, don't re-invent the wheel
  • Keep it small, keep it simple
  • Wrap it up and make it easy to use, build on, or re-purpose
  • Share outputs, exchange knowledge, learn from each other
    • Knowing that a tool doesn't work so well in solving a particular problem is just as valuable as knowing a tool that does the job perfectly
    • Write up your experiences and share them
    • Publish results for evaluation and comparison with other tools

This manifesto was developed from wiki posts by Maurice de Rooij, along with discussions over the years with clever people such as Andrew Jackson, Carl Wilson and David Tarrant.

See this page for more on SPRUCE Mashups.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.