|
Suvabrata Roy wrote: Which part is the most important part in prospect of a coding.
1. Making money.
2. Delivering the product.
3. Delivering what was requested.
|
|
|
|
|
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
Suvabrata Roy wrote: 1. Exception Handling
Not important - Exception avoidance is, however.
Suvabrata Roy wrote: 2. Reliability
I don't know how you would define this? Are you talking about the developer being reliable or the software they've developed? If the latter then I don't know what you mean by a reliable program? One that runs every time rather than crashing ?
Suvabrata Roy wrote: 3. Availability
How does coding affect availability? UNless you write code that only works on Wednesdays?
Suvabrata Roy wrote: 4. Performance
At its extremes it may be important - but better slow and working than fast and not!
Suvabrata Roy wrote: 5. Security
Depends on the system. If you're writing an ATM system, very, if you're writing a tic-tac-toe game then not much
Personally my No.1 would be maintainability.
MVVM # - I did it My Way
___________________________________________
Man, you're a god. - walterhevedeich 26/05/2011
.\\axxx
(That's an 'M')
|
|
|
|
|
Yes I am agree with you Maintainability is one of the most impotent thing while coding.
But I meant to say availability in terms of easy to deploy application and less dependency on Components.
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
|
Getting S%!& done.
Seriously all that you mention is great and extremely important. But don't ever lose the final goal of putting product out the door. If you cannot get information into the customers hands you won't have a job for very long.
It bugs me when people spend 3 weeks in analysis paralysis on Error/Exception handling when the project should have taken 1 day. But going from your list
Availability
Reliability
Security
Performance
Errors/Exceptions
To err is human to really mess up you need a computer
|
|
|
|
|
Well Explained...
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
There's no best answer, each project has a especific order.
Missing
1. Usefullness
Paulo Gomes
Over and Out
|
|
|
|
|
Reliability encompasses all the others except maybe performance, but I would think think a product without acceptable performance would be consider unreliable by most.
|
|
|
|
|
Hmm....
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...
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.
|
|
|
|
|
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.
|
|
|
|
|
I'm with you although I'd call it: Maintainability
Of course, for small throwaway apps, this doesn't matter. But for apps that will need to be maintained and enhanced and modified over time, it is important to have it coded properly, not just have it working. It is important to be able to make changes to it without breaking everything (or having to spend a week, six months down the road, trying to figure out how the code is actually working so that I can enhance it), etc.
My two cents,
-D
|
|
|
|
|
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...
}
|
|
|
|
|
and really enjoying your work
David
|
|
|
|
|
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...
}
|
|
|
|
|
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...
}
|
|
|
|
|
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...
}
|
|
|
|
|
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...
}
|
|
|
|