Maintaining Code

How would you word and sell your skill of maintaining software and code but not doing new builds? For instance one of our applications uses VB6 and requires changes from time to time. Export functions, new columns for reporting extracts even some new functionality, but never brand new builds. It's essentially software maintenance but that's it. On the database side I do a lot of new design work, stored procedures etc...

How do you sell that? How would you word it? I'm nervous to over sell but I want to take credit for making changes and deploying.

Does that make sense? I've been battling with this for a long time in regards to interviews and wording on my resume.

Thanks for any input.

Find more posts tagged with

programming

Comments

JDMurray

Explain your job in terms of the different areas of software development and maintenance where you work: requirements gathering, marketing/product planning, functional/system design, coding/implementation, testing, deployment, maintenance, documentation, and customer support. What did you do when and where?

And VB6? That was my main programming language from 1998 to 2008. (I started with VB3 back in 1993.) I began transitioning to .NET programming in 2004, but new projects kept wanting stuff built in good ole' VB6. Like COBOL, VB will keep programmers maintaining legacy code forever.