Most important side of coding
-
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.
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
-
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... }
-
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:
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[^]
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... }
-
1. Running code 2. Getting paid 3. The rest is just the noise of the job that will vary by task.
Play my game Gravity: Android[^], Windows Phone 7[^]
hmm :)
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.
No dear speed will always matter...
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
1. Doing stuff. 2. Going to the pub Not necessarily in that otder. hic!
Veni, vidi, abiit domum
:laugh:
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
standards :) typo...
Life is all about share and care... public class Life : ICareable,IShareable { // implements yours... }
-
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.)
-
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... }
-
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... }
254
-
0. Bacon 1. Coffee 2. Specification 3. Design 4. Payment
The only instant messaging I do involves my middle finger.
-
If you have enough Bacon, you don't need Pizza! :laugh:
The only instant messaging I do involves my middle finger.
-
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... }
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.
-
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... }
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
-
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:
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.
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.
-
Since when? Cost influences everything we do: if it costs too much, it won't get done; it is comes in under budget we might get new toys. Or a pay rise.
The only instant messaging I do involves my middle finger.
OriginalGriff wrote:
Or a pay rise.
Wait,...you lost me there. Did you mean the bonus the execs give themselves?
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.
-
Getting paid... I wouldn't do it otherwise. Don't get me wrong I enjoy coding but after 8 hours a day I don't look at any code after hours. I see Griff already had payment on his list. That's how important it is to coding.
It was broke, so I fixed it.
