I Gave 2 Hours Daily to DSA & System Design, Best Decision Ever

Summary

In this motivational video, a software engineer shares how dedicating just 2 hours daily to studying DSA (Data Structures and Algorithms) and system design for 31 days transformed their skills and confidence. Despite initial struggles and competing commitments, the author emphasizes the power of consistency over motivation. By following a simple routine of problem-solving and system design practice, they not only gained technical knowledge but also overcame the fear of technical discussions. This story encourages others to commit to steady, daily effort for tangible growth, proving that discipline can lead to lasting results.

Takeaways

• 😀 Consistency is more powerful than motivation for long-term success.
• 😀 Dedicating just two hours a day for 31 days can lead to significant improvement in technical skills.
• 😀 Starting small is key: Even 20% understanding is valuable as long as you build the habit.
• 😀 Setting clear, simple goals (1 hour of DSA, 1 hour of system design) helps stay on track.
• 😀 Daily practice builds confidence, not just in interviews, but in real-world work situations.
• 😀 Understanding concepts deeply (like sliding windows, Kafka, retries) can be achieved through consistency.
• 😀 Motivation is fleeting; discipline and regular, focused effort make lasting progress.
• 😀 Breaking complex topics into smaller, manageable pieces allows for gradual mastery.
• 😀 Shifting from 'I’ve seen this' to 'I understand this' is a rewarding milestone in learning.
• 😀 It’s not about perfection but about showing up and doing the work every day, even when it's tough.
• 😀 Small wins early on (e.g., solving problems faster) lead to greater clarity and enjoyment in learning.

Q & A

Why does the author recommend dedicating two hours a day for 31 days?

The author emphasizes that dedicating two hours a day for 31 days, focusing on DSA and system design, can create lasting improvements without requiring a drastic time commitment. The consistency of showing up daily helps build habits and leads to noticeable growth in technical skills.

What is the significance of the author's 1.5 years of experience in the script?

The author uses their 1.5 years of experience as a back-end developer to illustrate a point: despite having experience, they still struggled with technical concepts like system design and interview preparation. This demonstrates that experience alone isn't always enough without consistent learning and improvement.

How does the author feel about motivation versus discipline?

The author distinguishes between motivation and discipline. While motivation can be fleeting and situational, discipline is about showing up and putting in the work consistently, even when you don’t feel like it. The author credits discipline as the key to long-term success, rather than relying on short-term bursts of motivation.

Why does the author suggest starting with simple tasks like lead code problems or system design concepts?

The author recommends starting with manageable tasks, such as solving simple lead code problems and focusing on core system design concepts, because they help build a foundation of knowledge. By focusing on small wins, learners can gradually progress to more complex problems and concepts without feeling overwhelmed.

What is the purpose of tracking daily progress and taking notes?

Tracking progress and taking notes allows the author to reinforce learning and understand what works and what doesn’t. Writing down concepts and summarizing them in their own words ensures deeper comprehension and creates a tangible record of their progress.

How does the author describe the transformation from week one to week four?

The author describes their transformation as gradual but profound. In the first week, they were struggling with basic concepts, but by the fourth week, they had built enough confidence and knowledge to contribute meaningfully in meetings, explain technical concepts clearly, and write cleaner code. This shift reflects the power of consistent effort over time.

What is the 'small decision' the author refers to that led to big changes?

The 'small decision' refers to the author's commitment to dedicate two hours a day, every day for 31 days, to learning DSA and system design. This consistent effort, despite being a small daily investment, had a transformative impact on their skills and confidence.

What advice does the author give to those who feel stuck in their careers?

The author advises people who feel stuck, particularly those with 1-2 years of experience, to stop waiting for the 'perfect time' or a course. Instead, they should commit to two hours of focused study every day for a month, which can help them overcome obstacles and make significant progress.

What is the author's perspective on system design and its role in their growth?

The author views system design as a critical skill that was previously unclear to them. By dedicating time to understanding concepts like message queues, Kafka, and retry mechanisms, they gained the ability to not only comprehend but also explain system design concepts confidently, even in real-world work situations.

Why does the author mention feeling 'lost' in meetings and what changed over time?

Initially, the author felt 'lost' in meetings because they couldn't explain concepts clearly or confidently. Over time, as they consistently worked on DSA and system design, their understanding deepened, and they gained the confidence to speak up in meetings, offer suggestions, and explain complex ideas without relying on external resources.