Skills that must be owned by the Programmer

Source: freepik.com

Maybe you are asking, if the skills that must be owned by a Programmer are logic, algorithms, and mathematics? No no !! You will be taught about it, but it is not mandatory regarding skills in the field of technology.

Now, my friends NulisTechno, now we will discuss about the skills that are required to have in various fields of technology. Now try cone at the Programmer, there is much to be learned in this field. For example for web developers (web programming) you have to learn things like the picture below:

Source: github.com/kamranahmedse/developer-roadmap/

See, there are so many. Maybe for you beginners, you will think this is a complicated thing, this makes you think that you will not be able to learn all of that, the thinking comes because you do not know or have not mastered the skills that you really must have. So what are you waiting for !! Yuks, see our explanation. So that you are more stable and also easier to master the technology field.

Skills that must be owned by the Programmer

1. English language

Source: freepik.com

Now, what you need to know is that most programming languages ​​and technology languages ​​have developed in English. And that requires you, to learn English. It's okay if you still master passive English (read and hear), it will also help you in understanding commands, programming languages, documentation and modules related to that field. However, you also need to improve these skills. So you can also be active. So this English will make it easier for you to:

• Read and also understand documentation
• Understand every error message in your script
• Ask in global forums
• Learning the web that comes from outside
• Make it easy for you to find references, because many references are in English.

2. Read each Documentation

The documentation itself is a document in which contains explanations about the relevant technology. Of course, this documentation skill is very important and even becomes very mandatory for programmers, because if you cannot understand the purpose of the documentation, you will not understand anything. In general, this documentation is presented in a complicated manner, which is complicated here means that the language is presented using technical language that makes people easily bored to read it, not only that this documentation is available in English, and in it also contains screenshots that are incomplete. Then what should we do, bro, how do we understand ??? Friend, it's easy, you just never need to give up, believe when you repeat learning continuously you will understand the documentation, and after that you will start to get used to reading the form of presentation of the documentation and means you can more easily understand the contents contained therein. However, you also need to know that the documentation is divided into several types, namely tutorials, references or explanations, and also in FAQs (this is a collection of many questions or frequently asked questions). You can also learn documentation on DevDocs, Mozilla Developer Network, The Linux Documentation Project, Stack Overflow Documentation, Google Developers, Microsoft Developer Network, and also Facebook for Developers. and after that you will begin to get used to reading the form of presentation of the documentation and means you can more easily understand the contents contained therein. However, you also need to know that the documentation is divided into several types, namely tutorials, references or explanations, and also in FAQs (this is a collection of questions that are often or frequently asked). You can also learn documentation on DevDocs, Mozilla Developer Network, The Linux Documentation Project, Stack Overflow Documentation, Google Developers, Microsoft Developer Network, and also Facebook for Developers. and after that you will begin to get used to reading the form of presentation of the documentation and means you can more easily understand the contents contained therein. However, you also need to know that the documentation is divided into several types, namely tutorials, references or explanations, and also in FAQs (this is a collection of questions that are often or frequently asked). You can also learn documentation on DevDocs, Mozilla Developer Network, The Linux Documentation Project, Stack Overflow Documentation, Google Developers, Microsoft Developer Network, and also Facebook for Developers. and also in FAQs (this is a collection of frequently asked or frequently asked questions). You can also learn documentation on DevDocs, Mozilla Developer Network, The Linux Documentation Project, Stack Overflow Documentation, Google Developers, Microsoft Developer Network, and also Facebook for Developers. and also in FAQs (this is a collection of frequently asked or frequently asked questions). You can also learn documentation on DevDocs, Mozilla Developer Network, The Linux Documentation Project, Stack Overflow Documentation, Google Developers, Microsoft Developer Network, and also Facebook for Developers.

3. Read the source code.
Of course the source code will be easy for you to understand if it is yours alone, but won't the programmers also be working on a program together. Well what if you are not able to understand the source code of your friend. Because the skill to read the source code is very mandatory to be able to understand what other people have made. Well, the good news, I will give tips and tricks so that you can understand them, namely:

• Try reading the source code from the bottom up.
• Read the part that you already understand.
• Read every comment in the source code.
• Often you visit the Stack Overflow Documentation website

4. Debugging

Source: freepik.com

If you don't know what debugging is, we will explain it. Debugging is an activity where you look for bugs or errors in your source code. Well, you need to know that the name of this debugging began in ancient times, a computer was experiencing an error and after finding out it turns out that what makes it error is a bug (insects) so that until now debugging inj is a term that is known to many people. Now, in Debugging you must be able to master the following:

• Understand every error message and also resolve it.
• Look for locations or lines that have errors
• Analyze the cause
• Fix one error peraatu.

5. Skill for asking and also Searcing google.

Source: freepik.com

Now you need to pay attention, when asking questions must be clear. Do not let you just ask, "Sis, why is this an error (skrenshoot)" of course this is not the right way to ask, it could even be you instead ignored or didownvote and you end up being bullied.
Therefore, you must have this skill, so you have to ask briefly, clearly but also in detail.
As an example : 

I get this problem ......, and get an error message like this ......, this is my source code (screenshot), I have tried changing it from ...... to ...... , I just updated from version .... to version ...... So I use version .......

         Well that's our explanation, it is a skill that you must have for a Programmer. Don't give up easily, you can do it as long as you want to try and be sure! YOU CAN DO IT !!! Cheer up

Share this post