Yeah, I hear all the popular wisdom about not re-inventing the wheel. It may be allowed that making some tiny wheels from scratch is good practice for beginners, but generally in real life, we shouldn't do anything of the sort.
But there are some of us who really believe that a big bloated unmaintainable mess should be chucked and something better made. Honestly, it takes me more time to figure out where in the existing source code of a component to make a small change, than it would take to just write a new whole new component from scratch in a better suited language and organized more sensibly. (How many of you ever had that thought?)
Not only that, but the kind of work I normally do, for which I get the most pay, praise, and am less likely to get fired from, is building new libraries, components, algorithms and such from scratch that app programmers can incorporate into their projects. If put in charge of a whole app (and I'm not much of an app developer) I tend to redesign some of the more annoying wheels (the square and triangular ones) so the whole thing is more the kind of vehicle the users want. I usually end up working more on the wheels than the whole.
I'm a wheelmaker, plain and simple. I can always make a new wheel that's rounder, or less weight for the same strength, than any existing wheel (at least within my domain of expertise).
I'm in a position to change jobs this summer. How should this wheelmaker's trait influence my job hunt, elevator pitch, portfolio and resume tweaking, to successfully hook up with an organization that needs wheelmakers, and avoid those who looking for someone to work within existing legacy code (my current job)?