I don't agree with this article. To me, clean and concise code is a skill that you should work to improve. When you have to solve difficult problems, that skill should be automatic and improve the entire process.
I can understand performing fewer tests in that context, because writing tests can take a lot of time. Still, a minimum number of tests that target complex code is a good idea.
And he agrees with you - "[... if] what you really want to be is a software engineer".
You can still be the designer of an experience, is what I'm saying. There shouldn't be anything lost if writing code properly is what you always do.