Last Updated:

10 Java Programmer Errors That Will Lead You to Problems.

Java Programmer Errors

1. Long thought and inaction

As in any business, if you think and ponder for a long time (to start or not to start, and what will happen then, and whether everything will work out, and what others will say), then everything will remain on an abstract level.

Of course, it happens that it is necessary to familiarize yourself with it (for example, studying the instructions before clearing the bomb), but in the case of programming languages, you do not need to pay much attention to this. So, you trample on the spot, looking around to make sure that you are not one of them, although in fact you and everyone are going backwards.

2. Internal attitude that I will not succeed. Java is complicated, it's immense.

 

True leaders have never been stopped by the word "difficult." If you run away from this word to other words ("easy", "fast", "no problem") - you can not start learning Java. Show me a man who knows all aspects of the language and knows how to apply all its modern technologies in practice - and I will spray him with gasoline and burn him, because I consider him an evil force that cannot exist on earth.

If you think it will take you several lifetimes to learn Java, you're right. In fact, you will study only a few areas of interest to you, and this will be enough for you, as they say, "for the eyes". On this you can build a successful career, on this you can earn good money. You can enjoy it and get a buzz out of it.

There is nothing complex about Java that cannot be understood. The main thing is to move from simple to complex, and not from complex to complex.

3. Fear of making mistakes.

 

At first, you think that everything should work perfectly the first time. Any mistake is fatal for you. You are afraid of mistakes like fire, you think that if you make a mistake, then you do not have enough brains to write the right code and you have nothing to do in programming. Of course, this is not the case. Only the one who does nothing is not mistaken. (The programmer who does not program does not make mistakes).

So much has already been said about mistakes and failures by various personal growth gurus that I have nothing to add. Everything they say is completely suitable for growth in learning Java. Don't be afraid of mistakes! These are your helpers! It's your experience! At first, mistakes will find you. The main thing is your attitude towards them. Thomas Watson, one of the founders of IBM, said something like this: "Whoever makes the most mistakes this month will increase the salary."

4. Getting ahead of yourself without learning the previous basics.

 

You may have heard somewhere that now J2EE is used on all major projects, and only ancient people program on J2SE. And they rushed to study J2EE at a time when they were still not familiar with J2SE. You think J2EE is much cooler, and no one needs J2SE, so you can jump over it. Many beginners have burned their hands on this one (including me) trying to learn Java by snoring.

First, with this approach, you soon realize that you need to go back to the starting point and practically start all over again, because there is no base, no foundation. But more deliberately, and not as before. So precious time is lost. If you don't know what interfaces and abstract classes are for, but you already want to program ejb components, then this will not lead to much. There will be more porridge in my head and, as a result, disappointment and lack of enthusiasm. Pointless copying of working code without understanding how it works is a sure way to gaps in knowledge and, as a reason, not professional suitability, which is revealed at the first serious interview.

5. Non-object-oriented programming.

 

If in the institute program you got acquainted with visual basic or delphi, then you probably remember how nice it is to program on them - you threw a button, wrote code for it and you're done. You remember how quickly they did all the institute tasks - I left the buttons, hung the necessary functions on each of them - the automatic exam is provided.

In Java, this approach turns into trouble, because the inability to generally organize the architecture of the program through the use of the principles of object-oriented programming is another road for your program to the cemetery of buried programs. There are such programmers – they are called "button-level programmers".

So, employers fear them the most, because they can confuse a large system the fastest, which will invariably lead to unnecessary costs. Try writing a system of more than 10,000 lines of code in a "student style" — just by hanging actions on buttons. You vomit. And then to change some functionality - vomit again.

Another thing is if the principles of the PLO are used. You know what and how it is connected with what, who is responsible for what work. You need to change something - you take and change, simultaneously knowing how it will affect other objects. For me, this was one of the most difficult problems in the transition from university tasks to life ones. Learn to first think about how all this will work with each other, what objects need to be created, where to place, etc.

Then start writing code. If beginners were punched every time they try to program in a non-OOP style, all beginners would stay to teach at the university, because they pat on the head for such a thing and give the highest marks (works - and okay).

6. Lack of practice

 

There is such a law of life – what does not develop, dies. There is either development or degradation. You won't find a middle ground here. Again, any growth guru will tell you that. But not everyone accepts this fact by virtue of their beliefs and principles. Go to the gym - muscles develop. Don't go— they're flabby.

Run in the morning - strengthen your health, do not run - lose health. It's the same in programming: there is no practice, your programming qualities begin to die out and become decrepit, your accumulated skills are lost. Even if you study the theory for tons, but do not try to practice what you read, this will not lead to anything. There are many people who in theory know Java probably even better than James Gosling, the creator of this language. But they can't write a single little program. (We had such teachers at the university)

7. Downloading and accumulation of information "in reserve".

 

I think this problem affects more than 90% of people who study any information. This applies not only to beginners and not only to programming.

It is very difficult to get rid of this problem, at the level of instinct we download and download necessary and unnecessary information in order to study it "later, when there is more time."

Over time, you begin to notice that not only on the hard disk there is free space somewhere, but also in your head - it seems that you downloaded so much information, and in your head is empty, or vice versa, all the free space is occupied and no longer gets into your head. There comes a kind of stupor.

 

8. The desire to get to everything on your own.

 

Someone will say that this is only a plus. But it happens that it takes too much time. Or you find a solution that is not so good, although you could be told the ideal, the best for your problem and subsequently you would solve a similar problem yourself, quickly and efficiently. When you can not solve the problem for a while, you are completely exhausted, you already begin to think that the meaning of your life is in solving this problem - that's when the "dead end" comes.

 

The mood at this time is bad, you do not want to talk to anyone, cheerful and cheerful faces cause irritation in you. It seems that the whole world is mocking you. That's just the way it is. Because the whole world is you, you're bullying yourself, trying to solve the problem on your own, no matter how complex it is, your internal ego is completely in control of your consciousness.

 

9. In contrast to the previous point - the desire to always ask everything from others

 

If you do not want to think for yourself, constantly turn to other people for help for any reason, if, seeing you in the corridor, colleagues tend to turn around as soon as possible so as not to stumble upon your questions - you will not last long in the world of programming, since about 80% of the tasks in it have to be solved independently.

Of course, at first you will have a bunch of questions, which your friends or colleagues will most likely help you to rake. But don't think they'll guide you by the pen for the rest of your life and solve all your problems — no one likes dependents.

 

10. Failure to use the full range of available information and training.

 

When you start learning Java, you will most likely need video instructions on how to run the first program, how to install jvm, etc. On them you will learn the basics faster than if you read the text without pictures and tried to determine the actions of the author from the words. It also often happens when ordinary text examples are better than any video show and tell how to solve the problem.

That is, depending on the purpose and audience, one or another type of presentation of the material contributes to its better assimilation. Thus, studying materials that you cannot understand due to the lack of visibility in them - you very soon lose interest in studying at all.