Infected
Guide
Oh well! Interesting that you guys replied,
Well there is a lot of time spend in design time, a lot of brain storming etc, most of the code is first visualized and debate-ed upon, before even the first line of code is copy/pasted or written, when you are working on a big project or with a lot of other systems connected; each line of code needs to be given alot more though than writing the code itself. There are performance, security, integration issues. I am not saying code can not be written without such analysis, but there is a big difference between good, re-usable, and well planned code and simply dumb code. There are atleast 5 ways I can think of writing the same "Hello World" program, but which code is apt in which application is what needs to be analyzed.
Alot of development time goes here before even coding anything. So on average a lot of time is spent here, well most of this stuff is done by Architects and not really programmers, but the programmers do need to think in these lines.
...and I did not even mention maintenance and debugging. which is what a lot of Product based companies are just doing now.
Well there is a lot of time spend in design time, a lot of brain storming etc, most of the code is first visualized and debate-ed upon, before even the first line of code is copy/pasted or written, when you are working on a big project or with a lot of other systems connected; each line of code needs to be given alot more though than writing the code itself. There are performance, security, integration issues. I am not saying code can not be written without such analysis, but there is a big difference between good, re-usable, and well planned code and simply dumb code. There are atleast 5 ways I can think of writing the same "Hello World" program, but which code is apt in which application is what needs to be analyzed.
Alot of development time goes here before even coding anything. So on average a lot of time is spent here, well most of this stuff is done by Architects and not really programmers, but the programmers do need to think in these lines.
...and I did not even mention maintenance and debugging. which is what a lot of Product based companies are just doing now.