Comment by Manuel_D

Some good advice here, some things are rather dramatic. I do like the encouragement to highlight the value you bring to the company. But "don't call yourself a programmer" is a bit dramatic. Highlighting your ability to program is pretty important.

The way I typically try to highlight my development contributions - if it isn't direct user-facing feature development - is to portray my software as internal "mini salesforce" for niche high value tasks for other employees. For instance at my first internship I automated manual tasks like thumbnail creation, searching and calculating market share of our company, and other tasks. It's fine to call yourself a programmer, just be sure to emphasize "I program X and Y that are crucial for teams A and B".