- Week
- Week 1
- Target
- 5
- Solved
- 0
- Reviewed
- Unchecked
TemplatesLearning & study · Coding problem log
Coding problem log
When you solve algorithm and coding test problems, log the type, result and retry date, and keep pace with your study group
What's inside · Table 2 · Checklist 3
Preview · a new document starts like this
Coding problem log
- Target problems
- Not set
- Study meetup date
- Not set
- Study partners
- Not set
Enter a target for each week in this month's goals table, then delete the example line in the problem log and add your own.
This month's goals
For each week, write the target and how many you actually solved.
| Week | TargetNumber | SolvedNumber | ReviewedCheckbox |
|---|---|---|---|
| Week 1 | 5 | 0 | Unchecked |
| Week 2 | 5 | 0 | Unchecked |
| Week 3 | 5 | 0 | Unchecked |
| Week 4 | 5 | 0 | Unchecked |
- Week
- Week 2
- Target
- 5
- Solved
- 0
- Reviewed
- Unchecked
- Week
- Week 3
- Target
- 5
- Solved
- 0
- Reviewed
- Unchecked
- Week
- Week 4
- Target
- 5
- Solved
- 0
- Reviewed
- Unchecked
Problem log
One line per problem. Leave unsolved ones as ‘Redo’ and set a retry date. Delete the example line before you use it.
Problem log
| Issue | Link | Type | Difficulty | Outcome | Retry date | What I learned |
|---|---|---|---|---|---|---|
| (Example) Two Sum | Not set | Array | Easy | Not set | Not set | This is an example line. Delete it and write your own. |
- Link
- Not set
- Type
- Array
- Difficulty
- Easy
- Outcome
- Not set
- Retry date
- Not set
- What I learned
- This is an example line. Delete it and write your own.
Study rules
•
Think on your own for 30 minutes before looking at a solution.
•
Write down what you learned, even if it's just one line.
•
Set the retry date one week later.
☐
Wrote a target for each week.
☐
Deleted the example line in the problem log.
☐
Set dates for the problems to redo.