[lowercased]

yeah, I was going to pound this home a bit more, but was seeing some other people already did.

Coming back to this, one of the defenses I've had from CS people who couldn't do day to day development all that well is "well... that's not what CS is for - it's really for diving deep in to the theories behind problems... " - or some other relative claptrap. On its own - yeah, there's a class of problems that are served well by people with a CS-focus. Just don't try to drop them in to a "developer" role and assume that they'll be "just as good or even better" than someone who's simply been doing development perhaps with minimal schooling or just self-taught. One skill isn't really a superset of the other, but some people tend to think of them as such.

[detail-oriented]

Agreed. The main point is that a CS degree is not a proxy for success in all things that require code. I like to keep in mind that a BS in CS only demonstrates the ability to study, memorize and be quized on your memory. Using a set of axioms to build something unique is totally different.