I'm not sure what your way is exactly but I also treat coding as a craft and I'd say it's far more commercially viable than what most other devs are doing. I design systems that are efficient, do what they need to do and nothing else, are well tested, quite easy to understand, work with and change etc.
The only thing about my way of working that I have commercial viability issues with is when I take over someone else's work and insist on basically rewriting the entire thing before actually continuing the work. I don't always do that, some projects are just too big and some are just fine, some projects don't need me to rewrite them. But most systems I've inherited have been absolute ass and I just refuse to build on a total shit foundation. First I fix the foundation, then I build on it. You want a code monkey to duct tape things together and add workarounds on top of workarounds until the codebase looks like Escher's stairs painting you'll have to find someone else to do it. I fix problems I don't just paint over them.
That has been a problem in some situations in the past but for the most part my work has been appreciated.
The biggest thing, is that I insist on doing things my way, which is a hideous chimera of cutting-edge, buzzword-compliant techniques, melded with ancient techniques I learned when I was programming in Machine Code.
Also, I insist on doing extremely high Quality work, and that seems to be very much out of favor, these days.
Just try starting a discussion on improving software Quality, hereabouts, and see how it goes.
For some reason, folks are actually actively against improving code Quality, and that is something that I can't comprehend, so I have to admit that I'm very much a "dinosaur."
The only thing about my way of working that I have commercial viability issues with is when I take over someone else's work and insist on basically rewriting the entire thing before actually continuing the work. I don't always do that, some projects are just too big and some are just fine, some projects don't need me to rewrite them. But most systems I've inherited have been absolute ass and I just refuse to build on a total shit foundation. First I fix the foundation, then I build on it. You want a code monkey to duct tape things together and add workarounds on top of workarounds until the codebase looks like Escher's stairs painting you'll have to find someone else to do it. I fix problems I don't just paint over them.
That has been a problem in some situations in the past but for the most part my work has been appreciated.