But for a starter for few years Job profile is important for development, slowly you need to build the domain knowledge also. Just for domain knowledge sake you go to support rather than development, your growth opportunities will be less. I didn't mean to demean support. When you want to grow fast, you should get to development.
What might be the best path for you to take, we can't know, because we don't know your career and life objectives. In IT you'd better be prepared to become familiar with a number of domains, because you're unlikely to stay in any particular domain for the remainder of your career.
i have heard that the coding is copy paste of the previously written codes , may be for some other client i.e. there is less development right from scratch nowadays. Is it true?
Also i want to know the ratio of development to production work nowadays? Why freshers are being put into support when they do not the heck of it?
Joined: Mar 22, 2005
Those questions are of a general nature - the answer varies widely from company to company. As to all coding being just copy-and-paste these days, that's just flat out wrong (which is not to say that it doesn't happen every once in a while); where did you get that idea?
Originally posted by Lakshya Sen: i have heard that the coding is copy paste of the previously written codes
The most dreaded decision to make while coding is to copy-paste, especially when you don't understand. You can always see a code and learn from it, actually you have to make a habit of reading others code because that is the only thing which can tell you how quality your code is when compared to others.
Reading source code also helps because it is almost sure in someone's career that one day they have to maintain code written by some other person.
Copy-paste will definetly save you some typing time but you will waste a lot of time fixing the bugs and you will never understand what exactly the code does till you fix all the bugs. [ November 14, 2006: Message edited by: Srikanth Raghavan ]
Joined: Oct 31, 2005
Well, I have too little experience to tell you anything about domain knowledge. So, I am making myself clear that whatever I am saying is my opinion.
I think that initially one should try and get into developement not because it's fun but you will get to know a lot of stuffs. You have to constantly read about software engineering methodologies, writing quality code, good designing, Object Oriented Programming (which isn't actually just extending and making subclasses) and a lot of other things. So, I would prefer developement initially and I consider myself very lucky to be involved in doing 3 products right from scratch.
If you got yourself into support, fine... You will gain a different kind of experience which I may not be able to gain in developement ---like analyzing the log files, tracking client's issues, handling phone calls and stuff like that which is also a very good experience.
But on the other hand, domain knowledge definetly helps and my boss keeps saying me that after a period of time (say 10 years) from now it's only the domain knowledge which will be more important than your developement skills.
But having said that, I would like to try atleast 3 or 4 domains before choosing one and shaping the rest my career on that. If at all that domain vanishes for some reason, I will have the knowledge of the other domains on which I have worked in the past.
Don't think too much about what you are going to do after 10 years or 7 years because you will come to know automatically when you gain some experience and you will make the best decision for you. Till then, concentrate on your present, that is programming...
This is what I tell myself, hope this helps you too Correct me if my notion is wrong somewhere or if I am missing something....
That was a very good blog Lashkya, but I could see more positives than negatives from what he is saying. It is for sure that life will be a lot tougher but you will get to learn a lot of things so early in your career and when you eventually work on some developement project you may be far ahead that your team mates....
But I still feel that you must do both of them (not at the same time always). So don't lose an opportunity when you get a chance in developement but take your current experience in support with you when you eventually do developement work...