This discussion is locked.
You cannot post a reply to this discussion. If you have a question start a new discussion

STEM Education - should it focus on technology itself, or on using technology to solve problems?

Just been listening to Eben Upton discussing how he came up with Raspberry Pi (good programme, worth a listen):

www.bbc.co.uk/.../b09ly60f


Took me back to my university years ('79-'82) when many of my cohort were playing with Sinclair micros etc, and I was thinking about why it never appealed to me. I think it's because while I do, obviously, find the development of new technology fascinating, what interests me is its ability to solve problems - whereas many of my colleagues were interested in the pure challenge of getting these piles of vaguely connected circuit boards to just work!


Now, I believe it's a Good Thing that there are young people who are fascinated with technology for its own sake, this is how the Microsofts and Apples of this world developed. But I do wonder if we focus enough in STEM education on the ability of technology to solve problems, and develop an interest in its possibilities from that direction? Two reasons:
  1. I suggest it will attract more people into the fold, and increase the general understanding of the value (actual and potential) of technology,

  • A good development and implementation team needs a wide range of skills (c.f. Belbin team roles), I suggest this approach would help us flesh out these teams with people who are able to form the link between the potential of technology and the needs of society (or the customer depending on your focus smiley).


(Also, it is often suggested that there is a sex bias here: boys tending to be more interested in just building things (and blowing them up!), girls tending to be more interested in why they're doing it. Personally I think this is, if anything, a gender issue rather than a sex issue and hence is terribly complicated - possibly best just to accept that different approaches appeal to different people?)


What are people's experience here? Do you think we explain enough what technology is for, and inspire young people to use it solve problems? Or - if we do we get too carried away with bells and whistles - is that maybe the right approach at a young age? Any good stories?


I'm very happy to admit that my big inspiration (in hindsight) was watching Thunderbirds as a very young child! I still have a little Thunderbird 2 on my desk to inspire me. Oh, and don't worry, I will still (much to the amusement of my family) sit with a huge smile on my face looking at a very elegent piece of engineering for its own sake. But it's got to be really elegent!


Cheers,


Andy


  • Former Community Member
    0 Former Community Member
    Hiya,


    Lovely topic!  I work with loads of STEM Ambassadors and have been one myself for years.  Prior to what I do now, I was an analyst, but I don't consider myself to be a computer/tech person - that said, I love making things.


    What we're seeing with technology seems to be similar for a lot of the conversation around maths - people don't like to say "I do maths" either - but for most engineers we will use various aspects of technology, computing and mathematics.


    I think that we should be talking about both aspects of technology - the "this is cool and look what it does" and "this is how I can various things because I know about it enough".
  • And this all ties in with the IET press release from last week:
    • Over two thirds (68%) of children hope to work in a ‘green job’, but 71% say a lack of knowledge about these careers could stop them from following their passion

    https://www.theiet.org/media/press-releases/press-releases-2020/18-september-2020-generation-green-ambitions-at-risk-of-going-to-waste/


    So for example, explaining how modern engineering is providing solutions to combat climate change and pollution seems like a good thing. And, on the other hot topic, how engineering is helping to find solutions to Covid-19. 


    On the latter point, I was giving a STEM presentation a few years ago, and yer typical 14/15 year old lad decided to show off to his friends by shouting out "yeah, but engineering doesn't save lives, does it?" Wrong time to say that, my wife was going through intensive cancer treatment at the time (all fine now), so I spoke at some length about radiotherapy equipment, MRI scanners, chemotherapy delivery equipment, chemical engineering of drugs (which all too often we forget about)...might not have been my most polished presentation but I think got the point across! I now usually put an abbreviated version of that in my presentations. 


    It creeps into the day job as well, with a slightly different angle - I assess clients' engineering processes,  and very often after they've spent ages describing the very clever engineering they've done I find myself repeatedly saying "but what is the actual problem you are trying to solve?" Because without that it's impossible to assess whether they've solved it. So building in that thought process from day "minus one" - while the prospective engineer is still at school - must be a good thing!


    Cheers,


    Andy

  • Good reminder about why we do what we do. Whilst some people “do” science or engineering for its own sake, the IET Mission and Vision make it clear that we are “working (together) to engineer a better world”. I thought that that philosophical approach is what drives STEM Ambassadors to enthuse youngsters, their teachers and their parents.
  • I have a slightly different view. Much of my career was spent trying to invent new items, particularly for Broadcast Television. I helped to invent the concept of electronic graphic systems, where there is only a simulation of working for the artist, on a vast array of numbers. At the time of inception, we also decided we needed a pressure-sensitive pen (brush, knife, airbrush, etc, whatever tool the artist was using) in order to simulate real artwork. A good deal of this needed to be carried out in hardware as computers at the time were pretty slow, and doing complex maths on millions of pixels per second was well beyond them. In fact, it was way beyond mainframes too, I know because I tried.


    The idea that one can invent technological solutions without understanding the limits of technology, somewhere suggested above, is in my view not possible. Take another piece of equipment which gradually became essential, the digital video tape recorder. At the time mainframe disks were a few megabytes, and datarates were pretty small. Digital video required continuous 270 megabits per second for 8-bit data. One required to be able to electronically edit the tape, sound and picture separately, in real-time. The tape consumption had to be as small as possible, and the system completely error free. Anyone could desire a digital tape recorder, but implementation was down to very few people, at Sony because they had the micro-mechanical skills required. Very few companies have attempted this project since.


    I will also mention the concepts required to design integrated circuits. Can the students possibly come up with something like a mobile phone, without having any idea how to make it? I think not. A mobile phone would have been useful in 1939 as a wartime communications aid. It could be envisaged, but the result was the 19 set. It was not a telephone and was portable by two big strong men. The principle was similar to a mobile phone, a multi-band transceiver, but the implementation had to use the technology available, which was valves. I was the System Architect for an IC product by a British semiconductor company. It was to make a SOC video camera, player recorder etc. The available market looked good, there was nothing like it available. The brief required a very good idea of the technology available, the operation of television systems, storage, compression, and also the consumer angle of what a consumer might want. Could your students even approach the ideas required. I think the answer is no.


    Overall I think the IET and others are doing exactly the wrong thing in the way they are trying to sell Engineering to students. To be good at Engineering requires a special kind of mind, which wants to know WHY all the time. If you want an easy career, go and be a doctor, a lawyer or something similar. The "why" is largely sorted out, you just do what you know to try to fix people. The nearest equivalent to a real Engineer is a research Scientist who designs new drugs. The way to get an interest in Engineering is to start by trying to fix things, preferably at a very young age. You will fail many times, but sometimes you will succeed. When you start to succeed more than you fail it well be time to learn how to design things. Back to square one, your designs will fail, but you will learn. Then you learn how to design better, the mathematics, the underlying technology will permeate the brain. Then you can think of new ideas, and they will be possible for you to make. 99% of people think it is all too difficult, needs too much effort, and the pay is poor. That is what you need to fight to be a real Engineer (Like Brunel who suffered all those things).