hai, i want the general guidelines that any software programmer should follow.
Coding Guidelines
Collapse
X
-
Tags: None
-
Dear PradeepOriginally posted by pradeepaveluhai, i want the general guidelines that any software programmer should follow.
Thanks ...Great asking cause I have the same asking to all of my friends. If I like to develop a project with front end as JAVA and backen as ORACLE. Whats the steps should I follow & mainly to connect this JAVA & ORACLE. I am highly expecting kind advices from all friend cause I am new in development.
Thanking you all. -
For the Java to Oracle connection thing you should really have asked in the Java forum. Have a read at a JDBC tutorial.Originally posted by fnbhnsDear Pradeep
Thanks ...Great asking cause I have the same asking to all of my friends. If I like to develop a project with front end as JAVA and backen as ORACLE. Whats the steps should I follow & mainly to connect this JAVA & ORACLE. I am highly expecting kind advices from all friend cause I am new in development.
Thanking you all.Comment
-
This actually differs quite a bit from place to place. It's also the reason why "in-house" code is looked down upon so much. I would recommend looking at the Java source - how they implemented the language. You will get acquainted with the finer points and some of the best-practice habits there.Originally posted by pradeepaveluhai, i want the general guidelines that any software programmer should follow.
In general, I would suggest prepending the "simple" types - int, char, string, with an identifier as well as good variable names so someone reading your code can decipher it easily (eg - i_numberOfMatch es for an int holding the number of matches so far).
Optimize when possible. I know this is a bit ridiculous to tell someone as a guideline when they dont' know the advanced data structures, but when you learn them remember one thing:
Your professors made you code linked lists and vectors from scratch to figure out how they worked. The most important part: ONLY to figure out how they worked. Trust the structures and methods to be implemented better and at a more optimized level than your skills until you are at the point where you are interested in and can understand the low-level algorithms of how each one works.
From there I would suggest looking into the package structures of large programs, but that definitely changes from place to place, so if you just keep coding every day, you will learn the things above - they come with experience as well ;).Comment
Comment