Depends on what you want to do. You've already done devp for 1.5 yrs. If you want to try something different go for it. On the other hand, try asking the company how internal transfers are treated. Are they given high priority? This will ensure that if you get bored of Support in sometime, you can make a switch to devp.
There are lessons to be learnt from support and maintenance positions, and there are other benefits too.
For example, support positions (I won't refer to it as s&m positions I'm not explaining that ) can give you access to a larger body of prewritten code from a large group of programmers. Trawling through this gives you the chance to see features you like and you don't like, things done well and... not so well. Another useful lesson from support positions is to see what it takes to write maintainable code. It sounds obvious, in theory it should be, in practice it is not.
The down side is that these skills, while making you a better programmer, are unlikely to be visible in terms of 'career progression', and maintenance positions tend to become a bit of a rut and count against you if you get stuck there too long.
It has long been my view that everyone should spend some time in a maintenance position, but I don't believe you have the experience to learn all the lessons available, and you may find it difficult to out afterwards.
In development u will learn better & get more opportunities than in support
Sunil Kumar Gupta
Joined: Aug 26, 2005
Originally posted by Amit Saini: Depends on what you want to do. You've already done devp for 1.5 yrs. If you want to try something different go for it. On the other hand, try asking the company how internal transfers are treated. Are they given high priority? This will ensure that if you get bored of Support in sometime, you can make a switch to devp.
As David mentioned there are positives and negatives. Positives it gives lot of scope for you to learn many things. If you are in development you may not get chance to see everything but in support job you may need to do. Support job may not be always support also, there will be enhancements also. Small may not require much work but if the enhancement is big then you need to go entire cycle of analysis, design, coding, testing etc., which will be same as development. Support job sharpens your analysis, estimation skills. When you go for a small change you need to analyze lot of other areas which are going to affected by this change which improves you analysis.
But you may not see all above positives in every case. Same time all development project may not give you what you are expected. This happens especially when you have less experience and there other seniors in your project.
At least I enjoyed the support projects I worked. Even though my management named them as support projects but I got small enchancements(which requires 1 month time) and got chance things to do which I used to do in development project. And moreover I am the only team member in that support project so I played all roles from analyzing problem, coding and testing.
So if you feel you will learn something from the work you are going to do then go ahead.
Good Luck [ November 29, 2005: Message edited by: KJ Reddy ]
Originally posted by David O'Meara: (I won't refer to it as s&m positions I'm not explaining that )
LOL. I can imagine writing my next job description - 'required keen and enthusiastic person for an exciting s&m position with a reputed company. Abundant opportunities to apply your s&m skills. Training provided. Workplace fun and casual........' And a mention of the required dress code somewhere in there
Thanks KJ for your reply. I think i should follow what you are saying.
Joined: Sep 20, 2003
Originally posted by Sunil Kumar Gupta: Thanks KJ for your reply. I think i should follow what you are saying.
Dont follow any one. Just think and take your own decision. Think about what others saying. If possible take advice from people who already working or worked in support projects, they may different experiences.