And learning CS to write programs is like learning to design combustion engines to drive a car.
Sometimes.
But often people will “write programs” without a decent understanding of the underlying layers and principles or foundation on which the technology is built. (Even some CS majors will do this.) this will result in weird bugs and behaviors they cannot understand or debug. Meanwhile their peers and managers have begun to use and rely on these programs and even integrate them into larger processes and workflows. Once the bugs start showing up, now you’ve got a big problem.
There are also some basics you’d probably won’t even register breaking without experience, going as far as pushing user credentials and personal data to an open git repository. I did that in my second pet project with just my temp keys to the cloud API, and github flagged that immediately. I guess, having at least the briefiest knowledge could’ve helped newbies avoid errors like that.
Sometimes.
But often people will “write programs” without a decent understanding of the underlying layers and principles or foundation on which the technology is built. (Even some CS majors will do this.) this will result in weird bugs and behaviors they cannot understand or debug. Meanwhile their peers and managers have begun to use and rely on these programs and even integrate them into larger processes and workflows. Once the bugs start showing up, now you’ve got a big problem.
There are also some basics you’d probably won’t even register breaking without experience, going as far as pushing user credentials and personal data to an open git repository. I did that in my second pet project with just my temp keys to the cloud API, and github flagged that immediately. I guess, having at least the briefiest knowledge could’ve helped newbies avoid errors like that.