I think it depends on the design approach used. If we go with user-centred design and see our main goal as representing the user in the delivery of a product, then I would see it as an advantage not to code. Else the perspective will be skewed too far towards the technologist view, away from the user view. But as Alan points out, “there is a tremendous breadth of skills, tasks, and job roles in the software development world”. And some of these should be able to code. Some of them explicitly should not, I reckon.