Earlier quoted context omitted.
We have zero Honeybadger errors, performance is acceptable for all our routes in the application, and all of our key stakeholders are ecstatic about what we've built. Is there some other metric I should be measuring our code by?
What about the actual users? If this works for you, go ahead, I can't stop you. But this is not software craftsmanship, or even software engineering. Don't act like it is.
Sorry, perhaps I wasn't clear—we write business software. The "key stakeholders" are the users. And they're ecstatic. They love what we're building.
I'd actually say it's both craftsmanship and engineering. :)