Learning in Public: My Road to 500+ Problem Solves

Solving hundreds of coding problems was not about motivation. It was about systems.

The shift that mattered

I stopped chasing random hard problems and built a loop:

1. Pick one pattern family for the week.
2. Solve 3 to 5 related problems daily.
3. Write a short note on failed attempts.
4. Re-solve key problems without looking at prior code.

A complex algorithm I finally understood

Segment trees felt intimidating for a long time. The breakthrough came when I stopped memorizing implementation details and focused on invariants:

• each node represents a range,
• combine operation must be associative,
• updates only invalidate the path to root.

Once those three ideas clicked, range query tasks became much less scary.

Why sharing progress helped

Posting my mistakes publicly forced me to explain reasoning, not just answers. That improved interview communication and debugging discipline.

Advice for beginners

Do not optimize for rating first. Optimize for understanding one pattern deeply, then stack patterns over months.