Mistakes I made in my Software Engineering career

Mistakes I made in my Software Engineering career

posted 4 min read

I made a lot of mistakes when I was learning to code. But I don't want the same mistakes to be repeated with my juniors; that's why I'm writing this post for you.

1. Not following a structured plan

When, I first started learning to code, I didn't have any structured plan to follow. Due to this, I suffered a lot even in learning frontend development or, to specify more, in learning the fundamentals like Html, CSS and JS. And, that's why it took me a lot of time to learn that.

2. Neglecting the Daily Practice Habit

I first thought that coding wasn't for me because I didn't make a habit of doing practice daily for building logic. So, make sure to practice daily and try to solve as many problems as you can whether you're a beginner or a senior working in the industry.

3. Not taking notes while learning

I didn't have a habit of taking notes; that's why I always struggled to revise the syntax whenever I sat down to solve any problem. So, make sure to take notes properly when you're learning some new topic, whether it's related to coding or something else.

4. Taking long breaks from coding

I wasn't consistent enough to sit and code daily; that's why I had to take the long gaps and due to this, when I started again, I felt like I was falling behind.

5. Focusing only on the syntax

In my early days of coding, I had this bad habit of writing code as soon as I sat down to solve any problem. I always thought to solve the problems using the syntax of the programming language I was using.

6. Comparing my progress with others

At some point, I compared my learning curve with others and thought that I'm not good enough to become a coder. I thought that coding was only for geniuses and thought that I wasn't good enough. But I'm here to tell you that coding may seem easy for geniuses. You, as an average person, will have a steeper learning curve than the rest. Instead of comparing your journey with others, try to learn from others, like how they approach a problem and how they write code. It'll make you a better programmer.

7. Wanted to become master of everything

I wanted to master everything at first, like I thought that you've to learn everything related to some tech. But I was wrong, and now I only focus on fundamentals and leave the rest to later because now I know that I'll learn the concepts when I build some project or if I do something related to that tech afterwards.

8. Not making enough projects

I didn't have the habit of making projects in my career. Now what I do is I try to make at least one project to implement what I've learned.

9. Stuck in tutorial hell

At some point in my career, I was stuck in tutorial hell, and I found myself watching tutorials like a Netflix series and not coding along the tutorial.

Tip: Develop a structured learning plan and stick to it. Dedicate time daily to practice coding, even if it’s just a small portion of your day. Focus on building projects to reinforce what you’ve learned and track your progress. Emphasize problem-solving skills over memorizing syntax, and always challenge yourself with slightly more difficult tasks to grow steadily.
Note: Coding is a marathon, not a sprint. Everyone learns at their own pace, and there’s no single right way to become a skilled programmer. Consistency, patience, and practice are key. Celebrate your milestones, no matter how small, and understand that mistakes are part of the learning process. Always strive to learn from them and move forward.
Caution: Don’t let long breaks, tutorial addiction, or constant comparisons with others derail your progress. Focusing too much on theory or trying to master everything at once can lead to burnout. Skipping practical application through projects or neglecting the habit of daily coding will slow down your growth and leave you feeling stuck.
FAQ How do I create a structured learning plan for coding?
Start by identifying your end goal, such as becoming a web developer, data analyst, or app developer. Break your learning journey into phases—start with the basics (like HTML, CSS, JavaScript), move to intermediate topics (like frameworks or backend programming), and tackle advanced concepts as you progress. Use curated resources like online courses, books, or coding bootcamps to stay on track.

How much time should I dedicate to coding daily?
Consistency matters more than duration. Start with 30 minutes to 1 hour a day, focusing on quality learning. Gradually increase as your schedule allows, but avoid burnout by balancing learning with breaks and other activities.

What’s the best way to take notes while learning?
Use a method that works best for you. Digital tools like Notion or Evernote can help organize code snippets, syntax, and concepts. Alternatively, keep a physical notebook for handwritten notes. Ensure your notes are concise and easy to review later.

Conclusion:

Now that you've read the article till here, listen to my advice carefully. If you're new to coding and thinking of quitting, then don't, because you'll get better with time, and you'll see how far you've come. Additionally, if you find yourself doing any of the mistakes that I mentioned above, then try to avoid them, as they'll stop your progress, and you'll find yourself complaining like I did.

If you want more such posts, then follow me, and don't forget to mention the mistakes that you made in your career.

Stay connected with me - Rumaisa Naveed

Happy Coding & Learning

If you read this far, tweet to the author to show them you care. Tweet a Thanks
I had similar encounter when I started out.
Yeah, it happens in the beginning. But we realize later that how far we've come.

More Posts

How To Create Custom Middlewares in ASP.NET Core

Anton Martyniuk - May 13, 2024

How to Build a Portfolio That Stands Out as a New Developer

Mohammad Yasir - Jan 25

LinkedIn vs. dev.to: What's better for Developers ?

ravixalgorithm - Jan 7

Foundational Algorithmic Paradigms and Advanced Algorithmic Concepts in AI Development

Niladri Das - May 16, 2024

How I optimized slow loading time using service workers in frontend

Nikola Perisic - Jan 7
chevron_left