D
David Ferguson
I couldn't agree more with this last post by KEJR, I have been trying to write a code and graphics standard for 20+ years. The best I can do is a standard for our company as any time I try to go beyond that.....too many "experts" get involved and I get nowhere. Most don't have a clue what they are talking about and inflict "opinion". As the customer I can control some of what gets written, as a supplier when trying to implement standards, everyone "thinks" they are experts and think "your standard" stinks......most haven't thought past the first layer of that onion.
As this poster says, shoot for naming conventions, document the he%# out of your code (usually to save you) even though time consuming, try to build a library of code and graphic snippets. I have old ladder chunks of reusable code for motors, valves, sequences, interlock diagnostics etc. And I have code chunks for the same stuff in modern controllers, ie objects for motors, valves etc that I just drop in, assign tags and code done.
But the "magic" is still in process knowledge and problem solving.....as said here, with any processors old code, a bad programmer can write "spaghetti" code. With new object oriented PAC's, nothing changed only now they can create code chunks, I can now write "ravioli" code if I want to.
The software programmers book from the 70's and updated in the 90's, "The Mythical Man Month, essays in software engineering" still has concepts for writing software that apply to control code.....simplicity, reusability, design, documentation etc. This is a must read for anyone doing any code....but that requires reading it.
What is the difference between an Artist and a painter......one does houses.
Dave Ferguson
Control Systems Engineer
Sent from my iPhone
As this poster says, shoot for naming conventions, document the he%# out of your code (usually to save you) even though time consuming, try to build a library of code and graphic snippets. I have old ladder chunks of reusable code for motors, valves, sequences, interlock diagnostics etc. And I have code chunks for the same stuff in modern controllers, ie objects for motors, valves etc that I just drop in, assign tags and code done.
But the "magic" is still in process knowledge and problem solving.....as said here, with any processors old code, a bad programmer can write "spaghetti" code. With new object oriented PAC's, nothing changed only now they can create code chunks, I can now write "ravioli" code if I want to.
The software programmers book from the 70's and updated in the 90's, "The Mythical Man Month, essays in software engineering" still has concepts for writing software that apply to control code.....simplicity, reusability, design, documentation etc. This is a must read for anyone doing any code....but that requires reading it.
What is the difference between an Artist and a painter......one does houses.
Dave Ferguson
Control Systems Engineer
Sent from my iPhone