No, why not familiarize yourself with operating system concepts. It will be a lot more use. Maybe after that learn to code.<p>I am a developer. If I am installing a piece of third party software and it doesn't work, the last thing I am going to do is to dig into the code. It more likely that an environmental variable needs set, or a library is missing. No coding knowledge required to fix these things, but an understanding of how everything fits together is.<p>(Getting bored of these kind of statements from Obama and the likes).
I think many developers are missing out on an opportunity to further their field.<p>With understanding comes respect. With respect comes the opportunity to have an informed discussion about ex. a project and why it's going wrong. A discussion where you as a developer do not feel like you are speaking to a black hole.<p>I never understood why so many developers are against this. Overall it's to your benefit.
I actually disagree. Maybe this sounds like nitpicking, but I think it would be much more beneficial for non-technical people to be familiar with high-level, commercially used concepts in computing such as servers, databases, how the web works, and how data is managed in general. At least to me, learning 'code' has the connotation of learning the bare minimum to make a web app. Maybe I'm wrong, but that's what most of these 'learn to code' initiatives seem to push and it gives people the wrong idea on how much they've really learned.
Coding is not the literacy of the future, nor will knowing how to code let you use many software products easier to use. If you have to know how to code to use software products, then we as programmers have failed. One does not need to be a mechanic to drive, to be a doctor to be healthy, or an director to enjoy a movie.
Can it help you be more analytical, sure, and that might be a reason to learn to code.
My 2 cents... This is not easy. Understanding coding has a much higher barrier to entry than simple proficiency in other under-utilized fields like Statistics and Economics. It is very hard to say this is something EVERYONE needs to know.
Basically an article that says a lot without saying anything at all. Learn to code if you want to or if you need to, but stop pretending that knowing how to write some markup, trying out a REPL or writing some quick scripts will give you some mystical insight as to how software works. Then of course "coding" by itself doesn't mean anything without elaborating on the particular paradigm and language properties.<p><i>At Axiom Zen we use tools such as Google Analytics for tracking interactions with our material, GitHub for internal collaboration and project management, and Intercom to connect with our users as well as monitor their use of our products. Without a foundation in coding, it would have taken me much longer to adopt these tools.</i><p>Really? At best, when it comes to Git, you're just learning a file system model and basic use of a shell. Assuming you're not using a GUI or GitHub's browser interface, which is likely.<p>I like people learning to code by their own volition. I don't like vapid fluff.