How Can I Stay Consistent With DSA, and When Should I Learn System Design?

Try pairing each topic with a small project that uses the data structure you just learned. It tends to stick much better than solving isolated exercises. For example, build a simple game or tool and deliberately use lists, stacks, queues, trees, or sorting algorithms where they make sense. A practical project also makes it easier to understand why a particular structure exists and when its performance matters.

A good way to make DSA click is to implement something practical instead of filling structures with random values. Small card-game projects are useful because you can build the algorithms yourself and see how the pieces work together. You could also try writing an arithmetic-expression parser to practice trees, operator precedence, and evaluation. For a roadmap, choose one solid algorithms book, work through the chapters in order, and complete the exercises at the end of each chapter. I’d focus primarily on DSA for now, while learning system design gradually through projects; deeper design concepts are easier to understand once you’ve encountered real implementation problems.