Top 10 laws of Programming Language we should know

In this post you will know the best laws of any programming language we must know as a software Engineer. They are

1. You must choose your programming language. Your job should not choose that for you.
2. Never jump in front of the computer until you know exactly the approach you will use to solve a problem. You may change the algorithm to improve the solution or for any other reasons, but don’t open the IDE app until you come up with an algorithm in mind
3. Always think that you code for human, not only for the machine. It could be yourself in the future, or somebody else who need to maintain your code. Write readable codes instead of cryptic smart ass ones
4. get proper hold on the basic stuffs. Loops, conditions and function/method calls. Play with them as much as possible. Switching between languages becomes easy if you understand these stuff, once and for all. Later, its all about just learning the syntax.
5. Before you start coding, write down the logic in laymen terms on a paper or keep a notebook. You can call it ‘algorithm’ if you want. It doesn’t have to be a sophisticated shit.
6. Always make your program as robust as possible.Once you are done writing the code, execute it and test. Then lean back and take a look, see if you can make it better/optimize
7. Remember one thing, doesn’t matter what language is trending , debugging is the KING. You can write the most optimized , good looking well performing code, but if you can’t debug and understand the code that is written by someone, its gonna be hard working on a existing project. And that comes with experience.
8. If you are sitting and struggling for hours together to write a logic and solve the problem and nothing is coming to your mind just take a break. Get up and take a walk. Don’t think about the problem. Just take a walk or go talk to that pretty girl sitting in the next line. Get a cup of coffee. Come back to your place. It might just click.
9. Always design the code as scalable as possible, expect changes and modifications, ensure the cost to do it as low as possible
10. Test your code intensively before your QA do it
11. Use version control and backup your code frequently