Research Complexity using the Google DSA path
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
- Quiet
- Domain
- content, documentation
Research direction
Start with the Google Data Structures and Algorithms path linked in the issue, taking each section's quiz before reviewing its materials. Schedule regular study time over the next three months, use spaced repetition, and prepare to share what you learned at a Friday demo; completion is demonstrated through your study plan, progress, and demo.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://techdevguide.withgoogle.com/paths/data-structures-and-algorithms/
Learning Objectives
- Plan a course of study
- Self evaluate progress with testing
Why are we doing this?
Now you are moving towards working as a professional software engineer, you need to develop your research practice. How will you develop your skills after this course? How will you keep learning and growing? It is crucial that you continue your education past this very short course.
During this module, we cover a small part of data structures and algorithms. But there's a lot more to learn. Google study paths are a useful guide, with built in quizzes and links to high quality materials. In your calendar, schedule a regular time to progress through this path over the next three months.
Tips
- Take the quiz for each section first, to see how much you already know about the topic. If you do very well, you probably don't need to spend a lot of time on those materials.
- Return to topics regularly using spaced repetition scheduled in your calendar
- Use a defined path with an end goal you can state, don't just randomly watch videos about programming, please!
Maximum time in hours
1
How to get help
Find a study partner or group in your class. Organise to meet with each other at least once per month (or more) for the next six months (online or in person) to help each other stay accountable.
How to submit
Come to Friday demos to demo what you have learned, whenever you want. Grads are always welcome at Friday demos.
- 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