These are the 7 rules
1.Analyze the Problem
2.Plan, then code
3. Fix identified bugs
4.Develop good coding habits
5.Review the code
6.Know thy enemy
7. Documentation is your friend
1.Analyze the Problem
In any project analysis is the main criteria for efficiency of the project. If we don’t understand the problem or what to do we can’t go further how to do? So first understand the Application/the project/Problem to find the optimum or better solution for that.
This analysis includes understanding of the problem and seeing the application from different prospective as well as Requirement analysis .These Requirements again includes
1) Functional
Tells us about the functional flow of the application
2) Technical
Deals with Technical scope of the application. That is what are the software’s to be used, which database to be used. This may again includes software requirements and hardware requirements
2.Plan, then code
Planning is very important thing in our day today life .If we plan effectively we don’t miss the dead lines so that feverish pitch situations can be avoided.
It's important how effectively we plan our code to produce the required output with in stipulated period. It's not that much easy. Some times it may be varying from simple to complex logic.
3 Fix identified bugs:
After the through and careful coding, test the code intensively in the end users prospective. Fix the identified bugs so that a tester may not be able to find out as many bugs as he want
4 Develop good coding habits
Follow good coding standards and naming conventions so that these increases readability of your code .Comment on source code as and when required during the development time.
Better to use xml Documentation Comments. These comments are formally single line C# comments containing XML tags. They follow this pattern for single line comments:
/// <summary>
/// This class...
/// </summary>
Multiline XML comments follow this pattern:
/// <exception cref=”BogusException”>
/// This exception gets thrown as soon as a
/// Bogus flag gets set.
/// </exception>
5.Review the code : After developing the code if you get the desired out put ,don’t think that your job is done. Try to write generic code. Review the code after developingThink of any possibilities that are there to modify it so that you can make the code as reusable ,robust and faster performance
Out of all alternatives select the best one .There can be many possible ways but the optimum way is the best way.
6. Know thy enemy (the most difficult thing that fears U) :
If you are feared of something don’t get scared or let the other person not to know about your weakness. You just concentrate on the thing in which you are lagging and try to improve from that side ,then practice it .Let your enemy get fear of you.
7. Documentation is your friend
Last but not least …and most important is documentation. After all u know something are developed some code on a specified day, or transferred some knowledge. Document it. As you gain experience you can know the importance of documentation. People say that they are irritated to document everything. But when you document it this is a written proof for what you have done and also it can be reference in the future .If you have forgotten something (as of human nature), just refer the document for details.
|
| Author: Azamat 06 Jul 2006 | Member Level: Gold Points : 0 |
Hello,
I was just wondering whether there is any kind of moderation available at dotnetspider or not. This article proves that no moderation what so ever is being done at dotnetspider.
If writing 5 points for freshers, is called an article, I am really suprised.
No Offence to SnowDrop but being a senior person at dotnetspider, he should be a little subjective in posting such kind of articles.
Anyways, Get a digiCam for this article.. lolz ;)
Az.
|
| Author: HimaBindu Veeramachaneni 17 Jul 2006 | Member Level: Diamond Points : 0 |
Hello,
Thanks for the feedback. Just have a look at modified article and welcome your valuable suggestions that are always helpful in improving my knowledge.
Due to technical problems the article is not in the proper format in the previous posting
|
| Author: DotNetGuts (DNG) 17 Aug 2006 | Member Level: Diamond Points : 0 |
Hi i really enjoyed your article and to add above comment i wud say tht article cannot be judge by its length, it is always judge by it content.
I Enjoyed the content
Keep going good work.
|
| Author: Gaurav Arora 15 Nov 2008 | Member Level: Gold Points : 2 |
Hi all!
This is the place where we can share our knowledge and there is no means in what ways one can get knowledge. The purpose of the articles is just share a good techie knowledge and I think there is no as such motto of the writer to publish the things here. So, please supply such a good articles to enhace DNS.
Best of luck!
Thanks & regards,
Gaurav Arora
|