Differences between “lepers” and “genuine” developers. How developers improve themselves.

Tram Ho

Programmers, a fairly hot profession in the context of Industry 4.0 today. The opportunity is quite open for everyone to become a programmer with abundant resources on the Internet, forums, courses everywhere, … Many opportunities, but also challenging, to become 1 Good developers require a lot of time and effort to “plug in the front of the computer screen”. So, sometimes, people say this job is in the top of the most toxic professions.

After many foolish times, fumbling with silly errors, I changed little by little my thoughts. Therefore, in order to have a bigger change, I decided to search google, learn the thoughts of the people left before, see how to apply it to improve myself. And here are 8 things I’ve found and summarized.

1. Never stop learning new things

The first step to learning something new is to get rid of everything you already know about it. It’s a bit weird, but experienced programmers find it a waste of long time to overcome the “I know everything” idea.

2. Stop, don’t try to prove you right

When someone reproaches your code, don’t try to explain how good the code is but think: “How do I make it better?” An amateur hand looks at his code and sees it “top”. They write tests to prove that the code is correct instead of being a bug. In contrast, Professional is always looking for what they are wrong, because they know, one day users will find what they have missed.

3. The operation code is not the end, it is just the starting point

The first step should be to write code that fulfills the requirements. When this score is reached:

  • Amateur often stops playing here, assuming everything is ok and move on to the next job.
  • Professional knows it’s only step one. The next step they figured out how to make it better. They constantly ask the question: How to make the program run faster, the code easier to read, easier to reuse?

4. Write the code 3 times

Ordinary people write code to run it, Professional write code to make it perfect and that rarely happens in the first place. A good software is usually coded 3 times:

  • For the first time, coding aims to prove the solution feasible. Aside from the programmer, it may not be easy for others to realize that the program is just proof-of-concept.
  • Second, write code to run the program.
  • Last 3, write code to run it correctly.

For good programmers, the steps may not be as obvious as they can do more in 1 step. However, they often discard the first or the second version before releasing their products. Because, for them, rewriting code helps to approach many problems and also prevents falling into a dead end.

5. Read a lot of code

Many people think that this is a valuable way to improve the coder. When you read a lot of other people’s code, you learn – The different ways of writing code, help improve the ability to understand your teammates’ code when you teamwork. And moreover, whether this coding technique should be avoided or should be learned, how to apply it to your project.

  • Different approaches to the problem, whether this person’s solution is better than yours, can be applied?

Always ask yourself these things, that’s how you assess your strengths and weaknesses.

Warning: Many programmers who need to solve a problem often find the code of other people and then copy the solution blindly. They just put it in without understanding or evaluating this code. This makes it easier to create bugs, which can take longer than reading documents and solving problems yourself.

6. Personal projects

Personal projects can bring many benefits to you. You learn tools and technologies you didn’t know; if you’re lucky, this knowledge will drive your prices higher in the labor market. At the same time, personal projects prove to your employer that you are constantly learning.

One benefit of personal projects is to help improve your ability to solve problems yourself. There will be no teammates to help with when you code your bugs.

Tip: Don’t choose projects that are likely to succeed, because learning the wrong words will help you gain more experience.

7. Find your teammates

Joining Hackathon, or the developer community, can be helpful. When you contribute code to a project, pay attention to the feedback you receive, which is how to find your own weaknesses. If you are more fortunate, you can find a mentor, who can not only teach you coding but also help you in career decisions. Do not miss that opportunity.

8. Learn technology, do not learn tools

Most programming languages, tools, or technologies just come and go. However, the basic concept will never change. Learning architecture, thought rather than just learning how to program helps you understand the nature of the problem more -> upgrade faster.


Share the news now

Source : Viblo