No, because that would be very short-sigthed...

Software is seldom done when finished, but continuosly
developed and maintained. And there is always new software
to be written.

To fire that kind of developer would be like shooting one
self in the foot. A one time sale, and the customer will never
return when he see quality recline.

all that in addition to, of course, professionalism and
pride in ones work.

It looks like a challenge, but I thought I would give it a try
(gosh, this is like a chess game). So, here is my 2 cents.

The reality may be that your employer likes you more if you write high
quality code and keeps you on the job. If so, you continue to write
high quality code and be happy. If not, maybe that employer is not good
for you anyway, and you find an employer that is as above.

But suppose that the above is true and a good employer is more likely
to dump you if you write high quality code.
Then, it may still be good for yourself to write high quality code, add
documentation, etc. because of your own sanity. As a programmer, you
may have an easier time if you do that as the code is easier to
develop, add features to, refactor, change, etc. You save yourself the
stress and possible guilt for degrading your ability.
If this is true and your employer, indeed, replaces you with cheap
scamers, then, he will get into trouble because the code will decay
over time and the cost of developing and maintaining will increase
despite the cheapness of the scamers. Let alone effort, time is also
important, which will tend to increase as new requests come.

Your employer will hopefully learn this. By the time, you will be off
the job. But if this is true, you will hopefully find an employer that
already has learned this in the past.

If so, then it is no real problem for you and there is no good reason
for you to change your high quality style to a low one. (You may
additionally learn how to find the job and environment you are more
suited for.)

Continuing the analysis, if no employer can ever learn that from the
experience alone, it may be worth finding ways communicating it. There,
some skills of communication and assertiveness may be required. You
will have the option to acquire such skills instead of changing your
coding style. I'd do that because it is a motivation to improve
yourself while the letter would feel bad.

hope you like my analysis...

alex

   The company I work for provides "IT solutions". We are called in, given
code written by someone else, make modifications to it, and give them the
new code.

   Invariably, the code we're given is always total crap. Why is this?

   Because if the code were good, they wouldn't have to have hired experts
like us to go in and clean up the mess.

   Firing your good coders in exchange for cheap scamers is a losing
strategy in the long run because it means you'll eventually have to call in
outside consultants like us, and we're very expensive.

   - Oliver

To write working and maintainable applications with good
documentation is our goal.  Once we have delivered we
are soon forgotten.  If we are very good we are never
remembered and the application continues to work until
requirements change.  We move on to other paths.
That is our way.