Group Project: Tic-Tac-Toe - Steps 1 to 6
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start with the README.md in the linked terminal-tic-tac-toe coursework repository and review steps 1 to 5 before beginning step 6. Work with two teammates, divide the specified tasks, write tests, and use the README steps as the completion criteria; there is nothing to submit for this issue.
Written by the indexing model from the issue text.
Description
Learning Objectives
- Split tasks among a group
- Write code according to a specification
- Write tests for your code
Link to the coursework
https://github.com/CodeYourFuture/terminal-tic-tac-toe
Why are we doing this?
One of the most important abilities you can have as a software developer, is the ability to work well within a team. There are many aspects to this, including:
- communicating clearly and consistently
- breaking down work into smaller tasks that can be shared among the members of the team
- handling disagreements with your team mates
- working with Git as a team
In this project, you will need to work as part of a team of 3 people. Use Slack to find 2 other people in your region to work with.
Organise a time to meet with your team. Together, follow the steps in the README.md file of the repository. In this sprint, you can work through steps 1 to 5, and start working on step 6.
Maximum time in hours
3
How to get help
If you get stuck or need help, discuss your questions or problems with your teammates.
If you need further help, raise your questions on Slack.
Submission & Review
Nothing to submit for this issue. Your team will be completing it's work in the next sprint.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 327
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Data-Groups
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Data-Groups Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
📅 Sprint 1 NotCoursework
CodeYourFuture/Module-Data-Groups#1443 · 1 assignee ·
-
🏝️ Priority Stretch 🐇 Size Small 📅 Sprint 2 Module-Data-Groups Optional Submit:Issue
Difficulty 1/5 Under an hour Newbie friendliness 58/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Groups Submit:Issue
Difficulty 1/5 1-3 hours Newbie friendliness 58/100
-
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 3 Module-Data-Groups Optional Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Data-Groups
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100