Prepare your lesson on complexity
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- content, documentation
Research direction
Start with the coursework page at https://sdc.codeyourfuture.io/complexity/prep/ and choose one listed topic, using the linked resources to explore it. Prepare a non-computer lesson or presentation and give the demo in class; Friday demos and ITP trainees provide opportunities for feedback.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://sdc.codeyourfuture.io/complexity/prep/
Learning Objectives
- Put together a presentation on a topic you explored in prep
Why are we doing this?
By teaching we learn. The best way to really understand a subject well is to know it well enough to teach another.
In class this week you will be teaching something. You will be explaining one of the following computer science concepts. You will not use a computer to explain this, but something else. This could be a whiteboard presentation, a drawing, a game, a conversation, or anything you like that will help you communicate the concept, except a computer!
Topics (for both sprints)
- Caching
- Precomputing
- Memoisation
- Time complexity of either logarithmic, linear, quadratic, or exponential algorithms
- Any sorting algorithm that takes your fancy
- Any search strategy
Maximum time in hours
4
How to get help
Come to Friday demos to practice your lesson. Ask trainees in the ITP course to give you feedback.
How to submit
Give your demo in class.
How to review
No response
Anything else?
- Dominant language
- Python
- Stars
- 0
- Forks
- 60
- 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-Complexity
-
NotCoursework
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
🏕 Priority Mandatory 📅 Sprint 2 Core Module-Complexity Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Module-Complexity Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Complexity Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
🏝️ Priority Stretch 📅 Sprint 2 🦑 Size Large Module-Complexity Optional Submit:PR
Difficulty 3/5 Half a day Newbie friendliness 45/100
All issues in CodeYourFuture/Module-Complexity
Similar issues
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
documentation
Difficulty 2/5 Half a day Newbie friendliness 62/100
inmanta/inmanta-core#10835 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
sponsored
Difficulty 2/5 1-3 hours Newbie friendliness 65/100