GrindLens

Your solved count tells you how far you've gone. GrindLens tells you what you're missing and what to solve next.

[GrindLens @grindlensdev]

real test: don't look at your solved list or your notes.

name 3 patterns you've actually practiced and still get stuck on.

not the ones you haven't touched. the ones you've solved before and still mess up.

harder than it sounds.

[GrindLens @grindlensdev]

just solved one binary search problem.

GrindLens already flagged it as a pattern to work on and lined up 3 more, easy, medium, hard.

not "here's 50 problems," just the next 3.

[GrindLens @grindlensdev]

"i've seen this pattern before" felt like the same thing as "i can solve this pattern."

it is not the same thing. not even close.

[GrindLens @grindlensdev]

kept asking myself "how many have i solved."

wrong question. the one that actually moves you forward is "what should i solve next."

one's a number. the other's a decision.

[GrindLens @grindlensdev]

finished a whole sheet once. felt done.

then someone asked me what i was actually weak at.

i had no idea. the sheet never told me.

[GrindLens @grindlensdev]

5 problems solved ≠ you know the pattern.

5 problems solved + repeatedly getting stuck on the same concept = different story.

[GrindLens @grindlensdev]

most people track how many leetcode problems they solved.

almost nobody tracks how many times they failed on the same pattern.

that second number is usually more useful.

https://t.co/7jhG7eJEh6

[GrindLens @grindlensdev]

@Gennz_01 indeed'

[GrindLens @grindlensdev]

you can solve hundreds of leetcode problems

and still not know what you’re actually weak at.

that’s the gap we’re trying to close.

not just how many you’ve solved -

what you’re weak at, where the gaps are, and what to practice next.

https://t.co/7jhG7eJEh6

[GrindLens @grindlensdev]

@nkcbuilds yeah, less goo'