Earlier quoted context omitted.
I'm a software developer too. Mostly mobile and backend. On the mobile part, most of the clients have pretty much no idea what a processor really is, or how networks work. Hell, I have to explain to them that if they want to build this kittens social network, they're going to need a back-end and that no, it doesn't matter to the mobile apps what language their back-end is written in (and vice-versa). For most of what…
Software scientist != software/hardware engineer != software/hardware developer != programmer/coder. Programmer must know how to program . Software developer must know how to make good software product . Software engineer must know how to understand and meet specifications , follow engineering codex, and son on. And so on. I'm talking about software developers . You are showing me examples unrelated to professional s…
I'm talking about people who are one of the or the only persons with any technical knowledge in their companies, who's job it is to interpret and understand whatever the requirements are and deliver on the products, wether it's apps, web or mobile, back-ends or both.
They need to know how to make good software products, they definitely should know how to understand and meet specifications, etc, etc, etc. They just don't. And yet, they have the positions they have. And what they're most lacking, contrary to the point you were making earlier, definitely isn't compiler theory or the ability to build shell scripting parsers, but the very abilities you just listed.
So no, we are talking about the exact same thing, you just seem lucky enough not to have encountered this kind of people in that kind of position, and I'm glad we have finally come to an understanding.