Most important side of coding
-
Ya!!!!
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
Suvabrata Roy wrote:
Ya!!!!
There are some project managers and sales people I would like to introduce you to :) But seriously, functionality is not a given. As others pointed out "Requirements", are important. With out them I can give you what you want always, as it is my opinion of what you want. Of course when you receive it you inform me that is not what you meant. Great! Can I have your requirements of what you want? Oh you know what I want. No, really I don not. Please tell me. OK, I want it to do A then B. 3 months later.... Ok Here it is A then B. Ah, but it is doing C. Its not suppose to do C. You didn't say that. Well I figured you knew that it can not do C. 3 months later.... OK here it is A then B and not C. Ahhh. You did not do B.2 you did B.1 :mad:
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet. The interesting thing about software is it can not reproduce, until it can.
-
:java:
The difficult we do right away... ...the impossible takes slightly longer.
-
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... }
Suvabrata Roy wrote:
Which part is the most important part in prospect of a coding.
Architecture. Because from a good architecture, the 5 things you listed are a lot easier to deal with. Marc
-
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... }
-
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... }
Catching exceptions is only aspect of error handling. There are several other aspects such as logging and state rollback. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
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... }
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
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
0. Bacon 1. Coffee 2. Specification 3. Design 4. Payment
The only instant messaging I do involves my middle finger.
I respectfully request replacing "Bacon" with "Bacon or ham". /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Suvabrata Roy wrote:
Which part is the most important part in prospect of a coding.
Architecture. Because from a good architecture, the 5 things you listed are a lot easier to deal with. Marc
Yes absolutely rite but which we should use while development whit out client's requirement just to ensure standers.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Just to maintain standers not depending on requirement...
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
Just to maintain standers not depending on requirement...
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... }
-
I respectfully request replacing "Bacon" with "Bacon or ham". /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Sorry, but...a "Ham Sandwich" is just "lunch". A "Bacon Butty" is a Meal!
The only instant messaging I do involves my middle finger.
-
Yes absolutely rite but which we should use while development whit out client's requirement just to ensure standers.
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
Suvabrata Roy wrote:
Yes absolutely rite but which we should use while development whit out client's requirement just to ensure standers.
Well, unfortunately, it's another item not on your list. "Testing!" Marc
-
Sorry, but...a "Ham Sandwich" is just "lunch". A "Bacon Butty" is a Meal!
The only instant messaging I do involves my middle finger.
OriginalGriff wrote:
A "Bacon Butty" is a Meal!
A rasher statement I haven't heard. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
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... }
The most important is: Does it solve the problem? In the end, nothing else matters.
-
OriginalGriff wrote:
A "Bacon Butty" is a Meal!
A rasher statement I haven't heard. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Brilliant!
BDF The internet makes dumb people dumber and clever people cleverer. -- PaulowniaK
-
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... }
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 :suss: If you can't read my code, try converting it here[^]
-
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... }
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')
