Back in 2018, my coding journey started. After over 5 years of coding, I believe I can provide my point of view. At first, it was delightful. I marveled at the results that R could produce. Mind you, this was the first time that I had written code! Typing a command and getting results was gratifying. I could have a positive influence on the society.
I remember writing my first “Hello World” and watching it print on the screen—it felt like I had unlocked a superpower. Fast forward five years, and while the excitement hasn’t completely faded, the harsh truths have surfaced.
1. You Never Feel Like You Know Enough
It doesn’t matter how many languages you’ve learned or projects you’ve shipped—imposter syndrome still sneaks in. There’s always someone using a framework you’ve never heard of, building faster, better, cleaner. The field evolves at a ridiculous pace, and you often feel like you’re one tech article away from being outdated. Even After over 5 years of coding, I still like I don’t know enough.
2. Tutorials Can Trap You
IT people are known to have a lot of certifications. Go through LinkedIn and browse for Careers such as Data scientists, AI engineers, or even IT professionals. You would be surprised.
Yeap! Tutorials are good. They are good, especially if you want to learn a language. But there’s a fine line between learning and tutorial hell. I spent months following tutorials without building anything real. The result? I knew how to follow steps but couldn’t solve real-world problems.
Another reason I suggest not going for too many tutorials or certifications is that you are learning to code to solve real problems. Pursuing a certification or a course might be rewarding and/or a good option. But it should be supplemented with real-life experience. This can be done through real-life projects.
I am not advocating against certificates in any way. Try to balance them. Have good projects on your portfolio.
3. You’ll Doubt Your Career More Than Once
At some point in my 5 years of coding, I stare at my screen, frustrated, and think, “Maybe I’m not cut out for this.” It happens. The bugs, the pressure, and the solitude can make you question your path. But here’s the thing: doubt is part of growth. The key is pushing through and solving one problem at a time.
4. Coding Alone Won’t Get You Far
Writing clean code matters, but communication, collaboration, and problem-solving are often more critical. Some of the best developers I’ve met weren’t the fastest coders but the best team players, thinkers, and listeners.
Similarly, knowing just one language or tool isn’t enough anymore. Today’s job market often demands a tech stack—not just Python, but also SQL, Git, Docker, APIs, maybe a bit of JavaScript, and even tools like Tableau or Power BI if you’re in data. It’s less about being a master of one and more about being adaptable, willing to learn, and able to understand how different pieces fit together to solve real problems.
5. Coding is a tool
You have heard of the term you should learn one programming language. The point that I want to make here is language. Why a language? You are talking to a computer and telling it what to do. As such, you must know what you are doing and how you will achieve it, then say to a computer.
6. Constant learning never stops
We started with the impostor syndrome, But here is more to the fact that once in this field. You will always be learning. Things change at a fast pace. Let me go with this example of Langchain in the field I know well. Not less more than a year ago, Langchain was widely used as an AI agent. But companies are shifting. If you have mastered Langchain, you must learn about a new AI agent.
Conclusion: The Beauty in the Struggle
Over five years in, I’ve learned more from my failures than my successes. Coding is not glamorous—it’s messy, frustrating, and sometimes thankless. But it’s also creative, empowering, and fulfilling. If you’re new to coding or in the thick of it, know this: the harsh truths are fundamental, but so is the growth.
Keep going. The keyboard’s your canvas.