I'll chime in because you describe me to a tee. I'm a "maker", and a tinkerer. The science doesn't really interest me near as much as the tools available to ma

I'll chime in because you describe me to a tee. I'm a "maker", and a tinkerer. The science doesn't really interest me near as much as the tools available to make things. And, when I try to dive into the science I get overwhelmed and feel like I cannot keep up. The overviews are often interesting, but deeper dives are very difficult to make because they're hard to keep up with and what I really want to do is make something. I've been pondering this very issue myself, and I'm leaning towards thinking there should be a clearer line between the too (CS & developers). I work with open source APIs and languages. I don't need to know about the guts of Javascript or processors to make apps. I need to know how to use the language and the APIs that make that easy for me. And that, just in and of itself, is a career choice that's quite different than CS. I'm using the tools the CS folks make easy for me to use to build apps and people like me can get very good at that, but it's an entirely different kind of person that's good at CS. Those folks are at a different, higher level of understanding how things work than people like me. What I do is akin to making cars out of parts engineers have designed.