|
|
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 | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
+ in afternoon.
|
|
|
|
|
Agreed!!! There is nothing better than a fresh pot of coffee to help write code!
|
|
|
|
|
If I was forced to choose one, I'd select #2. In reality, all are important. I would however replace "Exception handling" with "Error handling".
/ravi
|
|
|
|
|
Ok Nice one but how you segregate an Exception from an Error.
In my understanding what ever is thrown by CLR is Exception.
If Coder misplace logic that's an error.
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.
|
|
|
|
|
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."
|
|
|
|
|
Catching exceptions is only aspect of error handling. There are several other aspects such as logging and state rollback.
/ravi
|
|
|
|
|
|
Yes, but functionality is the most basic requirement without which you cant proceed but which ever point I have mentioned those are you may or may not.
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
|
Ya!!!!
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
|
Well said. +5
I believe this is the one of the main reason why most projects fail or gets delayed. It's because developers are trying hard to build software with multitude of features that in the end, the end users may actually not benefit from.
Signature construction in progress. Sorry for the inconvenience.
Damn you have the perfect signature - CBadger
|
|
|
|
|
I'd have to quote your entire post, assuming I did...
My experience has been...
THEM: Can you do A?
ME: Yes, here it is.
THEM: Oh, can you do B?
ME: Yes, here it is.
THEM: OK, can you do C?
ME: Yes, here it is.
THEM: How about D?
ME: Getting harder, but yes, here it is.
THEM: I really need E.
ME: Why didn't you ask for it first? I can do it, but it is much harder now.
THEM: I didn't know you could do it until you managed to do A, B, C,and D, but E is what I really wanted all along.
ME: You know, I could have given you E, much faster and easier if you had asked for it first.
THEM: I didn't know what you could do (as in product, not my abilities).
ME: Grrrr!
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
|
Collin Jasnoch wrote: Maybe some day they will refer to it as going Developer
I'd send you a t-shirt, but I think you already have one.
What always galls me is their insistence on paving the cowpath by electronically replicating their manual (paper) methods.
I understand that they don't know my job, but they blink at you uncomprehending when you explain that the computer can transcend their manual methods and do something that is a quantum leap over what they've been doing.
I always think of it as that it is part of my job to become an expert at theirs, if only for a day, so I can separate what they are doing from what they want done.
A side rant is how they fail to realize how you can fold the process into individual steps and then wave their hand and say, "You don't have to worry about X, because it only happens every once in a while."
For example at one job, the hardware manager freaked when I explained to him I did not have 60 separate modules to handle the 60 diverters on the conveyor, I had only 1, but in regards to those occasional events, if they happened even once, I had to have code to deal with it. It didn't matter that it was only needed once every million cartons, I still needed to take the time to deal with it. What really caused him to lose it was when it was revealed it didn't matter where a photoeye was located, I just had to change a parameter number to set it's location. He was too used to building rails to place the photoeyes on so their location could be fine tuned.
But then it was truly amusing when we had a bug, he suggested we run the computer slower so it wouldn't happen. His other bright suggestion was to print out all the instructions that were executed so we could find out where it failed. 
You are free to make varoom sounds as you pass your hand over your head repeatedly.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Suvabrata Roy wrote: Yes, but functionality is the most basic requirement
In (my) reality, prioritizing functionality is probably the key aspect of delivering a software product.
/ravi
|
|
|
|
|
I don't know, software isn't very functional if no attention is paid to the members of that list.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
That is the basic requirement....
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
All the above are handled by one point - Fit For Purpose
Simples.
speramus in juniperus
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
