This depends greatly on the situation. If one is employed in a very large corporation the different aspects of development will likely be divided enough that there is little to no overlap between the positions. Designers figure out the UI/UX and the front end programmers implement it. As the size of the venture decreases the overlap between positions does as well and interdisciplinary knowledge becomes more relevant. But regardless of all of that I would argue it is always a strength to understand the context in which you work even if you do not directly have to make use of that knowledge, so you can better understand your colleagues' efforts. This includes both programmers understanding the value of design and the design process as well as designers understanding some of the programming that has to happen to bring their designs to life - this will also allow for making informed choices of design based on how difficult an idea may be to work with for the programmers - though a conversation should happen regardless as the programming team will be the experts even if the designers develop a baseline skill. Likewise of course programmers may be opinionated about design ideas but probably should respect expertise of designers in their field.... In both cases, not accounting for incompetence existing 😛