Whether my statistics are right or wrong they were never intended to be 100% accurate, it was only a prop to describe the problem I'm facing with writing articles about automation from a developer's point of view. Ask people what "the cloud" means to them for instance, and depending on someone's exposure, their description of that term may differ quite a bit from that of someone else's.
Automation programming is my career, I think about automation in terms of controlling stuff through code, but in a very broad sense. For people that don't do this for a career, they may have a much more narrow idea about automation. Even if that is true, I would like to know what automation means to those people as developers, and what kinds of things they are trying and struggling with.
As you might be able to tell, and as Corrine has seemed to acknowledge, the developer audience is more of my real target. I would like to write about things that the general developer population can relate to and not just people in my area of expertise as I think it would be very unlikely that the majority of developers out there have the same type of hardware or resources in front of them as I do.
I can only speak from my own experience, and that's what I'm trying to do in order to explain my issue -- Try to take things in a much lesser literal sense.
Even if automation isn't about networking, I bet you that is the idea that most networking people have, because of their exposure to those kinds of devices. Look at any device today that you can control: TV's, power plugs, speakers, media players, then calculate the percentage of those devices that can't be controlled over the network. I can control my smart TV over the network, including my Apple TV, Sonos player, Philips Hue Lighting system, belken outlet plugs, and many more things.
As for a date on my article:
It is dated, maybe it's the fact that the text is too light to be noticeable which indicates that I should look into making it a bit easier for my readers to see?
Yes but on a very different topic I think. You're still talking about my article -- and I'm asking about automation topics that I should be targeting. The article I shouldn't even have posted really but I threw it in here as it seemed related to what I was trying to blog about at that point in time. I appreciate your insight, but it appears I haven't guided you in the right direction.
I'm not disregarding your advice, but I need less definitions and more hot topics dealing with equipment automation for the developer audience.
