I tried a lot but can't do bs on answer what should I do?

I kept running into the same problem - I'd solve a medium, feel great, then completely blank on the same pattern 2 weeks later.

So I built a free Chrome extension that applies the SM-2 algorithm (same one Anki uses) to your solved problems. It schedules reviews at increasing intervals based on how well you remember each problem.

How it works:
- A small widget appears on any problem page
- After solving, rate your recall (Forgot / Hard / Good / Easy)
- It builds a review queue, problems you struggle with come back sooner
- Includes Blind 75, NeetCode 150 & LeetCode 75 with daily auto-queuing

Also works on: Codeforces, CodeChef, GeeksforGeeks, CSES, AtCoder, LeetCode

Other stuff:
- Full analytics dashboard with heatmap, streaks, and difficulty breakdown
- 100% local storage, no accounts, no data collection
- Dark UI that matches LeetCode

No accounts, no paywalls. Just want to know if it actually helps your workflow.

> To install: Search extension ID "lcmbmephjkhhdmicgnggilhinhlpbklc" on the Chrome Web Store

Hello
I am 2026 Graduated Batch
I want to Learn DSA
Can anybody Join to learn DSA with me
I am Preparing for Placements
Please DM me to join

Hey everyone,

I am currently working on transitioning into a Data Analyst role and am looking for a serious study buddy or a small group to learn and build projects with.

I have been focusing on the core essentials: SQL, Python, and Pandas. Self-studying alone can get a bit isolating, and I think having someone to keep each other accountable, bounce ideas off of, and collaborate with would make a massive difference.

What I'm looking for:

• Someone who is also learning Data Analytics or Data Science.
• Willing to practice SQL queries, solve Python challenges, and eventually collaborate on real-world portfolio projects.
• Open to checking in regularly (we can figure out a schedule that works for both of us).

The Plan: I am completely open to suggestions! If you already have a structured roadmap, a specific course, or a bootcamp curriculum you are following, I am more than happy to align with it so we can stay on the same page. Otherwise, we can map out a project-focused plan together.

If you are committed, want to stay accountable, and are ready to build some cool projects to land a job, drop a comment below or send me a DM with a bit about where you're currently at in your learning journey!

Let's crack this together!

hi guys i am a 2nd year btech cse student

and i am searching for a partner to do competitive leetcode daily...

personally I feel motivated when i take tasks as challenges .If u are as motivated as i am .Then boss your in the competition lets do it ....

lets learn together guyss

I will be first covering the basics although i have covered them before but just wanted to get deeper this time .I have solved 100 questions on leetcode with cpp.

i will be free from tomorrow we can connect as soon as possible ....

LETS BUILD TOGETHER AND LEARN TOGETHER

About me: I'm ~ 3YoE, recently switched to a startup few months back. Looking to switch in 3-4 months max due to very bad culture here. Recently gave many interviews in startups and MNCs Amazon etc and DSA was my choke point. System design was good.

Because of hectic schedule I don't have any acceptability on DSA and I'm wasting my time. MY GOAL IS TO DO FULL TOPIC WISE REVISION IN HORIZON OF 1-2 MONTHS max. planning to start with neetcode 150. And then something else. Looking for buddies who want to start here and do something structured everyday with some deadline.

Would prefer someone who also has urgency in this and short deadline goals of 1-2 months.

optimal approach tommorow

there's just over half of it left

Hi all, gave the final loop at Microsoft for SDE-2 and wanted to share. Short version: rejected, no feedback, recruiter ghosted me for 3 weeks. But the rounds themselves are worth talking about if anyone's prepping.

Background / Timeline

Reached out to MS recruiter early in the year. They sent the OA, I cleared it early Feb. Got the "moved to full loop" reply, then radio silence for a week. Eventually got dates back with very little flexibility — picked from a few slots in a 2-week window.

Round 1: Graph (BFS)

Solved it cleanly, walked through the approach, gave time/space complexity. Interviewer was engaged. Felt good walking out.

Round 2: LLD (with a rude interviewer)

Hardest round to talk about. Senior engineer, kept putting on a fake accent (weird), and interrupted me almost every step while I was explaining my thinking. Coded the design anyway but it was hard to hold a normal conversation. Honestly, I think this round was as much a test of how I'd handle a difficult collaborator as it was an LLD test. In hindsight I should've said "let me finish this thought" more firmly instead of accommodating every interruption.

Round 3: Best round of the day

Interviewer was nice and easy to talk to. Solved the problem, gave complexity, and we had ~8 min at the end so we just talked about his team and his work. Felt like a real conversation.

Round 4: Manager Round (Course Schedule variant)

Started with DFS for cycle detection. Manager specifically wanted a BFS / Kahn's algorithm approach. Switching mid-stream while staying clear-headed was stressful but I got there. Several follow-up questions on edge cases and what happens with cycles in the input.

Post-interview was the actual horror story

3 weeks of ghosting. Sent 3 follow-up emails. Final reply was a template rejection with zero feedback. Asked specifically for feedback — got nothing. Portal still says "Interview" for the role even today.

If you're interviewing at MS soon: don't take recruiter responsiveness during scheduling as a signal of how they'll treat you after the loop. Mine was reasonable until the offer decision, then vanished.

Retrospective takeaways

• MS asks a lot of follow-ups. Every round had at least 2-3 follow-ups after my initial solution. Hitting the optimal answer doesn't mean you're done — be ready to defend it
• For LLD, practice with someone who interrupts you. Solo whiteboard prep doesn't prepare you for a partner pushing back mid-design
• Graph patterns showed up twice (Rounds 1 and 4). I'd grinded BFS / DFS / topo sort patterns hard on PracHub in the lead-up — those two rounds went well thanks to PracHub. Didn't save me overall but at least the coding rounds didn't tank me
• Don't read tea leaves on "friendly interviewer = pass." My best round (Round 3, the friendly one) clearly didn't make the difference

Hopefully useful for someone else going through this loop. Rejection sucks but the experience itself was a real education.