You’ve gone on a coding journey, you’ve gone down many paths, you’ve gone wrong many times, you want to know what’s next, and there are more questions to be asked. But as a human being, we are bound to make mistakes. As a result, novice or novice programmers make mistakes just like before.

You have too much on your plate

If you have a problem with C/C++ one item is a very enthusiastic one (● ‘◡’ ●).

Someone said, start with C, now you’re learning C, the second minute you hear C ++, now start learning C ++. The very next day, you read about where Java is popular, and then you jump to it. Someone whispers something and then does something.

Jumping from one thing to another, learning too much and having nowhere to go. This will only make you more stressed.

Focus on one thing at a time, master it, and move on to the next.

If you learn one language correctly, you will easily learn another. It’s a steep learning curve at first, but looking ahead, it grows exponentially, trust me. All programming languages work or behave almost alike, except that they differ in syntax and some internal workings. So don’t overwhelm yourself with too many things. Stay calm and take one step at a time.

New day, new language. As I said in the last paragraph, jump from one thing to another, this time not to learn something new, but to experience firsthand what is popular. It’s good in both cases. After all, curiosity is what sets us apart from the rest of the animal kingdom. But trust me when I start by sticking to one thing and then jumping around and adding new skills.

Not understanding basic knowledge and key knowledge

We can’t move forward unless we understand the basics, and I think that was one of our biggest mistakes in the beginning. Demoralizing and wasting time just from the start. Trust me, improve the basics, and the next advanced element will find its way to you like a river to the sea.

Not following coding standards

Now, I know lists, maps, string manipulation, file manipulation, streams, and all that kind of stuff. I’m writing code, and like hammering nails, life keeps going.

Then one day, while pushing code into production, an old piece of code pops up. I rushed back to the project, looked up the code, took one look, and the only thing I could think of was, “Who wrote this code?” Guess who he is?

I don’t know what that is. Code and comments are out of sync, variables tell a different story from the values they hold, and there are 600 lines of functionality. After about 4-5 hours of debugging, learning the code and cursing myself, I was able to fix the problem. Now that it was time to confess and correct my mistakes, I asked myself if there was a better way.

Improve your coding standards

Utility programmer

Code integrity (developer best Practices)

Code Craft – the practice of writing good Code.

Follow these standards and adapt them to your daily style and daily requirements. It makes your code more maintainable.

Code quality is one of the key things that people most often ignore when coding. I did, too, and learned it the hard way.

The best time to improve your code is after it’s finished

At this point, you know what’s going on in the code. A little push to revisit and then apply coding standards will improve the quality of your code tenfold, rather than a few days later when we forget about the little things.

So, don’t just leave things as they are, reread the code and look for possible cleanups. That way, you’ll be most likely to play the game in the future when everyone is looking for bugs in their code.

I know everything

“I’ve done my assignments and projects, I know everything, I can build anything.” B: Sure. But every day there are new technologies, new ways and better ways to do what you do in your life, and you’re still sleeping and dreaming that you know everything. Wake up, man. We only know to fall in this vast ocean of knowledge. Improve your knowledge level every day.

The modest improvement of one’s knowledge does not diminish it.