You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though there is a "Show/Hide Patterns" slide, it seem that most of the questions are clustered together when they share patterns within a difficulty.
Even though I try not to pay attention to the revealed patterns of the near by questions, I often see them. This gives me a very good hint on how to approach to a problem which I won't have when I will be in an interview.
A shuffle button/slide (some might want to get the original ordering back) would solve that problem since I wouldn't be able to guess the pattern with the ordering randomized.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion @TigerPurrer! I understand what you mean - I'll see if I can pick this up in the next little while! Thanks 😁
Edit: If anyone else comes across this and wants to give it a shot, feel free to! I'm happy to help get things across the finish line if you can get a pull request up (even if it's a WIP one)
I solved this issue... I think.
I didn't want to go into the React source code, so I pretty much just wrote a small UserScript that picks a random problem. Since filtering the table removes the entries from the DOM, the random choice is affected by whatever filters are on at the moment.
Even though there is a "Show/Hide Patterns" slide, it seem that most of the questions are clustered together when they share patterns within a difficulty.
Even though I try not to pay attention to the revealed patterns of the near by questions, I often see them. This gives me a very good hint on how to approach to a problem which I won't have when I will be in an interview.
A shuffle button/slide (some might want to get the original ordering back) would solve that problem since I wouldn't be able to guess the pattern with the ordering randomized.
The text was updated successfully, but these errors were encountered: