
I like to keep myself abreast of the latest engineering standards and practices from international organizations (API / ISO) and from engineering / operating companies. The best thing about them is I don't have to overload my memory trying to remember established engineering and design practices which are generally well documented in these standards. These standards also help me save time when I am involved in engineering design, and often I quote these standards in the engineering design documentation that I prepare. So reading, knowing and remembering (depending on how good your memory is) these standards apparently seems to be the key for success in any engineering work.
So far, so good. Now here comes the flip side. These standards and practices have been developed by fallible humans and are not commandments from god. These standards and practices have evolved over the years and are still getting refined which is evident from the revisions that periodically appear for them. These standards are also written, reviewed and approved by a group of people and organizations who claim that they are the best and most authentic source of information on the particular subject. I am not saying that the credentials of these people and organizations are questionable. My point here is, that there can always be a difference of opinion amongst indviduals or groups on how things should be done (read engineering design).
What "A" expresses as his opinion about the methodology to be adopted may not be agreed by "B" based on different experiences by "A" and "B". However, both "A" and "B" need to provide logical explanation of their ideas and be able to state benefits and disadvantages of their way of doing things. This is what we call as logical progression of any idea and the process of adoption / elimination of the idea based on the end goal to be achieved.
What I see today in the younger lot of engineers is the blind adherence to standards and practices without application of logic, functionality and end goal to be achieved. I do believe, that a lot of it has to do with lack of experience but to a certain extent it can also be attributed to finding a easy way out. It is there in the standard so who wants to take the pains to uncover the logic behind it.
When I mention all of this, I am not decrying the standards and practices. A lot of the engineering practices prevalent today and documented in these standards and practices have stood the test of time and have evolved and matured to the extent that trying to research them further is simply a waste of precious time, especially if you are an engineer.
My advice to the young entry level engineers is that when you read a standard or practice, try to analyze the logic behind it. Ask questions about it to the more experienced engineers. There will be occasions where even the more experienced engineer may say "Hey, I reckon this is the way it always has been and I can't help you anymore". It would be easy to give up if you get such an answer, but then think that everything has a logic and somebody out there knows that logic and you need to have the resilience to find out that logic.
Good luck to all of you young engineers in making the effort to find out the logic on what is written as a standard or practice. I will be more than happy to receive comments on this blog entry.
Regards,
Ankur.
Ankur,
Gracias por el aporte, mucho de lo que dices es verdad, recién tengo un año y medio laborando como Ingeniero de procesos y he podido observar cosas como las que mencionas, siempre he tratado de buscar la lógica a lo indicado en las normas, buenas prácticas o reglamentos, y en esa búsqueda también me he topado con personas (ingenieros mayores) que simplemente han venido haciendo las cosas por que nadie se las ha cuestionado y ellos tampoco a si mismos.
Aquellas personas que escribieron aquellas normas, recomendaciones, etc, han de haber tenido alguna razón y no es que haya sido algo tirado de los pelos (aunque uno nunca sabe).
Saludos
Luis Ramos.