Betclic Dojo - Where is Fluffy?

Transcript

1. Code Dojo Architectural Kata
2. vCommunicate v with your partner, be a pair, with the group vCode is design v No design talk without code, no code without talking vSlow down v No due date, no delivery, no tricks vLearning v Open-minded, from others vChallenge yourself v don’t be reluctant to try something new Code Dojo Some principles
3. Some tools • JetBrains Resharper (R#) – Productivity tool – Third hand of the developer – Must have for safe refactoring • Ncrunch – Continuous testing tool – Increase speed and feedback of unit testing – TDD without knowing • nFluent – Better assertions – Gorgeous error messages
4. Some tips • Talk • Baby steps • Red Green Refactor • Talk • Switch pilot as much as possible • Listen
5. Architectural kata
6. Architectural Kata DISCLAIMER This is a session without any tests nor any code
7. About Architectural Kata is a way to practice software architecture A customer will present a product idea You need to propose architecture of a software system You will present and justify your design in front of others Vote for the best architecture
8. Some rules Work in group of 3/4 persons None of you need a laptop You may ask moderators any questions about the project Any technology is fair game You may safely ake assumptions about technologies you don’t know well
9. The project Where’s Fluffy?
10. Description People who lose their pets often post on Craigslist or post fliers around the neighborhood. Local business folks want to go one better, a service describing missing pets, pet rewards (brokered/managed by the service), and location data points (GPS) of pet sightings Requirements: - users interested in finding pets register on the site - anyone can see a list of pets missing near to their location - pet finders can post "pet found" messages (with mandatory photo proof) and collect rewards on confirmation from pet owners - users can comment on pet missing entries, offering data points (sighted, area checked with no results, etc) - local scalability (per-city), but possibly scaling out to other cities - mobile device accessibility
11. Discussion Phase
12. Peer Review Phase
13. Voting Phase