2007-06-02 20:20:26 · 7 answers · asked by ?theriddler? 1 in Computers & Internet ➔ Programming & Design
I think they are referring to top down design. If you develop correctly you can anticipate problems and solutions before they arise. Trouble shooting, on the other had can be costly. Will my program not load because of a corrupt Java Script, and unregistered Dll who knows? Had had the developer been more careful I would not have to troubleshoot an ambiguous problem.
2007-06-02 20:32:15 · answer #1 · answered by Anonymous · 1⤊ 0⤋
development and troubleshooting in a sense are one in the same..
you develop an application to solve a problem..
you troubleshoot as well to solve a problem. The difference is how those two are applied..
you would'nt develop an application to solve a network problem, however you would troubleshoot the network to find what the problem is..
likewise, you could develop an application to track productivity in some means useful to you, thus solving a problem..
I would not say one is better then the other.... I personally prefer troubleshooting networks, and am not fond of development, however I can hack some scripts together on the fly if neccesary..
it's just all part of what makes up the skillsets to get the job done..
2007-06-02 20:28:30 · answer #2 · answered by m34tba11 5 · 0⤊ 0⤋
Let's say I have a client who requested a custom program. I need to put in mind that the client has a desired output and doesn't want the program to be buggy and requires the least maintenance. In order to achieve this, development requires a lot of attention, in fact, it is the most crucial part in any software designing project. Bugs and errors cannot be avoided but it can be reduced. With excellent development and preparation, troubleshooting might not even be needed at all!
Development is always primary. Others (coding, testing, revising) are secondary
2007-06-03 02:00:13 · answer #3 · answered by Francis Seriña 1 · 0⤊ 0⤋
Because at the time of development whatever crap is coded needs to be cleaned at the time of troubleshooting
2007-06-02 21:31:35 · answer #4 · answered by Anonymous · 0⤊ 0⤋
Development is what I do before something hits the fan; after that, it's troubleshooting. Tho my clients like it better if I am trubleshooting my code, because they know it already exists (is out of development.)
2007-06-02 20:57:21 · answer #5 · answered by CuteDaemon 1 · 0⤊ 1⤋
Both takes same amount of time and money. Some time trouble shooting may take lots and lots of time at the end nothing happens. Therefore, development considered better option, even if it takes more money and extra time. Once you trouble shoot the same trouble may occur again and again. By developing there is a possibility that those kind of troubles may be totally avoided.
Another thing, there are people ready to buy new products than existing one. By considering all these factors, DEVELOPMENT is considered better option than TROUBLE SHOOTING.
2007-06-02 20:39:23 · answer #6 · answered by soundrajan v 3 · 0⤊ 1⤋
you should know better than anyone, if you are what you say you are....
2007-06-02 20:25:48 · answer #7 · answered by Carling 7 · 0⤊ 0⤋