You take me the wrong way - please note
Unfortunately most of the world do not understand our Ozzie sense of humour!
I have never been afraid of being replaced either - if it ever happened so be it.
It is nice to have time to examine things logically and methodically but when there is a line down, production stopped, workers sitting around - you just have to do what you have to do very quickly to get production up again.
I do understand both sides as I have my pieces of paper but I started on the other side then got my bits of paper. I still think it is the better way to start out as I found myself that understanding the real world actually helped me substantially in the academic world - certainly meant I ruffled some lecturers feathers though!
Good luck but get some practical first - it will make you far more valuable to a prospective employer.
I was not meaning to be hostile at all!Learn about control systems, design and implementation, control circuit design, trouble shooting including hard wired logic. Most control systems have hard wired logic.
Unfortunately most of the world do not understand our Ozzie sense of humour!
I have never been afraid of being replaced either - if it ever happened so be it.
Exactly what I intended to convey. Without field experience all the bits of paper in the world are useless as things are totally different in the academic and real worlds. The basic principles are the same but the execution is totally different.I think what BobB was implying is what I believe: Get some field experience, then go to school. Advanced schooling is kinda lost on someone who doesn't yet even know what they don't know. Without the experience of installing and trouble-shooting, how do you even know where best to focus your time, money, and attention at school? Apprentice type training is exceptionally valuable. It is so (sadly) common today to find folks who have no concept of how SCADA knows whether a valve is open or shut, much less how to cause it to change position or modulate. Experienced people will tell you that those basics are key. Then get into database mastery, when you fully understand what it is you actually are documenting. This is not eloquent, but I hope you take it in the vein it is intended.
It is nice to have time to examine things logically and methodically but when there is a line down, production stopped, workers sitting around - you just have to do what you have to do very quickly to get production up again.
I do understand both sides as I have my pieces of paper but I started on the other side then got my bits of paper. I still think it is the better way to start out as I found myself that understanding the real world actually helped me substantially in the academic world - certainly meant I ruffled some lecturers feathers though!
Good luck but get some practical first - it will make you far more valuable to a prospective employer.
This was a very serious suggestion.I would try to get a job in a systems house if I were you - they have people from virtually every discipline and they all learn from each other. They also work as a team - read plenty of spread sheets running around between the various disciplines.