CodeYourFuture / CodeYourFuture/Checkpoint
Play computer: broken code
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 62
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 1
Description
### Link to the coursework
https://github.com/CodeYourFuture/CYF-Workshops/tree/main/playing-computer
### Why are we doing this?
In your technical interview, you may be asked to play computer.
> [!TIP]
> Playing computer means simulating how the computer executes our code. We "step through" the code, line by line, and work out what the computer does when it follows each instruction.
Practice playing computer now. Find a blocked feature or technical question with linked code. Play computer and step through line by line. Can you predict the output or find the problem?
Talk through your process in the Slack thread or ticket conversation.
### Maximum time in hours
1
### How to get help
Find someone to help by playing computer with their blocked or broken ticket.
Contributor guide
Research direction
Open the linked playing-computer coursework and find a blocked or broken ticket with linked code. Step through that code line by line, record the predicted output or problem, and discuss the process in the Slack thread or ticket conversation.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100