This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

You don't need practical skills to be an engineer

Hi,


Ok, that's a deliberately provocative thread title, but it's one I'm willing to defend. But let's go back a bit first...


There have been various discussions on these forums over very many years where someone says in passing statements such us "CEng now needs a Masters degree, but Master students come out with no practical skills". Of course I'm paraphrasing greatly, but I'm sure people will get the idea. Similarly I've heard the view expressed at many engineering gatherings of "our graduates come in not knowing how to solder / use a spanner / wire a plug". Now I'm sure often these statements are perfectly true for many of those entering the engineering profession, the question is whether it matters. And I'd argue that much of the time it does not, and that it's important that we debate this. (Hence this thread!)


To give my own perspective on this, my background is as an analogue audio frequency design engineer, with my postgraduate entry level jobs to this role being as a maintenance and then test engineer. Back in the 1980s I did need to dismantle, solder, and mantle again. My first development roles were based around soldering irons and test equipment. By the early '90s my analogue development team was based around modelling tools, our prototypes were surface mount, and although we used manual test equipment the amount of building  / modifying we did was tiny - and ideas and the ability to play around with them were FAR more important than practical skills. Then our world went digital. Analogue modelling had improved the performance of our systems 10 fold, digital systems improved the possibilities 100 fold. The digital teams needed no practical skills whatsoever, but my goodness they did  - and do - some fabulous engineering.


Of course, there is still a real world to interface this technology to. And this is where the key word in the subject of this post comes in - that word "need". We do need a proportion of engineers to have practical skills to cope with the real world interface, but we don't need every engineer to have those skills to contribute to a team. For me this is summed up beautifully by my one and only patent (sadly not renewed, eu EP2100792 (A1)  if anyone's interested!). There are five of us named on it, these are:

  • A mathematical modeller

  • A DSP on FPGA implementer

  • An analogue electronic systems modeller / application specialist

  • A hardware developer

  • A manager / systems integrator / systems concept engineer / patent author and general herder of cats (me)


Only one of these needed practical skills. And yet this was an extraordinary engineering innovation. I'm allowed to say that as I didn't do the really clever bits, my main role was to bring the skills together and enable them - and that's the point. None of these people could have come up with the overall solution by themselves, that's why all are named on the patent.


So I would - and do - argue very strongly that an excellent engineering innovation team needs three skill sets within it:
  • Practical skills

  • Theoretical skills

  • Human skills


And the best teams have the best people in each of those areas, working together and respecting each other. So a mathematical modeller knows their system is "garbage in, garbage out", and works with those with application knowledge to help them refine their models. And a prototyping engineer knows their prototype is useless with no software to run on it. And they all know they will make mistakes, and will have misunderstandings, and so managing the human side of the development is vital. Working in this atmosphere of mutual respect is tremendous. Been there, done that. Working in an atmosphere of silos, sneering, one-upmanship, and inverted or verted snobbery is destructive and, I submit to the court your honour, produces poor engineering (by any measure). Been there, done that, left the company (a long time ago).


Now there is an argument, I've used it myself, that practical experience helps develop problem solving skills. And for some engineering activities I would support this. However a lot of modern engineering is based around very deep mathematical modelling, that's how we've achieved the fantastic advances in, for example, communications and data management we have over the past 20 years. So we have to accept that those involved will become abstracted from the "real world", it's then a management problem to manage the interfaces. In my present field, safety engineering, it is a reality that software engineers will implement what they are asked to implement. There's a whole other level first to define those implementation requirements correctly and thoroughly, which requires a different skill set. (And validating is a different skill again.)


So can I propose that we stop saying "engineers coming out of university with no practical skills is a Bad Thing" and similar statements - but I am very willing to support the statement "not enough engineers coming into the profession with practical skills is a Bad Thing".


Thoughts?


