Programming principles and guidelines in software engineering
The variable names should be in camel case letters starting with a lower case letter. All the names of constants should be in upper case. In case the name of constant is too long, it should be separated by an underscore. The temporary storage variables that are restricted to a segment of code should be short. It is important to note that a single temporary variable should not be reused in the same program.
The use of literal should be avoided. These numbers are counted as integers and result in wrong output of the program. The use of numbers in naming variables should be avoided. As with variables and constants, there are some guidelines that should be followed while naming functions in the software code.
These conventions are listed below. Comments are helpful in proper understanding of the code segment used in program. Commenting conventions should be used efficiently to make the code easy to grasp. Generally, two types of commenting conventions are used: file header comments and trailing comments.
File header comments are useful in providing information related to a file as a whole and comprise identification information such as date of creation, Dame of the creator, and a brief description of the software code. Trailing comments are used to provide explanation of a single line of code. These comments are used to clarify the complex code. These also specify the function of the abbreviated variable names that are not clear. The commenting conventions that are commonly followed in the software code are listed below.
The Principles Of Good Programming. Manikanta Pattigulla Updated date Jul 05, Overview Programming principles have helped me over the years in becoming a better programmer, and I believe, this article will help any developer become more efficient and able to produce code which is easier to maintain. What are Programming principles? Why should a developer follow the principles? What are the benefits if developer followed it? Readability All developers were in a team able to understand the code.
So our code is always easy to extend without breaking existing business rules. Modularity Divide a program into reusable pieces: functions, modules, libraries. In other words, a piece of logic should only be represented once in an application. Duplication is the root of all software evils. Duplication is a waste. The KISS principle states that most systems work best if they are kept simple rather than making them complex; therefore simplicity should be a key goal in design and unnecessary complexity should be avoided.
This principle can be applied to any scenario, including many business activities, such as planning, designing, and development. Just one word… Wrong! Practice-Practice-Practice makes a man perfect.
These principles are not something you can learn and apply on. It is very much similar to what we hear about old wine. These were some of the most important basic principles that play a big role in your journey as a developer. I am pretty sure there might many more principles I might have missed upon. I have decided to dedicate a separate article for that. If you like the article, hit the like button, share the article and subscribe to the blog.
View all posts by shravan Like Like. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account.
Notify me of new comments via email. Notify me of new posts via email. Skip to content. Keep It Simple, Stupid is a great life hack!!! Look at the how messed up this looks? With experience, your standards will just get better and better. Share this: Tweet. Like this: Like Loading Published by shravan Published September 3, October 23, Previous Post Corona : What a year this week has been.
Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email Address never made public. Follow Following.
0コメント