As some of you may have seen from our Blog site (blog.almoproav.com), I posted my perspective a couple months ago on this growing notion of control system implementation really being more about leveraging web based configuration tools as opposed to code creation science projects, especially with main stream AV integration deployments.
There was an article posted very recently in Commercial Integrator Magazine that caught my eye. It seemed as though at first glance the author was very much trying to stave off what I wrote about. Not specifically to my post, but in general.
While I’m convinced that my perspective is on target, I do believe the author presents a compelling perspective on the value a programmer can bring to the table, once I read it completely. One thing is for certain, a programmer worth their weight in gold, will take the time to understand the project needs at all levels. And in fact, I would agree that really no one has a more in depth understanding, end to end. The problem is not usually that they don’t get it, it’s that they rarely know how to translate that understanding in a way that will allow for the end product to achieve the desired results for the stakeholders. That’s why it leaves an integrator vulnerable when so much rides on the man behind the curtain.
As with anything in this day and age, evolve or get left in the dust definitely applies here. What is certainly on life support are code writers sitting behind a laptop all day collecting a pay check, writing code and developing relational database architectures, while working with the constant attitude of knowing more than everyone else because they understand complex programming languages that the average human mind can’t wrap its head around. How’s that for a run on sentence…
The bottom line is this, on large, enterprise level integration projects, having programming wherewithal that gets it from top to bottom is without question invaluable. The key is (as pointed out in the article) to leverage these resources for all things impacting the project beyond the code created to run it. And manage those resources in a way that minimizes or even eliminates fiscal vulnerability.
Take a look at that article and post your thoughts and opinions here in our blog.
I look forward to hearing from you!