Most important side of coding
-
Hi Geeks, Which part is the most important part in prospect of a coding. 1. Exception Handling 2. Reliability 3. Availability 4. Performance 5. Security You can chose multiple but you should assign them as priority.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Hi Geeks, Which part is the most important part in prospect of a coding. 1. Exception Handling 2. Reliability 3. Availability 4. Performance 5. Security You can chose multiple but you should assign them as priority.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
6: Something no other software has done. 5 down to 1: it's called a Try Catch.
-
Hi Geeks, Which part is the most important part in prospect of a coding. 1. Exception Handling 2. Reliability 3. Availability 4. Performance 5. Security You can chose multiple but you should assign them as priority.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
:java:
The difficult we do right away... ...the impossible takes slightly longer.
Agreed!!! There is nothing better than a fresh pot of coffee to help write code!
-
Hi Geeks, Which part is the most important part in prospect of a coding. 1. Exception Handling 2. Reliability 3. Availability 4. Performance 5. Security You can chose multiple but you should assign them as priority.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
Accuracy. Everything else can get stuffed.
-
Hi Geeks, Which part is the most important part in prospect of a coding. 1. Exception Handling 2. Reliability 3. Availability 4. Performance 5. Security You can chose multiple but you should assign them as priority.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
Pizza!
-
Which work dear I did not get your point. whatever thanks for comments.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Pizza!
with Cold drinks ( diet) ;P
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Accuracy. Everything else can get stuffed.
Accuracy always depends on functionality and desire output...
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
1. Exception Handling 2. Reliability 3. Availability 4. Performance 5. Security 0. Well documented, maintainable code. Inevitably you will get 1-5 wrong but without 0 you have little to no chance of fixing the problems.
Scope Document, Technical Document , RTM (Requirement Tractability Matrix) are most impotent in prospect of Documentation. :)
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
6: Something no other software has done. 5 down to 1: it's called a Try Catch.
Quote:
1: it's called a Try Catch.
I think you want to mentioned Exception Handling.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Yes, but that's changing the argument from "what is the most important thing" to "what are important things to do". For example, code maintainability is an extremely important thing and often has the convenient side-effect of stability, security and speed, but it isn't the most important thing.
Exactly that's why I asked people to prioritize those points
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
None of the above. IMHO the most important aspect of coding is CLARITY! Clarity makes all the others possible. Without it, you can't implement any of the others. Clarity is why we create subroutines and classes: To break up the code into manageable chunks mere humans can understand. Clarity is why we have comments and expressive variable/method names. Clarity is why a method of three subroutine calls in a loop is superior to a 200-line mess that no one can understand or reliably modify. Clarity is key to writing maintainable, reliable code. Good programmers strive for clarity.
Yes you are rite but still above mentioned points as also applicable while development.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
They will be: 1. Exception Handling 1. Reliability 1. Availability 1. Performance 1. Security Oh, did you mean real code? then: 1. Usability (that's that it works and does what it supposed to do) Everything else is a bonus.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
:) ;)
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
1. Reliability 2. Performance 3. Exception Handling 4. Security 5. Availability (not sure what your definition is here: platform support?) If its buggy I don't care about most of the other stuff. If it is tight I am concerned about how fast it is and how well it handles typical exceptions. If it runs well I am concerned about security and platform availability. If it is buggy how secure can it be anyway.
"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"
Well said... :-O
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Suvabrata Roy wrote:
In my understanding what ever is thrown by CLR is Exception.
I'd rather say that an Exception is caused by an error.
You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the tallest guy in the NBA is Chinese, the Swiss hold the America's Cup, France is accusing the U.S. of arrogance, Germany doesn't want to go to war, and the three most powerful men in America are named "Bush", "Dick", and "Colon."
Wrong. An Exception is not always caused by an error. Example: A new application is installed and tries to read the non-existent default settings file. The resulting FileNotFoundException is simply a way to tell the program to use defaults and initialise the file. It is not error.
-
Wrong. An Exception is not always caused by an error. Example: A new application is installed and tries to read the non-existent default settings file. The resulting FileNotFoundException is simply a way to tell the program to use defaults and initialise the file. It is not error.
The FileNotFound Exception would be caused by the StreamReader which tries to read the inexistent file - It is an Error, since the stream reader can't read the file. The Program using the defaults is actually the program handling the StreamReader's error.
You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the tallest guy in the NBA is Chinese, the Swiss hold the America's Cup, France is accusing the U.S. of arrogance, Germany doesn't want to go to war, and the three most powerful men in America are named "Bush", "Dick", and "Colon."
