Disagree. I wrote this article because I kept meeting people who were non-technical but they were afraid of technology.
If they learn to code, even if they don't do it well, they will be able to talk the same language and get people on their team to build what they want.
I never said don't build your network. Just get some common ground first.
I'm aware you didn't say don't build your network (you didn't specifically point to doing so, but it's not my intention to call you out for not doing so). I also like the idea of a non-technical person getting their feet wet as to shake the fear of technology. However, there is quite a difference between getting your feet wet and living in the ocean.
I also couldn't disagree more about them learning to code equates to talking the same language. That's what I call "smart enough to be dangerous". It gives them a false sense of security and can lead to them making decisions up the business chain without consulting the development team because they now "speak our language".
A non-technical person who doesn't have a true desire to become a developer shouldn't be dictating directly to a development team. That's why you have TPMs and Business Analysts (in larger companies) and in smaller teams hopefully you're using some sort of Agile process whereby business desires (stories) are translated into tasks for the dev team.
If they learn to code, even if they don't do it well, they will be able to talk the same language and get people on their team to build what they want.
I never said don't build your network. Just get some common ground first.