How do you plan and approach your DSA revisions?
Hey everyone!
I'm curious to know how you all approach revising DSA problems after solving them.
Do you follow a sprint-wise approach, revisit problems based on patterns/topics, maintain a revision tracker, or follow something like spaced repetition?
A few things I'd love to hear your thoughts on:
- How frequently do you revisit previously solved problems?
- Do you revise problems topic-wise or follow a fixed schedule?
- How do you decide which problems need more attention?
- Do you maintain notes or revisit the problem and solve it from scratch?
I'm trying to build a consistent and effective revision strategy, especially to retain problem-solving patterns and improve recall during interviews.
Would love to hear about your approaches, experiences, and any tips that have worked well for you!
Thanks in advance!
Recommended Reads
ServiceNow Is Hiring: Senior Software Engineer
ServiceNow is looking for an experienced software engineer to work on enterprise-scale applications and collaboration platforms. The role involves building inte
From SDET to Microsoft Backend Engineer | ₹22 LPA + $40K Stocks
Moving from an SDET role to a backend engineering position at Microsoft is a significant career transition. I’ve received an offer for Software Engineer (Backen
TransUnion Is Hiring: Associate Software Engineer
TransUnion is hiring an Associate Software Engineer for its TruAudience Marketing Solutions team. This is an entry-level full-stack role where you'll work on we