Refine your Chat Application ticket
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- content, documentation
Research direction
Open the linked coursework issue #2 to understand the large chat application ticket, then review the planning board where the smaller tickets should be created. Done means the work is split into prioritised tickets, each estimated at no more than three hours, with required and skippable work identified within the 16-hour project limit.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://github.com/CodeYourFuture/Module-Decomposition/issues/2
Why are we doing this?
The "Write and Deploy Chat Application Frontend and Backend" ticket is too big to be useful.
We can't meaningfully plan a 16 hour ticket, we can't easily tell if we're struggling and need help, and it doesn't help us understand what is important and what we should skip if we run out of time.
Split it into smaller tickets which each won't take more than 3 hours to complete. Prioritise them:
- Which do you need to do first?
- Which are absolutely required?
- Which ones could you skip if you ran out of time?
Bear in mind you only have 16 hours to do this project. It's ok to decide not to do some of the requirements. But you should be intentional about which ones you skip. e.g. it would not be ok to skip adding the ability to send messages. A chat application doesn't make sense without being able to send messages.
Maximum time in hours
1
How to submit
Create prioritised, estimated tickets on your planning board breaking down the big ticket into small tickets.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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-Decomposition
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Decomposition Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Module-Decomposition Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Decomposition Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Decomposition Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 55/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Decomposition Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Decomposition
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
NousResearch/hermes-agent#119856 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
openclaw-en
Difficulty 1/5 Under an hour Newbie friendliness 85/100
duanyytop/agents-radar#3441 ·