- Use a problem solving approach to implement user requirements
- Build a web app
- 1: In order to access more requirements, let me know when you’re done
- I'll need up-to-date documentation to know how to run your app
- 2: There are no steps/walkthroughs
- 3: Afternoon pairing - equal commits.
- 4: All work must be test-driven
- User sees the home page at the index where it has
- A heading
- A form
- All the messages with a timestamp in reverse chronological order(newest at the top)
- User can input text of a message
- User can submit the form and see the new message at the top of the previous messages
- Tues / Wed / Thurs 10 - 12noon Walk-in Q&A with @edward
- Follow BDD
- Focus on pairing well and getting better at communicating
- Reflect on your learning and problem-solving process - and actively seek to improve them
- Keep tasks *as simple as possible
In your pairs, you should both be aligned on the following. If you're not drawing diagrams for each other on paper - something's not happening!
- User stories
- Diagram what it’s going to look like
- What pages - rough sketches
- Diagram some typical requests and responses - the flow of data through your app
- Some first tests
- See @edward