No coding needed: explain a solution in plain English (5 min)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Browse the solution files in the repository and choose one whose top comment is missing or unclear. Read the solution, then improve only its comments to explain the approach in plain English; add time complexity if you know it. Comment with the file you chose, and consider the work done when the explanation is clearer and the code is unchanged.
Written by the indexing model from the issue text.
Description
You don't have to write code to contribute
Some solutions have short or missing explanations. Help the next learner understand them.
Time: ~5 minutes | Skills needed: Reading + writing
Task
- Pick any solution file (any language)
- Read it
- Improve the top comment: what does it do, in simple words?
- (Optional) Add the time complexity if you know it
Only edit comments, please don't change the code.
Explaining code is one of the fastest ways to understand it.
Comment which file you picked.
Open for everyone
This issue is open for everyone: beginners, experienced developers, students, and people who don't code at all. Any language, any level, no experience required. If you want to help, you are welcome here.
How to contribute
- Comment on this issue to claim it
- Fork this repo
- Clone your fork and create a new branch
- Make your change
- Commit, push, and open a Pull Request
New to open source? Start here before anything else:
First Contributions - github.com/firstcontributions/first-contributions
Prefer video? Watch this: How to contribute on GitHub (YouTube)
If this repo helps you or you like where it is going, a star is a nice way to say thanks and helps other people find it. Entirely optional, and you do not need it to contribute.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 3h 32m
- Merged PRs (30d)
- 21
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Huerte/algo-solutions-python
-
15-minutes all-levels any-language beginner-friendly codewars good first issue hackerrank help wanted interview-prep leetcode open-source students testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Huerte/algo-solutions-python#188 ·
Maintainers usually reply within 1 day
-
15-minutes all-levels any-language beginner-friendly codewars design good first issue hackerrank hacktoberfest help wanted interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Huerte/algo-solutions-python#187 ·
Maintainers usually reply within 1 day
-
30-minutes algorithm all-levels beginner-friendly codewars data-structures documentation dynamic-programming good first issue hackerrank hacktoberfest help wanted interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Huerte/algo-solutions-python#186 ·
Maintainers usually reply within 1 day
-
5-minutes algorithm all-levels any-language beginner-friendly community documentation easy first-timers-only good first issue hacktoberfest help wanted learning no-code-needed open-source python students
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Huerte/algo-solutions-python#185 ·
Maintainers usually reply within 1 day
-
15-minutes all-levels any-language beginner-friendly codewars good first issue hackerrank help wanted interview-prep leetcode open-source students testing
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Huerte/algo-solutions-python#184 ·
Maintainers usually reply within 1 day
All issues in Huerte/algo-solutions-python
Similar issues
-
Remove the `pull_request_target` workflow before GitHub blocks itPossibly taken @jat255 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
IBM/mcp-context-forge#7483 ·
Maintainers usually reply within 2 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
[Bug Report]: OpenAI 辅助 API 连通性测试因输出上限仅 1 token 误报“未知错误”Possibly taken @fjfanjian claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Project-N-E-K-O/N.E.K.O#3640 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
acl-org/acl-anthology#10808 · 1 comment ·
Maintainers usually reply within 1 day