I run a contract shop and all my best DB guys are greybeards... coasting. It doesn't matter, after so many years with postgres & MySQL they are amazing.
I would probably differentiate by work visibility: good work in DBA/sysadmin/security/accounting/quality is invisible, you only notice those folks when they have screwed up.
With product/UX/new features it's the other way around, coasting is not possible.
That very much depends on the application. I maintain some enterprise solutions for customers. Clients get upset if UI has flow changes. Also, changes don't make me money unless they are required for a new customer. I will do it on request and invoice for the work but no one is interested in change for the most part. I think this is VERY common in enterprise software.
There was a time when machismo was my middle name (much younger) and would have seen that as necessary for a successful startup. Now that I have several startups behind me I see it as simply bad management which decreases your chance for success which is stacked against you from the beginning anyway.
That was several years ago. I don't think that startup exist any longer.
Here right now the age vibe is coming from ;) It's not like a doctor can coast it out (or maybe I'm also naive).
(I'm an employer as of now)