[HN Gopher] Show HN: I made a spaced repetition tool to master c...
___________________________________________________________________
Show HN: I made a spaced repetition tool to master coding problems
As you solve LeetCode questions, you can mark them as hard, medium,
or easy. The tool will then recommend questions you should review
based on (1) how hard the question was for you and (2) how much
time has passed since you last reviewed it. I'd recommend normally
attempting LeetCode problems and just marking them as hard, medium,
or easy for you at first so the tool knows which problems to
recommend you review! Here's the theory behind spaced repetition
and learning if interested:
https://www.codecademy.com/article/spaced-repetition
Author : cubemaster
Score : 30 points
Date : 2024-04-26 19:38 UTC (3 hours ago)
(HTM) web link (www.lanki.xyz)
(TXT) w3m dump (www.lanki.xyz)
| cubemaster wrote:
| Hey guys! I'm Shreya.
|
| I recently noticed that many people that solve leetcode style
| problems to learn programming patterns tend to save links to
| problems they'd like to try again later on google docs/notes.
|
| However, this doesn't help them remember to try these problems
| again or differentiate between problems that are more urgent to
| revise.
|
| Built this tool to help solve this inefficiency!
| xandrius wrote:
| Or just use this public Anki deck as a base and add your own
| questions to it: https://ankiweb.net/shared/info/1223170466
| cubemaster wrote:
| do you think it adds friction to go between the anki screen
| and the leetcode screen?
| SpaceManNabs wrote:
| how is this different from sharing an anki deck?
| xandrius wrote:
| So many people coming up with different Anki's. For me Anki is
| so flexible that I don't think anything will ever easily beat
| it.
| cubemaster wrote:
| how do you use anki for code/technical skills?
| cubemaster wrote:
| super similar - was inspired by anki! this extension shows up
| directly on the leetcode website as a starting point, but
| looking to expand to all of ankis-type features soon
| sirobg wrote:
| Seems nice, congrats! How does the recommendation algorithm work?
| cubemaster wrote:
| currently recommends 5 problems using a ranking algorithm that
| calculates a score similar to this:
|
| score = ( timeSinceLastAttempt ^ 2 ) * difficulty;
|
| Anything else you'd want factored in?
| nico wrote:
| Off topic: is spaced repetition ever used for training LLMs? Does
| that even make sense?
|
| Thank you
| mpmisko wrote:
| Training for multiple epochs is a bit like that :)
| orsenthil wrote:
| Will it stop recommending if you have mastered the problem? Or
| will it give a new problem to solve ?
| cubemaster wrote:
| for now, it will always 5 recommend problems you have attempted
| before, prioritizing the ones you solved both (1) longest time
| ago and the ones that were (2) hardest for you. so it will not
| recommend anything you haven't tried. would you want it to stop
| recommending a problem once you've mastered it? maybe an
| indication on the tool so you can mark it as mastered?
| xzel wrote:
| I'm about to start the leet code grind for interviews coming up
| and I'll give this a shot. I found your feedback form on your
| website but would be nice to post it in your post here as well.
| Cheers.
| cubemaster wrote:
| posted! thanks for the advice :)
| reddit_clone wrote:
| I keep hearing this. What exactly does 'leetcode grind' mean?
|
| I take it you solve puzzles by writing code. How does it help
| with job interviews really?
| mardef wrote:
| Many engineering interviews include literal "solve this
| problem on leetcode" sections.
| linguae wrote:
| "Leetcode grind" means solving Leetcode problems.
| Interviewing for many software engineering positions in
| Silicon Valley these days require doing well on Leetcode-
| style coding exercises where one has a limited amount of time
| to solve a problem.
|
| What makes software engineering interviews a grind these days
| is that many employers don't care about your thinking
| process; they want an optimal solution to the problem within
| the time limit without errors, since chances are high that an
| applicant will come up with the optimal solution. In
| addition, the high compensation for many Silicon Valley
| employers has made these positions very desirable and thus
| ultra-competitive. The same type of applicants who grinded
| for high SAT and AP scores in high school and who grinded in
| college for 3.7+ GPAs don't feel discouraged grinding some
| more for a six-figure job with life-changing amounts of RSUs
| once vested and other perks. You can grind hard, but chances
| are high that somebody else spent even more time studying
| than you. These types of interviews are similar in spirit to
| the employment exams that some companies have in Japan during
| job-hunting season for upper-level college students.
|
| So, aiming for a FAANG position, as well as software
| engineering positions at many other companies in Silicon
| Valley, essentially require studying not unlike preparing for
| a GRE subject test for graduate school admissions.
| cubemaster wrote:
| here's the feedback form from the landing page:
| https://docs.google.com/forms/d/1Nqq9xj13ZZHlih16xsTp2Nsl4Zc...
| aster0id wrote:
| Just fyi for the dev - on mobile, the slide in menu that opens on
| clicking the burger icon on the top right is empty.
|
| Cool idea btw. What do you think about incorporating the
| "patterns" associated with problems into the repetition
| algorithm? For example, if I find 2 pointer problems hard, then
| the next 2 pointer problem will be recommended sooner.
| cubemaster wrote:
| yes, was thinking of adding this in! will start adding possible
| features here:
|
| https://alpine-aspen-2ab.notion.site/Lanki-da1481129bfa4d3ca...
| aster0id wrote:
| I can totally see what you're solving for - the friction of
| switching between an anki deck and leetcode to achieve the
| same thing with existing tools.
|
| If you want one data point about how I prepare for coding
| interviews - I just solve Neetcode's list and the blind 75
| list (minus the overlap between the two). For reference I got
| 5 offers in quick succession after being laid off in early
| 2023.
___________________________________________________________________
(page generated 2024-04-26 23:00 UTC)