How to become a Good Programmer
Programming

By Admin - October 03, 2017 10:50 pm   0   100   0

There's a lot more to professional programming than writing code. From working with a team to solve problems to version control, you won't make it to the major leagues without a toolkit of other critical skills. We asked you, and some other professional developers, what those skills are, and here's what we learned. With all the buzz about learning to code, it's easy to think that knowing a programming language is all it takes to be a professional developer. However, like other jobs, it takes more than one skill to really be great. We can't list everything that every programmer may need, but here are some of the most important skills (besides coding) you should work on if you really want to be a developer.

Work on Basics

As it is true for any industry and any job, the conceptual understanding is the key to success. Unless one has a strong conceptual foundation, he/she can never be a good programmer. The core conceptual understanding helps you in designing and implementing the best solutions in the best possible way. If still, you feel a gap in core computer science and your programming language specific concepts, it’s never too late to go back and review the basics.

 

Start putting question tags (how, what) with every set of code you write

One thing that I realized creating a clear separating line between good programmer and rest is that zeal to know what and how it is happening. There is a small group of people who can never leave a code without knowing exactly what is happening when it executes. I understand that in tight deadlines, we don’t get this liberty always and hence have to leave the code just knowing that it’s doing its job. Although this is a bit different topic of how to handle such situations, as a programmer one can always try the level best to dig into as much as one can. And believe me, this becomes a habit with time and then you do it unknowingly every time.

 

You learn more by helping others

Most of us have a common tendency of turning our heads towards forums or groups only when we need help. And again a clear separation between the good programmer and rest that the formers visit these places more often to help others. This makes them learn more than they learn to get their problem solved by someone else. Within a team as well, help others to solve their problems. Believe me, understanding others’ problem in their context, investigating on that and providing solutions; will leave you much more learned than before.

 

Spend more time in analyzing the problem, you’ll need less time to fix it

Spend more time in understanding and analyzing the problem and designing solutions for it. You will find the rest of the things quite easily doable. Designing not always mean using modeling languages and tools, it can be as simple as looking at the sky and thinking the solution in your mind. Those who have habits of pressing keyboard (for coding) the moment get the problem, usually ended us something different than the requirement.

 

Write simple, understandable but logical code

As in almost every aspect of life, the formula of ‘Keep it simple and short’ works in programming as well. Write more logical code and avoid complexity. Sometimes people do write complex code just to prove their capability to write such codes. My experience says that simple but logical codes always work well, resulting in fewer issues and are more extendable. I remember an excellent quote

 

Don’t dismay yourself by looking at changing technology world

Over these periods in IT industry, I met with many people who are either disappointed by their work or even left it to search new job saying they want to learn and work in latest technologies. I don’t see any problem with this aspiration but the very first incorrect word is the ‘latest technologies’. What we are hearing every day and mean here is new tools, APIs, frameworks, and others mean coming up every day to make the programming easier and quicker. This anyway will continue in the technology world. But what needs to be understood is that the core and basic technologies changes with much lesser pace than frameworks, tools, and APIs around it. This is like the sea where the surface water moves very rapidly but the deep water is relatively calm and concentrated and most of the aqua lives survive here. So, feel yourself in that deep water and close to core technologies. Fore. g. in Java enterprise world, lots of web frameworks exist and new ones coming every other week. But the core concepts of the request based client-server communication, MVS pattern, filters/servlets/JSP, resource bundling, XML parsing etc remains same. So spend more time in learning these core concepts rather than worrying about ever-changing frameworks and tools around it. Believe me, with the foundation of core concepts, you will always find easier to learn new frameworks, tools, and APIs.

 

Be the first to analyze and review your code

Although a bit difficult, try to break your own code before others can and with the time you will learn to write close-to-bug-free code. Always do a close and unbiased review of your code. Also never hesitate to take others view on your code. Working with good programmers and taking their feedbacks will surely help you become a good programmer.

 

Read documentation

One of the essential habits of a good programmer is that they read lots of documentation. May it be specifications, JSR, API documents, tutorials etc. Reading documents helps you creating that essential foundation based on which you program in best of the way.

 

Don’t work for longer time

Many times software programmers implement workaround solutions (maybe because of lack of time, lack of problem understanding or lack of technology experience). But over the period these workaround solutions always resulted in corrupting the code, making it less extendible and maintainable and a lot of wastage of time later on. Always prefer to implement when you know the in-out of the solution. I understand that it becomes unavoidable in some circumstances, but it’s like, one should speak the truth always but you tell lie in some circumstances.

 

You can learn from others code as well

I interacted with some excellent programmers who actually have java source project inside their IDE all the time and read/refer that in daily work. They do it not only to fulfill their appetite of knowing the basics but also to learn ways of writing good programs. Reading and referring reliable and known open source code or your senior’s code, can also help you make your programming better.





Comment