Don't start coding before watching this! | Must watch for beginners! | Coding Mistakes 😩

Summary

In this video, Nishant Chahar addresses common mistakes beginners make in coding, such as memorizing syntax and multitasking, and emphasizes the importance of understanding logic, following a structured learning approach, and continuous practice. He advises against seeking the 'best' programming language and highlights the value of community support, creating projects, and maintaining a problem-solving mindset. Chahar encourages patience, as improvement in coding is gradual and compares the learning process to a marathon, urging viewers to persevere.

Takeaways

• 😀 Understand logic, don't memorize – coding is about understanding how and why things work.
• 🔄 Avoid multitasking – focus on one topic at a time to improve retention and mastery.
• 🔧 Problem-solving is the core of coding – practice this skill to become a better coder.
• 🏋️‍♂️ Don't quit too soon – coding requires persistence, much like going to the gym.
• 🛠 Make projects, avoid tutorial hell – apply your knowledge through small projects to solidify your learning.
• 👨‍💻 Connect with peers – working with others or joining coding communities helps you stay motivated and resolve doubts.
• 💻 No best programming language – focus on learning one language well before exploring others.
• 📝 Practice dry runs – running your code manually helps you spot mistakes and improve your problem-solving approach.
• 🌐 Share your progress publicly – post projects on GitHub and LinkedIn to build your portfolio and network.
• 🏃‍♂️ Coding is a marathon, not a sprint – take your time to grow and develop as a programmer.

Q & A

What is the biggest mistake beginners make when learning to code?

The biggest mistake beginners make is trying to memorize concepts. Instead, they should focus on understanding the logic behind coding and how things work.

Why is multitasking discouraged when learning coding?

Multitasking is discouraged because juggling multiple topics, like learning several programming languages at once, prevents deep understanding. It's better to follow a structured approach, focusing on one thing at a time.

What does the speaker mean by 'tutorial hell'?

Tutorial hell refers to watching many tutorials without applying the knowledge. Even after going through numerous tutorials, beginners may struggle to complete practical tasks like building a simple project.

Why does the speaker emphasize the importance of practice for at least 6 months to a year?

Coding requires consistent practice over time. In the first few months, progress may be slow or not immediately visible, but continuous effort leads to gradual and exponential improvement.

What are dry runs, and why are they important in coding?

A dry run involves manually walking through the logic of code to identify errors and better understand the solution. It helps improve problem-solving skills and reduces mistakes during coding.

How can public learning on GitHub and LinkedIn benefit a coding career?

Publicly sharing projects on GitHub and LinkedIn builds a portfolio, which can attract potential employers and help create a professional network. It also demonstrates initiative and progress.

Why does the speaker discourage beginners from asking for the 'best' programming language?

There is no single 'best' programming language. Beginners should start with one language, master it, and then explore others as needed for different use cases.

How does problem-solving mindset play a role in becoming a successful coder?

A problem-solving mindset is key because coding is not just about learning syntax but about breaking down complex problems into smaller, manageable parts and finding effective solutions.

What analogy does the speaker use to explain the learning process in coding?

The speaker compares coding to going to the gym: just as physical progress takes months of consistent effort, coding improvement happens gradually with continuous practice over time.

What key message does the speaker give about the pace of learning to code?

The speaker advises against rushing. Learning to code is a marathon, not a sprint. It’s important to be patient, make mistakes, and continue improving over time.

Outlines

00:00

🚀 Mistakes Beginners Make in Coding

The speaker opens by addressing the common mistakes beginners make when learning to code, such as starting incorrectly and getting demotivated. He emphasizes the importance of learning from these mistakes and introduces himself as Nishant Chahar. He encourages viewers to stay until the end of the video and engage in the comments section by sharing their struggles. Before diving into the tips, he makes an announcement about a new DSA (Data Structures and Algorithms) course, promoting the benefits of learning with his Cohort 5. He also offers structured coding resources through AlgoPrepX for various development courses and stresses the importance of enrolling soon due to limited offers.

05:03

🧠 Don't Memorize, Understand the Logic

The first major mistake beginners make is trying to memorize syntax instead of understanding the logic behind it. Nishant emphasizes the importance of comprehending how and why things work in coding, which makes problem-solving easier. He advises learners to focus on creating logic and solving problems rather than rote learning. The second mistake is multitasking—he warns against juggling multiple programming languages or concepts at once, recommending a structured learning approach. He suggests following a language-first strategy, mastering basics before moving to advanced topics.

👥 Find Support and Don't Work Alone

Nishant highlights the challenges of coding alone, stating that coding requires consistent practice over months to see progress. He suggests joining coding groups or online communities like Discord to find support. He recommends enrolling in courses such as AlgoPrep's DSA Cohort 5 to connect with a peer group on WhatsApp. He stresses the importance of problem-solving and continuous learning with a structured approach, avoiding the trap of trying to learn too many things at once.

