Resource suggestion for the Sprint 1 complexity exercise

Open Beginner friendly
#225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, python
Domain
documentation

Research direction

Review Sprint-1/README.md's Resources section and the existing HelloInterview two-pointers entry, then check the linked PracHub exercise for fit with the module's complexity objective and any external-resource policy. Done means a maintainer-approved, neutral link is added beneath it with matching wording; otherwise leave the README unchanged.

Written by the indexing model from the issue text.

Description

NotCoursework

Hi CodeYourFuture maintainers,

I worked through Sprint-1/README.md and noticed the Resources section intentionally combines language references (Set, toSorted, Python sorted), a HelloInterview two-pointers overview, and a video before the Big-O explanation.

Would this concrete follow-on exercise be useful for learners after they understand the two-pointer pattern?

https://prachub.com/coding-questions/implement-two-pointer-unique-pair-sum-search

It asks learners to implement a unique-pair sum search and explain the time/space tradeoff, so it connects the two-pointers reference directly to the module's complexity objective. Disclosure: I am the founder of PracHub.

Possible neutral addition beneath the current two-pointers resource:

  • PracHub two-pointer pair-sum exercise - implementation practice with complexity analysis

I can open a minimal PR if this fits the curriculum. If external practice links are intentionally limited, please close this with no action. I am not asking to remove or replace the current HelloInterview link.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Complexity

All issues in CodeYourFuture/Module-Complexity

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.