By the way, bizarrely my practical engineering skills are now way better than they were in my 20s when I actually needed them for work, partly due to experience, mainly unfortunately due to medical issues at the time. In fact (as one or two of my more "old school" supervisors delighted in pointing out) I was pretty cack-handed. (I just checked, cack-handed is not rude!) I'd like to pass on my appreciation to those enlightened managers who realised that my problem solving skills meant that I was valuable - they just needed to make sure that nothing I touched ever made its way to a customer! There is a VERY serious point here, I could easily have been put off engineering for life with that attitude of "you're cack-handed, therefore you're an incompetent engineer". Although I do apologise in retrospect to the The Kinks for any reliability issues in the mixing desk they bought in 1985 which I worked on rather a lot, probably the product that has gone into service which has more of my personal soldering in than any other...I did get one of my more dexterous colleagues to check it over very thoroughly before it went out!


Thanks,


Andy
  • Hmmmm...

    Two thoughts (having very quickly read this whilst procrastinating on a major work problem!):
    1. I'd sort of like to agree with the idea behind these definitions, not out of "elitism" (an engineering technologist to these definitions could be organisationally superior to a professional engineer) but out of clarity.

    • However, I can't see - to take just a couple of examples - that in the UK a senior engineering officer in the forces or the senior engineer on an oil rig will accept being potentially recategorised as an "engineering technologist" rather than a "professional engineer". Just as they would currently object (rightly or wrongly) to being IEng rather than CEng.


    I'd almost say that this whole business of trying to formally "categorise" engineers is a complete waste of time and effort - as indeed a large part of private sector engineering already does. The only reason I do support bits of it is because I find the third party accreditation that CEng / IEng provides is valuable (partial) evidence of competence for safety cases. And I think it's personally very useful for engineers to benchmark themselves against what I see as good practice standards - which is I'm very happy to promote the UKSpec process.


    Probably this is all being approached from the wrong angle - if it was started from (for example) "what legally should only a CEng / Professional Engineer be allowed to do" the definitions of titles would probably get much clearer. But that's straying into the "Time for licenced Engineers?" thread.


    Cheers,


    Andy
  • I thought it might be helpful to reference The International Engineering Alliance definitions of “Engineer”, “Technologist” and “Technician”.  http://www.ieagreements.org/assets/Uploads/Documents/Policy/Graduate-Attributes-and-Professional-Competencies.pdf 

     

    Naturally this refers to the practical emphasis of “Technicians”. However it defines “Engineers” primarily by attributes that might most commonly be associated with fundamental research and development type activities that are “science led”. Arguably, most of what would be regarded as “Engineering” as carried out by  Chartered and Incorporated Engineers in the UK, Eur Ing and the “mainstream” of engineering practice throughout the world, would fall within the definition of a “Technologist".

  • Hi Roy,


    really like that idea of a "registered engineer"! Take five house points smiley (Do schools still have house points?)


    As I expect I've said before, I do have a problem with that word "elite" as it has unhelpful connotations. I don't consider myself as any more worthy of saving from a sinking ship than someone with EngTech, IEng,  or indeed someone with GCSE D&T. However, I do feel competent to take personal responsibility to sign off novel safety critical designs within my area of expertise, and hence feel perfectly justified in being CEng. But as you suggest, trying to correlate my education and training with why my employer, myself, UKAS and the IET all think I am at that level of competence would probably be impossible. What I like about the IET's implementation of the UKSpec process is that it focuses on how you are actually doing your work today. Personally I find the exemplifying qualifications a bit of a red herring - although it's useful guidance to give an idea of the level of technical understanding expected at each level. Maybe the next version of UKSpec will have better wording on this point???


    On the "am I an engineer?" point, I find this a completely invalid question. If I was introducing myself professionally I would never say "I am an engineer". At present I'm a safety assurance engineer, I've been (working backwards) a manufacturing engineering manager, a safety critical equipment design engineering manager, an electronics design engineering manager, an analogue electronics design engineer, an analogue electronics design engineering team leader, an electronics design engineer, an electronics test engineer, and an electronics maintenance engineer. Without the qualifying wording the description would be misleading. I know many engineers would like to be able to simply say "I'm an engineer and I'm proud" (hence all the calls for regulating the title), personally I'm very pragmatic that we are where we are, and we just have to be a bit bullish about using more exact titles that will make sense. (Incidentally I've more or less bludgeoned the words "engineer"/"engineering" into many of those job titles, in many cases I didn't tend to use it at the time. For example I used to call myself an "electronics designer" rather than an "electronics design engineer" as it seemed to make more sense to people - otherwise they tended to expect me to have practical skills smiley) To go back to the medical example, immediately following a car crash a paramedic is likely to be a darn site more use than a brain surgeon, they are both "medical professionals", and the surgeon may be seen by some as having higher "status", but the important question is which one you need at the time!


    Or in other words: yes, I agree!


    Cheers,


    Andy
  • Roy, as always, an excellent post with great insight!. When PRAing, I always try to ensure that everyone achieves what they deserve. This can be hard work, sometimes because candidates have real difficulty in self-assessment and in writing down what they have achieved, but sometimes they come up against what I call someone with the old school attitude, who still hasn't adopted the inclusive nature of the IET. There are usually ways of getting around this, but I can never guarantee that justice will always be done!
  • Oops! I wasn't feeling well last evening and missed a couple of typos.


    "Once the academic benchmark was moved to bachelors level, it became what CEng was, with CEng supposedly moving to become a “masters level elite”. However, to avoid misunderstanding, I don't think that this happened, although some people might disagree."
  • Andy, thanks for picking up on some of my reflections with some excellent thoughts of your own. I didn’t share my own story for the self-indulgence of “everyone’s favourite story –themselves” but to create debate.

     



    Readers can form a judgment about my career story, during which I didn’t meet the requirements of CEng at any time. Some would probably opine that I'm not a "proper engineer" but a Technician with added management or an "associate professional". That's fine, but fortunately, I have some other achievements to counterbalance any negativity that this might imply. Others who have continued to work as “engineers” may feel diminished and insulted by such a judgment. Their sense of grievance being stoked by the large numbers of CEng registrants who retain the designation as an "honour" often based on meeting academic+experience requirements of decades ago. Those who have been evaluated against UK-SPEC are actually a small minority. I see no benefit in taking CEng off anyone except for malpractice, but PEI "supervision" of registrants (such as voluntary supportive review) has historically been virtually nil.

     



    When the IET came into being, it chose an "inclusive" approach to membership, IMechE and ICE have eventually followed a similar path. However, other influential PEI constituents of Engineering Council want to maintain a much more "exclusive" model, intended to promote Chartered Engineers as being a "superior highly intellectual elite". I can empathise with that position, since most have studied hard, developed to a high standard, been sold “superior status”and are naturally resistant to diluting it. A significant proportion of our own members may feel similarly, but have accepted that suitably competent people should be registered as CEng using UK-SPEC.

     



    My main concern is what proposition are we offering to those who develop "engineering" careers. Arguably, to all of those except entrants to CEng accredited (Washington Accord type) Degrees it is a confused, inconsistent, potentially unfair and often partly negative one.

     



    The IET and some other PEIs have begun to offer more support to Apprentices or Undergraduates studying "different but equally valuable" (according QAA at least) types of technical degrees. Unfortunately,however, as they begin to progress their careers they may discover that they have been placed on to the "second class" pathway to start with. A Degree Apprentice for example, may be placed at a disadvantage in the Engineering Council world, even if their workplace contribution is much greater than peer colleague with “more maths” from the first year of their course.

     



    They may also find that if they progress into project engineering or management then, “that isn't chartered", unless you have the right degree, in which case it is. If your work is mainly the application of established technologies “that isn't chartered either”, unless you have the right degree then it is, likewise how do we define "creativity and innovation" - having the right degree!

     



    Is there good evidence about the usefulness of “good” and “not so Good” types of degree and are there proven correlations with relative performance across a reasonable range of engineering roles? If there isn't any proof of a strong correlation, then the education system is just deciding preemptively about the performance of engineers practice some years later. This isn't valid or fair! A childhood IQ test might have similar predictive validity?

     



    I'm not seeking to discourage academic excellence, but diminishing and excluding other engineers with slightly different optimisation, isn't “excellence”, it is naïve and counter-productive to the common good. Fine for bureaucrats, rule makers, box tickers and status seekers, but of very little value to most engineers, which may be a reason why many of them don't engage. Incidentally I have very strongly supported programmes such as Engineering Gateways, which help to develop and give academic value to work-based learning once it has been acquired.

     



    My suggestion to help bear down upon this “academic 1st class, vocational 2nd class” attitude which drives some of this snobbery and counter snobbery, is just to decide that as professional Engineers and Technicians we don't want to be Snobs or Counter-Snobs. Just like we don't want to be Sexists or Racists. We just want to develop our collective contribution to society. This is my interpretation of “Working to Engineer a Better World”.

     



    We can and should add value by supporting the registration of competent Technicians & Engineers committed to professional conduct. Defining that distinction isn't easy, but we have UK-SPEC to start with. The idea that Engineers beyond graduate level sit in different “silos” via academic selection is “artificial” and I think discredited.

     



    When HNC/HND engineers were excluded from CEng decades ago, they had to form a new category of their own and they adopted the “more practical” value statement. However this distinctive proposition and the market that it served has been in decline for decades. Once the academic benchmark was moved to bachelors level, it became what CEng was, with CEng supposedly moving to become a “masters level elite”. However, to avoid misunderstanding, I don't think that this didn't happened, although some people might disagree.

     



    Where this leads me, is that if professional engineers of graduate standard are on the same pathway then there is no “us and them”, everyone should be a “registered engineer”first. Then after a significant period of monitoring by their institution, they may be transferred to CEng.


     



    Perhaps before we leave the EU, we can borrow the Eur Ing criteria for our “Registered Engineer”? https://www.feani.org/feani/eur-ing-title/what-eur-ing-title.



    A couple of key extracts



    Education and experience together is less than the minimum seven years' formation required, the balance to seven years should be covered by education (U), experience (E), or training (T) monitored by the approved engineering institutions, or by preliminary engineering professional experience.



    The duration of professional engineering experience shall be at least two years and include the following:




    • The solution of problems requiring the application of engineering science in the fields such as research, development, design, production, construction, installation, maintenance, engineering sales and marketing, and Management or guiding of technical staff or The financial, economical, statutory or legal aspects of engineering tasks, or Industrial and/or environmental problem solving.



    My underlining is mine, illustrating where I have have frequently encountered opinions that this is “not CEng, but IEng work”, based on interpretation of UK-SPEC. Of course Engineering Council barred Incorporated Engineers from Eur Ing registration, even if they met the requirements.

     



    If we adopted something around Eur Ing as our “mainstream” standard with CEng on top (beyond most UK charterships) some adaptation would be needed to avoid blocking those on the underlined career paths from progression. Would that be possible or acceptable - does anyone have an opinion?


  • Many thanks for excellent comments!


    Mark: re your point "You don't necessarily need practical skills to be an engineer" of course I completely agree - I was being deliberately provocative with the title! I'd just got slightly frustrated with a few water cooler instances recently of engineers being rude and condescending about other, perfectly competent, engineers for having "no practical skills". And hopefully it's clear I also completely agree with Alasdair's (and other people's) points that we need the whole range of skills, and they don't all need to be in the same person. If we start hearing engineers belittling others for having "no maths skills" or "no creativity" we must equally bring it up. It's just unfortunate that "no practical skills" seems to have become a bit of a meme.


    Roy: Fantastic food for thought. To follow up a few points:

    My early education emphasised knowledge of facts rather than analysis or the presentation of ideas/concepts



    You could spin a whole piece of PhD research into engineering education and development on that! (And people have.) I suspect that actually all professions are like this, some sections believe that excellence is about assimilating facts and knowledge (and skills), other sections believe it's about ideas and concepts. In fact both are needed. But I find this particularly interesting with regard to engineering as I've always regarded it as a creative subject and hence something that can't (just) be taught. I don't just want to know what the previous engineer did and repeat it, I want to improve on it. Now to be fair this meant I was probably a bit blind in my early career to the excellent lessons that can be learnt from past practice, but fair enough we all (hopefully) gain perspective as we get older. But once again I think this is horses for courses, we need a real mixture in the profession of solid knowledge of current best practice together with a willingness to break the mould and try something new. And again these don't all have to be in one person, although this is probably the area where it is most challenging to get people with these different perspectives to respect each others views - but it can be done.


    When I was making career choices, I didn’t know anyone in my social circle who had attended university and I aspired to independent adulthood, earning my own keep etc. asap



    I'd go one step further from this point. Every so often I like asking people how they got into engineering, and over 90% of the time it seems to be partly from at least one parent being an engineer / technician. I may get a bit controversial here, and I'm happy to admit to having no hard evidence so can easily be shot down, but I have a very strong impression that a large percentage of us who are (or have recently been) leaders in UK engineering will have been influenced - perhaps more strongly than we like to admit - by our parent's (or at least our parents generation's) attitude to engineering. Which in the UK from the 1930s to 1960s was very heavily, and necessarily, based on practical problem solving. As I mentioned, in my career I've seen modelling absolutely revolutionise engineering design work - which is brilliant, but is a culture shock to the profession. And I think we should feel happy to admit that - as AA would say the first step is to admit you have a problem. ("Hi, my name's Andy, and I'm a traditional engineer. In the last week I used 15 op-amps a day.")


    Operations and maintenance of high value intensively used assets requires a “bias for action”, much of the time that we might call “practical”.

    Perhaps research development and fundamental design begin with a “bias for analysis” first which we might call “intellectual”.

    Within the “Engineering Council family” an analytical or conceptual approach is considered to be “of an intellectually higher order” or “academic”. It is therefore held in higher esteem, than a “more practical” or “vocational” approach.

     



     And vice versa for those working in operational areas who can - and often do - hold a practical approach in higher esteem. So this leads to a interesting thought (which I think emerges from a few of the above posts): is it really a lack of "practical" skills that is causing other engineers (and employers) a problem, or is it sometimes really a lack of that "bias for action"? As I mentioned above, I started my career in roles where you had to problem solve immediately to keep the system going, and then sort out the underlying problems afterwards, and this was fantastically useful when I moved into R&D as I could speak to customers, applications engineers and manufacturing staff in their own language - I could feel their pain at having down time in their systems. And I think this chimes with the point about:


    What many employers are really complaining about is the graduate lacking sufficient usable skills to make a productive contribution quickly.



    If new entrants - graduates or not - have a "bias for action" and a suitably thorough approach they are likely to find solutions to problems, including identifying people who have the practical and theoretical skills to support solving the problem. (By the way, this is why I like UKSpec, because it does - to me - identify this approach.) So yes, I think it is a challenge for the industry to find ways of developing those skills, and there is a particular problem that academic education, for perfectly good practical purposes, actively eliminates team problem solving skills which are exactly what we need! If a student at his viva said "I got this student to write the software for me, this other one to build it, this other one to test it, this fourth one to do the presentation, and I kicked it off and kept it on track to meet the requirements to time and budget" they would fail. But my goodness would they be employable!



    My kicking off this thread didn't actually come from comments from engineering employers (although I have heard some express this view, so it could have done), but rather from other engineers. Particularly, I was at a gathering recently where I heard (from different people) both "the problem with graduates today is they have no practical skills" and "the problem with women engineers is that you train them up and then they just go and get pregnant" *. I think, whilst understanding why and how people have developed these opinions, it's important to bring these attitudes out from the water cooler and into the glare of daylight!


    Thanks again all, hopefully a useful thread to point to when this issue gets mentioned in passing in other future threads?


    Cheers,


    Andy


    * A whole other thread in this one of course...

  • I completely agree with the OP though would change the topic title slightly to "You don't necessarily need practical skills to be an engineer" because... it all depends: As the OP mentions, its about the collective skills within the team, how that team works together, and the team output. Practical skills are important for some teams for some of the time, but maybe not always and probably not in every team member as other non-practical skills are valuable and essential.


    In my work, I routinely facilitate new product development teams where the preparatory work includes team selection drawn from multiple disciplines - design, production, quality, purchasing, sales, marketing... you get the idea. A multidiscipline team is an essential element toward a successful outcome.

     

    Which leads me to feel that expressions of graduates (or anyone working in a technical discipline) lacking practical skills is more of a reflection of flawed recrutiment, or inadequate team building/selection and or management of that project or team.

  • Roy Bowdler:



    • The collective desire of Chartered Engineer representatives for status is reasonable and understandable. However, the great majority of them seem confident and successful in their careers, with little need to obsess about relative status.


    Roy,

    Well said, I fully agree with your comments. I view my CEng as an indication that I do a good job in a professional manner, no more. It is certainly not a status symbol and I hardly ever refer to it. Going back to the title of this thread, I would agree that you don't need practical skills to be an engineer but also that you don't need theoretical skills to be an engineer. However most engineering projects need both (though not necessarily held by the same person). The person with the practical skills is often as important as the person with the theoretical skills. It the person with the practical skills only were to be awarded CEng on the basis of doing his/her job well and in a professional manner, that would be fine by me.

    I consider that I have practical skills but not using them on a day by day basis means they are not as practiced as the people who normally do the work. Those people should also get recognition, and if it is decreed by ECUK that the recognition is to be called EngTech I will value it as the judgement of their peers that they do good professional work (and similarly for IEng).

    I could in fact go further and say that with the relative numbers of EngTec and IEng to CEng, CEng as the most numerous might be seen as of the least value, but that might stir the pot too much.....

    Alasdair
  • At the risk of “over sharing”, I thought that I would tell my story of leaving school at the age of 16 to pursue an engineering career. It may not be “typical” but something similar was the common experience of many entering engineering until the 1990s.      

     

    The first year of my CEGB Apprenticeship was spent at college where practical work in mechanical fitting, using machine tools, fabrication and welding, some wiring and instrumentation.  There were two academic streams with some just doing C&G “Basic Engineering Craft Studies” and some in addition doing the G* (Technicians) course. After this you chose to specialise in Mechanical (“the wooden tops”) , Electrical (“the cream”) or Instrumentation (***** potential homophobic abuse). The second year was a 3 month block ( C&G Electrical Technicians course for me) followed by 6 months at the “Plant Training Centre”. This “company college” was superb and by the time you left you knew “inside out” much of the equipment that you would encounter in a modern (nearly new) Power Station, The Head of Department (an HNC CEng) and his deputy, had frequent short sessions on the relevant theory in context for those who were interested. The only thing I didn’t already know when I did a part-time ONC the following year was calculus (apparently so beloved of CEngs). Studying on day release for a Higher Education Qualification (HNC) was less rewarding. However because there were few takers for the heavy current option, I got a lot of electronics which interested me the time, including as a hobbyist with projects from ETI & Practical Electronics magazines etc. This was probably the closest I got to computing, as the 8080A was out. I suppose the nature of my job offered little opportunity to apply mathematical theory rather than just use relevant formulae. Also the lack of time in one day, didn’t allow you to develop valuable “academic attributes” around research and communication skills. For many on the course “General Studies” was just a nuisance subject.  

     

    Having completed my Apprenticeship and HNC, I transferred to High Voltage Substation Maintenance (132-400KV). I  joined IEEIE and negotiated an arrangement where I could swap my hours around to continue in part time-education. I initially hoped to do a part-time Electrical Engineering Degree but there was only one offered within 2 hours, when I inquired I was advised that “because the mathematics content of my HNC wasn’t strong enough there was no advance standing” and the course would be 5 years one-day and an evening. I requested the syllabus and went through it. I couldn’t honestly see how it would benefit me, since it just seemed to be what I already knew “with mathematical bells on” and of little relevance to my work.  An older colleague was pursuing CEI/Engineering Council Exams, which seemed similar but without any teaching.  I chose instead to do a two year course at my local Polytechnic for The Institution of Industrial Managers (formerly The Institute of Works Managers and now CMI). This was worthwhile with significant maths in Accounts, Economics and  Operational Research (statistics). I was assured that an additional “diploma” year would guarantee MBA admission, but I needed a pause in studying to pursue other interests.

     

    I won’t bore you with the rest on my career story, but I became IEng at 27, Chartered in the HR domain (via an MSc), A short-term cover HSE manager (IIRSM Diploma), eventually also that MBA with the OU.  I realised that I had kissed goodbye to the possibility of Chartered Engineer when I didn’t do the Engineering Degree, but my IEng and membership of an Institution of “Executive Engineers” seemed just fine.  Taking a UK-SPEC perspective, I only ever did a modest amount of engineering design, often “on the fly” and never needed any more maths than I had, except to decode the occasional text book.  

     

    Relevant reflections - some for debate

     
    • My early education emphasised knowledge of facts rather than analysis or the presentation of ideas/concepts

    • When I was making career choices, I didn’t know anyone in my social circle who had attended university and I aspired to independent adulthood, earning my own keep etc. asap.  I didn’t know any entrepreneurs either, although a good friend had a successful painting and decorating business by the time he was 20 and another went straight into the family haulage firm. 

    • My practical craft (or hand) skills were mediocre at best, but I was good at more technical work like fault-finding, which required practically applied “cleverness”  

    • I was lucky to find a reasonably successful pathway with no route-map to guide me, but as everyone knows the definition of luck is “opportunity meeting preparedness”, I actually had to battle for opportunity and worked hard to be prepared.

    • I bought my first home at 21 and was head of a small department at 27, I eventually topped out one step short of Director, which I’m sure some would consider “over-promoted”. wink


     

    • Operations and maintenance of high value intensively used assets requires a “bias for action”, much of the time that we might call “practical”.

    • Perhaps research development and fundamental design begin with a “bias for analysis” first which we might call “intellectual”.

    • Within the “Engineering Council family” an analytical or conceptual approach is considered to be “of an intellectually higher order” or “academic”. It is therefore held in higher esteem, than a “more practical” or “vocational” approach.

    • Every minuscule division between every “type” of engineering practitioner usually matters to someone, whether it is part of their self-identity, sense of self-worth, immediate and wider peer group etc.  Starting from that point, a social science frame of reference is often more relevant than a technical one in explaining the difference.

    • We are often very specialised experts until that specialism isn’t needed any more, when our answer quickly becomes “I’m sure I can get my head round that”.  Demarcation was heavily defended by Trades Unions at one time.  Engineering Council Institutions must explicitly not be Trades Unions , but some of the same human needs are being satisfied.  Mutual solidarity can easily be mobilised by any common threat or enemy.

    • Engineering Council’s attempt to “modernise” into the 21st Century by describing its registrants as being “different but equally valuable” was taken as a threat to their status by some CEng who mobilised to squash the concept. Other perceived “threats” treated similarly have included  blocking suitably qualified engineers from Eur Ing and objections to other Chartered designations.

    • The collective desire of Chartered Engineer representatives for status is reasonable and understandable. However, the great majority of them seem confident and successful in their careers, with little need to obsess about relative status. Perhaps all we are seeing is a variation on Car Club members whingeing about Caravaners etc.?  No doubt if handed they were handed reins of power Caravans would be banned on many roads during the day.

    • As far as I can tell without a serious research study the “status” of engineers has not advanced by a (metaphorical) millimetre in my lifetime and may have reduced, despite the academic inflation that has taken place. Perhaps a few who in move in certain social circles are more accepted? It is difficult to compare performance across different eras, Footballers being an obvious example, but given that in Engineering we are all standing on our predecessors shoulders, there isn’t a clear performance improvement either ,is there?