> Really? How about in industries where it's straight up impossible for the developer to do so? How do people function in those industries? How does cutting edg

> Really? How about in industries where it's straight up impossible for the developer to do so? How do people function in those industries? How does cutting edge tech get made in, say, the medical industry? > Are you suggesting that people building machines to perform brain surgery should have to go to med school and specialize as well as becoming an engineer? Consider your limitations as a developer, and having your department defer to hiring or consulting from trained and experienced medical professionals to help guide and shape what it is you are making? Along with ongoing hands on training for targeted demographic for insight and instant feedback I can't think of a way for cross-disciplinary innovation to occur. > Here's a question. What would you say to a blind programmer who is working on autonomous driving vehicles? Do you think such a person could never do a good job, because they have no experience driving a vehicle? This is an extreme, because while I'm sure blind developers exist, I'm also sure they are a small minority and are likely NOT working on main developer roles for AV; but if they were I bet they were doing so collaboratively amongst other able bodied developers who are relying on training deep learning model rather than making an if else command for his colleagues never seen 'what to do if a baby carriage steps out of your Tesla' situation. You are resorting to hyperbole to try to make a weak point and it doesn't bode well for the substance of your argument, either way I think you get what I'm trying to say, albeit some what condescending manner. You can agree or disagree with it, but I think this is a major trigger point for so many here (likely the FAANG/MANGA underlings) they know it's a bone of contention. > There are tons of extremely valid reasons why a software developer might not want to or be able to put themselves in their customer's shoes directly, without it being "white glove developer syndrome" as you put it. And they can still be excellent developers. I disagree. You can be a developer, and as noted in my preface an above competent one, but I hardly think you'd call yourself an excellent one in the presence of an actual excellent one if you've ever met one. I'm cognizant that I am not nor do I dire to be an excellent developer and I've been humbled when I have met one and they are usually obsessed and perhaps tortured by their obsessions which they are focused on; still, despite it being somewhat socially awkward it was a worthwhile experience.