Hysen Labs
Open-source project
azl397985856/leetcode avatar
azl397985856

leetcode

LeetCode Solutions: A Record of My Problem Solving Journey.( leetcode题解,记录自己的leetcode解题之路。)

55,763 stars9,379 forksJavaScriptNOASSERTION
01
DEEP OPEN-SOURCE ANALYSIS

LeetCode Solutions: a problem solving record with a study plan

A JavaScript repository that tracks one developer's LeetCode work and pairs it with a 91 day algorithm practice group built around daily check ins.

02
DEEP OPEN-SOURCE ANALYSIS

A solutions record with a study plan attached

The GitHub description calls it a record of a problem solving journey. The README goes further and attaches a study apparatus to the solutions: a membership discount page for LeetCode, a 91 day algorithm activity, and an offer of one on one tutoring. The author's stated belief is that learning algorithms depends on accumulation, that quantity has to come before quality.

03
DEEP OPEN-SOURCE ANALYSIS

The 91 day activity and paid tutoring

The 91 day activity is an organized practice group with a set learning path and enforced daily check ins. The README is fairly critical of the seven day or one month interview prep courses floating around, arguing that steady accumulation works better. The author also accepts 1v1 algorithm tutoring, priced according to the student's current foundation and the content wanted.

04
DEEP OPEN-SOURCE ANALYSIS

How the repository is organized

Beyond the solutions, the README explains a daily question activity run inside WeChat and QQ groups, where everyone solves one problem together and the results get filtered into the solutions module later. A guide to basic techniques lists divide and conquer, binary search, greedy, sorting, search, graph theory, and dynamic programming topics like knapsack and longest subsequence. A medium difficulty collection carries the advice to code each solution yourself even after reading the explanation, because the details only stick through writing them. A third party plugin site estimates contest scores based on pass counts, and the homepage links to a Gitbook version.

05
DEEP OPEN-SOURCE ANALYSIS

Editorial conclusion

The repository is really two things at once: a public record of solved problems and a hook for a study community. For a learner the more interesting part is the method: daily practice and writing every solution by hand, rather than the answers themselves.

06
DEEP OPEN-SOURCE ANALYSIS

Official sources

07
Community notes

Community notes