ScrapheapChallenge
From SPA Wiki
Here are what the participants found helped their efforts:
- Break the problem into parts
- "Luck" in finding components
- Focus on the minimal functionality and grow the system from there.
- Incremental, small steps
- Always keep the system working
- Don't be fixated on the technology
- Start with example code and change to fit your needs
- Find components that do more of the problem: are a better fit
- Divide the research task (e.g. finding useful components or services) between the pair
- Keep it Simple, Stupid!
- Code examples that are easy to find
Here are what the participants found hindered their efforts:
- Version incompatabilities
- Environment dependencies
- Difficult to find what you're looking for
- Descriptions of components or services not good for getting a quick idea of what the API does
- Confusing language (gobbledigook) used to describe the API.
- Leaving integration to later
- Bad example code
- Closed formats
Blogs about the Scrapheap Challege workshop at SPA 2007:
