This content originally appeared on DEV Community and was authored by Peteroums
For many, a programmer is a dream profession. Young (and not so) people storm the admissions offices of technical universities, study video tutorials, and laugh at clever jokes in the “Typical Programmer” communities and the like.
Moreover, many people study programming at universities and training centers, sincerely believing that the cherished crust will open the doors to an exciting profession. Company representatives will line up to get a newly minted specialist in their staff. This is rarely the case. And the reason for this is the mistakes made by the programmers themselves.
I recalled many statements by employers and teachers throughout my programming journey and came up with 5 signs by which they distinguish a good programmer from a bad one.
1. Lack of self-discipline
It has been said many times, but I will repeat it: programming is not only creativity but also hard work that requires perseverance, patience, and the ability to organize your workflow.
Can’t sit in your chair for more than 30 minutes of coding? This is not required — in the end, it can harm your health. Take a break, have some tea. The main thing is functionality — the task must be done, errors must be fixed, and all the code must be clean and up-to-date.
What you can do:
Discipline yourself. Plan time for work and leisure. Read about the Pomodoro technique — it helps many to increase the productivity of personal labor.
2.Going to extremes
I often have to deal with someone else’s code that does not compile. What would a bad programmer do in this case? Erase everything and start writing again. This is fraught with several things:
The risk of aggravating the situation. By the way, an overly self-confident programmer does not like it very much when he is caught by the hand when making a mistake.
Depriving yourself of the opportunity to learn by parsing someone else’s code, even if it is not working. Being able to read another person’s code is a great skill.
What you can do:
Don’t go to extremes. Learn to work autonomously and in a team. Soak up new experiences, even if you consider yourself the coolest programmer on the team.
3.Inability to build algorithms
There is an opinion: a bad programmer immediately writes code, and a good one first builds the architecture of the project. It isn't easy to disagree with this. Over the years of working, I have made sure that as a programmer, I have not developed the habit of carefully considering and structuring the task they face and only then taking on its solution. This also applies to developing a commenting system in PHP, a calculator in Delphi, and even writing the notorious “Hello, World!” on any YP.
Read More :: https://cmsinstallation.blogspot.com/2021/04/how-to-distinguish-good-programmer-from.html
This content originally appeared on DEV Community and was authored by Peteroums
Peteroums | Sciencx (2021-04-28T06:27:23+00:00) Difference between Good developers and Average developers – who you are ? Good Or average ?. Retrieved from https://www.scien.cx/2021/04/28/difference-between-good-developers-and-average-developers-who-you-are-good-or-average/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.