|
No dear speed will always matter...
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
Nobody cares about speed if you don't solve their problem. The very existence of .NET and Java prove that speed is not of primary concern. Now, once you solve the problem, reliability, predictability and speed come very much into play (hence, why I still get work doing C++ development.)
|
|
|
|
|
Yes we should solve the problem and we also care about speed at the same time
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...
}
|
|
|
|
|
1. Running code
2. Getting paid
3. The rest is just the noise of the job that will vary by task.
|
|
|
|
|
hmm 
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
Suvabrata Roy wrote: Which part is the most important part in prospect of a coding.
What's most important to you when undergoing surgery?
- Anesthetic?
- Disinfecting?
- Sewing the body when done?
- Checking if you still have both your gloves?
- Survival?
Please, assign priorities
They're all priorities. When someone repairs a car, do you ask whether checking the brakes is a priority? What you're asking is where you can cut corners. The plain answer is that you can't, the quality will always suffer.
That doesn't mean that the client would notice. Security isn't a problem (and doesn't get any budget), until it's proven to be broken. A completely secure program that doesn't perform, will not be used, no matter what it will promise the user.
The most important aspect of any trade, is learning the trade.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Yes I consider your thoughts and they are absolutely perfect in our real life scenario, but when we code just to have fun then or just to deliver some utility to some not only for money but as tech guy I will help him then which we should keep in mind.
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
Eddy Vluggen wrote: When someone repairs a car, do you ask whether checking the brakes is a priority?
I see we are of the same mind.
I used to counter with a similar question when a management fad was "Time boxing". Work on the module for a certain amount of time and then move on.
I'd ask, "Do you want the mechanic working on your brakes to time box or would you rather he finish the job?"
Yes, I was one of the usual suspects when it came to asking questions at the end of a presentation.
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: 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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