🔍 Pick One Language and Avoid Tutorial Hell

There’s no 'best' programming language, and beginners shouldn't get caught up in debates about which one to learn first. Nishant advises picking a language that feels comfortable, mastering it, and then moving on to others. He also warns against falling into 'tutorial hell,' where learners watch many tutorials without actually building anything. To combat this, he suggests creating small projects, such as an expense tracker, to solidify what you’ve learned.

💪 Don't Give Up Too Early

The speaker urges beginners not to quit coding too early. Many give up within the first month, but he explains that initial struggles are normal and progress takes time. He compares learning to code with going to the gym, where you don’t see immediate results but gradual improvements over months. The key is to keep practicing, and eventually, progress will accelerate exponentially. Coding is a long-term journey, and patience is essential.

📝 The Importance of Dry Runs

Nishant discusses how dry runs—manually stepping through your code—are vital in understanding mistakes and improving problem-solving skills. He warns against the habit of submitting solutions repeatedly without understanding the errors, a common issue on coding platforms like LeetCode. Dry runs help map out the logic and can be especially useful during coding interviews.

🌐 Share Your Learning Publicly

The speaker encourages learners to share their projects and coding progress on platforms like GitHub and LinkedIn. By making their work public, they can build a portfolio, network with others, and gain recognition in the programming community. This also motivates others and helps learners get feedback from the broader coding world. He invites viewers to share their thoughts about the video on social media, emphasizing that public learning can help develop connections.

🧩 Develop a Problem-Solving Mindset

Programming is not just about learning syntax or libraries but developing a strong problem-solving mindset. Nishant advises breaking down larger problems into smaller challenges and treating coding as a problem-solving exercise. He cautions against focusing only on learning new tools and libraries, as true coding skills come from solving real problems.

⏳ Take Your Time, Coding is a Marathon

Nishant wraps up the video by reminding viewers that coding is a long-term process. Progress takes time, just like a tree that grows slowly or a gym routine that doesn’t show immediate results. He quotes Bill Gates, who said that people often overestimate what they can achieve in one year but underestimate what they can achieve in ten. He emphasizes the importance of continuous learning, patience, and the mindset that coding is a lifelong journey, not a sprint. He ends the video with a motivational message to keep learning and improving.

Keywords

💡Coding

Coding is the process of writing instructions in a language that computers can understand. It is the foundation of software development and is essential for creating applications, websites, and other digital products. In the video, coding is the central theme, with the speaker discussing common mistakes beginners make when learning to code and offering advice on how to overcome these challenges.

💡Data Structures and Algorithms (DSA)

Data Structures and Algorithms (DSA) are fundamental concepts in computer science that deal with organizing and manipulating data efficiently. In the script, DSA is highlighted as crucial for coding beginners, with the speaker mentioning a specific course that has helped many students succeed in interviews at top tech companies.

💡Problem-solving

Problem-solving in the context of coding refers to the ability to analyze a problem and come up with a logical solution using programming concepts. The video emphasizes that problem-solving is the most crucial part of coding, and understanding the logic behind programming constructs is more important than memorization.

💡Multitasking

Multitasking, as used in the video, refers to the practice of trying to learn multiple programming languages or concepts at once, which can lead to confusion and ineffective learning. The speaker advises against multitasking and suggests a structured approach to learning one thing at a time.

💡Structured approach

A structured approach in learning coding involves a step-by-step method, starting with basics and gradually moving to more complex topics. The video script mentions the importance of a structured approach to avoid feeling overwhelmed and to ensure a solid foundation in coding.

💡Coding groups

Coding groups are communities where individuals come together to learn, discuss, and solve coding problems. The video script suggests that being part of a coding group can be very useful, especially when learning alone can lead to frustration and quitting.

💡Best programming language

The concept of the 'best programming language' is addressed in the video as a common misconception. The speaker clarifies that there is no single best language and that it's more important to learn one well and then it becomes easier to pick up others based on different use cases.

💡Tutorial hell

Tutorial hell is a term used in the video to describe the feeling of watching many tutorials without being able to apply the knowledge practically. The speaker recommends creating projects as a way to avoid tutorial hell and to ensure that learning translates into practical skills.

💡Dry runs

Dry runs refer to the practice of going through a coding problem or solution mentally or on paper before writing actual code. The video script highlights the importance of dry runs for identifying mistakes and improving problem-solving skills in coding interviews and assessments.

💡Public learning

Public learning involves sharing one's coding projects and progress with others, often through platforms like GitHub and LinkedIn. The video encourages public learning as a way to strengthen one's portfolio, network with others, and showcase one's skills and progress in coding.

💡Problem-solving mindset

