You're stating

> you're not really paid for agonizing over eloquent or great code, but just code that "gets the job done".

Somebody might interpret this statement as if nobody (in their context) should worry about writing good code. If you're writing good or bad code it doesn't matter as long as it works. Package and ship it and call it a day.

But the author addresses this:

> It's not even about good work. This is also a given. That's the default expectation, it's part of the package. The cake will be good.

Then I'd say that you're paid for "good code that gets the job done".