s
Start Teaching
Messages
User
Back to Stories
7 Mistakes to Avoid as a Software Developer
Technology
  • Mar 26, 2021
  • 10 minutes

7 Mistakes to Avoid as a Software Developer


If your interest and competence in computers are at a high level and you have convinced yourself that you can do this job, you are on the right track. However, sometimes things happen that we skip.

Unless we do these, we move away from the definition of a good software developer. I’ve compiled a few features that a good software developer shouldn’t have.

1. Living addicted to perfection.

It is everyone’s dream to live a complete life where everything goes perfectly. But when a software developer wants to write a great project, they stumble. Because they will see mistakes and deficiencies. Thus, with a waste of time, they can never focus on that part.

Medium-level projects, like everything else in life, continue their life process at a normal level. In other words, they up to the mark good or bad. Perfection often makes you question yourself and your project. Perhaps it will delay you from accessing the project you want.

2. Postponing things to do

The days pass like this when we postpone a job we do, and it becomes more and more difficult to do that job day by day. The job gets bigger because the work to be done at the beginning of the project and the work to be done afterward are different. The cost of time will gradually increase.

When you postpone the job, your mind will always stay in that job, you will do the other job you decide to do with lower performance. Saying “I’ll do this later, I just want this code to run right now” will cost you time.

Software developers love hard work. Even if things seem easy, they postpone them for a break. However, it is not enough for the software developer to do this job well. This is concentration work, and your life should be orderly. Regular sleep and regular nutrition are also very effective in this regard.

3. Trying to reach the result immediately

Are you familiar with the circle that Noel Tichy describes for personal growth?


 


To improve ourselves, we need to get out of the Comfort Zone and enter the Learning Zone. Unfortunately, this is not that easy. First, getting out of the Comfort Zone means going into the unknown. The individual can instinctively resist this because this transition can create uneasiness within the individual. Also, this transition can be very challenging for the individual mentally and spiritually. Second, the location of the Learning Zone is constantly changing. It is not easy to predict when you are in the Learning Zone and when you are in the Panic Zone.

When we look up at a gigantic master, the question arises as to how did this man/woman have such talent, knowledge, and skill. At the same time, we see how small we are ourselves next to this giant, and we get lost next to it without even looking for a place to hide.

Were famous software developers born as masters? Or are they ultra-smart? If so, why are they and not me or you? The answer to these questions is easier than we think. They are no different from you and me. We have the same physiological characteristics. There is one thing that makes them different: they paid the price of being masters.

4. Thinking about working long hours is beneficial

This situation depends on the programmer. Some programmers prefer to work long hours and are motivated that way. But think about it, you can find a solution that you haven’t found for long hours, soon after you take a break.
Instead, my preference is to take a break every 2–3 hours. Also, getting something to drink allows us to get up and move. Thus, it is easier to find solutions to problems.

5. Writing code as no one else would ever check

It could be you, a colleague, a new employee, or even a developer working at another company, but someone will have to maintain your code or add extra functions.

This item is somewhat difficult to understand as most junior developers are used in projects where only one person writes code and has a classic university project approach with no one else involved.

The situation is a little different in a professional environment; You will be asked to write code in a project written years ago, and your code will need to be ready for the “next person” to come in a few years.

Take time to review your code every few hours. Add necessary documentation to README files, delete files you temporarily added to the project, and unused code. If you have difficulty when you need to decide on an architectural or programming issue, contact someone more experienced in your work environment. Not only will you improve the state of your code, but you will also be better at dealing with similar situations in the future.

6. Not listening to others and not getting help

People should not hesitate to help and ask for help. It is very important to seek help with an issue we do not know.

If you don’t ask questions will cause a waste of time. In my first job experience, I was afraid to ask questions because I felt stupid. This caused me to delay 2 months to understand the issue. My boss had mentioned that this is not true, and he said that asking effective questions improves people.

When you start to listen to what others have to say, you educate yourself and improve your way of thinking thus making yourself more knowledgeable. This in turn makes you a better developer. If you don’t like listening to people, you will always remain a bad developer regardless of how much time you spend coding in a language.

For any platform, feel free to ask questions to your senior developer. Asking the right questions shows that you are on the right track.

7. Not Reading the Code

Again, I think it is fine to read the article I’ve written in Better Programming.
Read as much code as possible to learn new information and improve clean code writing.

https://betterprogramming.pub/6-reasons-why-reading-code-is-more-important-than-writing-21e7b0b62203


The main goal of the developer is problem-solving, and for the developer, writing code is a means rather than an end. We can solve a problem we have identified by writing code, but there may be more different and logical solutions for a problem that has always existed.

At this point, you should constantly read different codes to improve your perspective. This will both give you different perspectives and speed up your understanding of the codes written by others when you get a job. The best source for this is open source projects on Github.

Conclusion

Not all work ends by loving this profession. We must analyze our shortcomings and improve them.

Thank you for reading!

Recommended instructors

Find instructors for your goals & budget.