A problem-solving mindset is an attitude of approaching challenges with the intent to find solutions. In the context of the video, developing a problem-solving mindset is crucial for becoming an effective coder, as it involves breaking down complex problems into smaller, manageable parts and addressing them systematically.

💡Patience

Patience is emphasized in the video as a key attribute for learning to code, drawing a comparison to a marathon rather than a sprint. The speaker advises against expecting immediate results and encourages a long-term perspective, similar to the gradual growth of a bamboo tree.

Highlights

Most people start coding the wrong way, leading to frustration and quitting.

Avoid memorizing coding syntax; focus on understanding logic and how things work.

Multitasking is ineffective when learning coding; follow a structured approach.

To master a subject, learn basics first before jumping into advanced topics.

Coding requires continuous practice for 6 months to a year to see improvements.

Joining peer groups or coding communities can help resolve doubts and maintain motivation.

There is no single 'best' programming language; start with one, learn it well, and then expand.

Avoid 'tutorial hell'; watching multiple tutorials without practice won't help you learn.

Don’t quit coding too early; initial struggles are normal, and improvement comes with practice.

Dry runs of code are essential for identifying mistakes and improving problem-solving.

Share your coding projects on GitHub and LinkedIn to strengthen your portfolio and network.

Develop a problem-solving mindset; real coding skills come from solving problems step by step.

Don't rush the learning process; coding, like building a strong foundation, takes time.

Coding is a marathon, not a sprint; continuously improve and code throughout your career.

Bill Gates: People overestimate what they can do in one year and underestimate what they can do in ten years.

Transcripts

If you are starting coding without knowing these things, then you are wasting your time.

Most people start in the wrong way, get frustrated along the way, and end up quitting.

In today's video, I will tell you about the mistakes that beginners commonly make,

which lead them to feel demotivated and give up on coding.

Trust me, this video is going to be a lifesaver for you, so be sure to watch until the end.

Now, let's get started.

Hi guys, I am Nishant Chahar.

Welcome back to the channel.

Before we dive into the video, quickly tell me: what is your biggest struggle in coding?

And at the end of the video, comment on which mistake you have made or which mistake you relate to the most.

I am very excited to read your experiences in the comment section, so do leave a comment.

Now, let's start the video.

There is an important announcement for everyone watching this video.

If you are learning how to code, data structures and algorithms (DSA) are going to be very important.

We have launched our Cohort 5 of DSA, and we have already taught around 5,000 students.

Many have successfully cracked interviews at companies like Google, Amazon, and Microsoft.

If you want to see the reviews, you can check out our website.

There are many amazing reviews.

So, increase the pace and definitely check it out and enroll.

The price is Rs. 4,500, including GST.

You don't need to pay anything separately.

The early bird offer is ending soon, so enroll quickly.

If you want a recorded version of all the courses—whether it’s LLD, development, DevOps,

back-end, front-end, DSA, or anything else—you can find it on AlgoPrepX.

You’ll get it in a structured format and also get the questions on the same platform.

You can even practice development problems.

So, go quickly and check it out.

Let's start the video .The biggest mistake people make is memorizing things.

You don’t have to memorize anything in coding.

You need to learn and understand the logic.

You should understand how things work and why they are used.

Instead of memorizing

syntax and concepts like loops, conditions, breaks, and others, focus on understanding their purpose and application.

Once you grasp these concepts, it will be easier for you to create logic and solve problems.

Problem-solving is the most crucial part of coding.

The second mistake is multitasking.

Do one thing at a time; don’t juggle multiple things simultaneously.

Multitasking is not effective when learning new things.

Beginners often say, “Today I’m studying DSA,

tomorrow I’ll study Python, the day after I’ll study C++, then I’ll learn React, followed by HTML, then JavaScript.”

Because of this, you end up learning nothing.

Follow a structured approach.

For example, if you want to learn DSA, start by learning a language,

then basic syntax, followed by arrays, strings, and so on.

If you are learning web development,

start with HTML, JavaScript, CSS, basic projects, and then move on to React.

Jumping directly into advanced topics without mastering the basics will not work.

If you want resources or a roadmap, there will be a 90-day roadmap for DSA in the i Button, along with a list of free resources.

This will help you study for free if you are interested in development, cloud, AI, or anything else.

When working alone, it’s easy to get frustrated and give up.

Coding requires continuous practice for at least 6 months to a year.

You will encounter doubts and problems that need to be resolved.

Coding groups or peer groups are very useful.

If you’re in a good college, connect with your peers.

If not, join Discord

or enroll in courses where you can find like-minded peers.

Definitely check out AlgoPrep's Cohort 5 for DSA.

You will join a community on WhatsApp where you can ask questions and get help from others and instructors.

You can check the launch video from i Button for better understanding.

The fourth mistake is asking for the best programming language.

