Challenge: make an existing solution shorter or faster (30 min)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
Research direction
Browse the existing solution files and choose one to improve. Keep the original, add a version named practice<n>_v2.<ext> or place yours below it, and explain the change in a comment; mention time complexity if it changes. The issue does not name a file or test, so first identify a suitable solution and compare your version with the original.
Written by the indexing model from the issue text.
Description
Think you can do it better? Prove it.
Pick any solution and write a cleaner, more idiomatic, or faster version, in the same language or a different one.
Time: ~30 minutes | Level: Beginner to intermediate
Rules
- Keep the original solution
- Add yours as
practice<n>_v2.<ext>(or below the original) - Explain what changed in a comment
- Mention time complexity before/after if it changed
Show off your best tricks. Learning from each other's style is the whole point.
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
- 2h 43m
- Merged PRs (30d)
- 7
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
-
Add one Codewars or HackerRank solution you have already solvedPossibly taken @dk5488 claimed this 2 days ago. Open5-minutes algorithm all-levels any-language beginner-friendly codewars easy good first issue hackerrank hacktoberfest help wanted interview-prep leetcode open-source students
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Huerte/algo-solutions-python#144 · 2 comments · 1 assignee ·
-
30-minutes community documentation enhancement good first issue hacktoberfest help wanted
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Huerte/algo-solutions-python#143 ·
-
5-minutes all-levels beginner-friendly codewars documentation good first issue hackerrank hacktoberfest interview-prep leetcode no-code-needed open-source students
Difficulty 2/5 Under an hour Newbie friendliness 68/100
Huerte/algo-solutions-python#140 ·
-
15-minutes 5-minutes algorithm any-language beginner-friendly c cpp csharp easy go good first issue hacktoberfest help wanted java javascript kotlin python rust swift typescript
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Huerte/algo-solutions-python#138 ·
-
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 83/100
Huerte/algo-solutions-python#134 ·
All issues in Huerte/algo-solutions-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pydantic/pydantic-ai#12091 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
CSS enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pychess/pychess-variants#2448 ·
Maintainers usually reply within 1 day
-
Bump locked PyTensor so Apple clang 21 does not pass -ld64Possibly taken @drbenvincent claimed this today. Openbug dev ops
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
ai_p2 bug comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ClickHouse/ClickHouse#128306 · 1 comment ·
Maintainers usually reply within 1 day