|
After I started working at a company, I found out that the job is to maintain a software product. Most of the work that I'm doing is finding and fixing bugs. It's not easy work. However, there is no new feature development. I am worrying about this, as it might mean I won't ever get the chance to focus on development. What can I do to transition from a job that's maintenance-only to one where I'm creating and designing software? |
|||||||||
|
|
Your situation is far from unique. Most of the developer jobs are actually maintenance jobs, even though usually they include at least some new features too. If there are no feature requests for your product at all, maybe it is on the road to being abandoned... you should clarify this with your manager. It is important to know why there are no new features: is management unwilling to invest any more in the development of this product, or are the users completely out of new feature ideas? In the latter case, it is also possible that there are very few active users and/or they have grown so accustomed to the way the program currently works, that they can't even imagine any change in it. However, if management is not totally closing out new feature developments, and you have contact with the users, you might be able to catalyse them to request new features. Take any opportunities to discuss bug reports and possible solutions with them, ask their opinion about how best to handle specific error cases, and how this program could be made better in general. Eventually they may mention ideas out of which new features can sprout... At any rate, discuss your concerns with your manager. If you are lucky, you will be understood and you can work out an expectable solution together with him/her. E.g. it may be possible for you to work part time on another, actively developed product. If not, you basically have two choices: continue your current job and work on pet projects in your free time to keep up and improve your development skills, or start looking for a new job. |
|||||
|
|
Learning automated test techniques as part of your maintenance will be a useful skill that you can use during your career. You can learn a unit testing framework for the technologies (client and server), a mocking framework, unit test techniques, integration test techniques; there is a lot to learn. It can help your regression tests for maintenance work you're currently doing and keep you interested until you will able to take on functionality. |
||||
|
|
Ask your manager whether you will be implementing features in the software or whether you will strictly be maintaining the software. You basically want a description of your role and your responsibilities. If what you hear doesn't meet your liking, you can let your manager know at this time. If they aren't willing to accommodate you, you have no choice but to start looking for work elsewhere. |
|||||||
|
|
You need to check if there are feature development opportunities in your workplace. If not, then at some point, you will have to make a decision - do you acquire the maintenance skills or do you move on. I'm not sure what to tell you to do. I'm not familiar with the set up in your location. For the most part, the likelihood is that your life will not be a support-free zone, unless you're working in some product development shop, and even though I imagine the options for developing features from zero will be limited. What you do will depend on a decision which you have to make. Decide what you want to do and how you can get to do it. There is little else I can tell you in terms of what do you do |
|||
|
|