there is no single "best" programming language.

Start with one language, learn

it well, and then it will be easier to pick up other languages.

Different languages have different use cases.

For web apps, learn JavaScript.

For iOS apps, learn Swift.

For Android apps, learn Kotlin and Java.

PHP was used for the back-end of Facebook, and React is popular.

Along with that, your JavaScript is being used a lot.

Now, whatever language you understand well, whatever language is easy

for you to learn, you should start with that language.

That is the best language.

So don't get caught up in the debate about which is the best programming language.

If you pick one, learn it well.

After that, you can jump to another language.

The fifth problem that comes is tutorial hell.

I have faced this myself, and many of my friends have also faced it.

What does this mean?

You have seen many tutorials—50 to 60 tutorials.

After watching them, you feel that you know that thing.

For example, you learned Python.

You watched the entire tutorial on Python.

And finally, when a friend asked you to make a calculator in Python, you couldn't do it.

This is called tutorial hell.

So whenever you are learning something, it becomes very important to make projects.

Try to create small projects, mini projects.

For example, if you are learning web development, you can create an expense tracker.

What is an expense tracker?

It will show you where you have spent your money.

People typically use Excel sheets for this, but you can build your own app for it.

The sixth point is, please don’t quit too early.

Generally, people try for 10 to 15 days, try for a month, and then give up.

The same problems occur with all beginners.

It is difficult at the beginning, and it was the same case with me.

At that time, it may feel like coding is not for you, but it’s just problem solving.

The more you practice and try, the better you will become.

So don’t quit too early.

Do your best, try to solve problems, and things will start improving.

A simple example: when you go to the gym, for at least 3 to 6 months, you won’t see any changes in your body.

The same is true for coding.

When you start practicing, for the first 3 to 6 months, you might

not even know if you are improving.

But then, your progress will suddenly accelerate.

Slowly, gradually, and then exponentially, you will start to see significant improvements.

So don’t give up quickly.

Keep practicing, and you will learn effectively.

The seventh point is the importance of dry runs.

Generally, whenever you are giving a coding interview,

practicing coding questions online, or taking an online assessment, dry runs become very important.

During interviews, you will be asked to do a dry run.

This will help you identify your mistakes.

On platforms like LeetCode, people often keep submitting solutions without understanding their mistakes.

You can’t learn this way.

So whenever you write any code or devise a solution to a problem,

you should definitely try a dry run.

For example, if you’re working on a palindrome check,

make a mind map on paper: first this will happen, then this, then this, and so on until you reach the solution.

It becomes quite easy to translate this into code.

This will help you resolve errors and understand

how much your problem-solving ability is improving.

The eighth point is public learning via GitHub and LinkedIn.

Share your learnings publicly.

If you’ve made a game, share it.

If you’ve completed a challenge, share it.

If you’ve completed a challenge, share it on GitHub.

Additionally, post it on LinkedIn.

This will benefit you greatly.

If you’re watching this video until now, you can post that you’ve learned a lot.

You can share on LinkedIn that Nishant’s video was very helpful.

I would

appreciate it and be motivated to make more such videos for you.

Keep posting on LinkedIn or GitHub.

This will strengthen your portfolio and make it easier to network.

When you send connection requests,

people will check your profile and see your projects.

It makes it easier to make connections.

The ninth point is developing a problem-solving mindset.

The real fun of programming comes when you are solving problems.

By just learning syntax and libraries, you won’t become a real coder or problem solver.

Software engineering is all about problem solving.

Many people learn lots of libraries

and syntax but can’t become good programmers or developers.

You need to work on your problem-solving ability.

Solve problems, break them down step by step,

and learn how to address smaller issues to solve the larger problem.

Treat every coding problem as a challenge.

Break it down into smaller challenges and try to solve them.

The final and most important thing is not to rush.

There is a process, and it takes time.

Just like a tree takes time to grow, if you know bamboo, it stays in the ground for 5 to 6 years before it starts growing.

Learning something new also takes time.

Don’t expect to master it immediately.

Similar to going to the gym: if you are trying to build your body, you won’t see results immediately.

It will take time.

Bill Gates said a very good thing: people overestimate

what they can do in one year and underestimate what they can do in ten years.

This applies to coding and any career.

In one year, you might not achieve much, but in ten years,

if you work hard continuously, you’ll see tremendous progress.

If you liked these points, please let me know in the comment section.

Like the video, comment on what your favorite learning from this video was.

Remember, coding is a marathon, not a sprint.

You don’t stop after 100 meters.

It’s a marathon, and you need to keep coding throughout your life if you’ve chosen a software engineering path.

So don’t be afraid.

Learn slowly, make mistakes, and improve yourself.

Thank you so much for watching this video.

I hope you liked it.

Like, subscribe, and see you in the next video.

Till then, bye.