Stop trying to troll PeterPoddy

Sorry, it’s too easy. Plus I’m right and they know it. The sooner they accept that, the better I think you’ll find. 🙂

TTFN
Got a 1.5+ hr drive home now, I’ve been educating you lot when I could have been on my way home! 🙂

Sorry, it’s too easy. Plus I’m right and they know it. The sooner they accept that, the better I think you’ll find.

I’m on “their” side 😛

So he would be a ‘software mechanic’ then?

Dunno, maybe.

Sorry, it’s too easy

It would be if it wasn’t so transparent. You’re clearly not a Trolling Engineer 🙂

My last job title was Sales Engineer. How does that work then?

My last job title was Sales Engineer. How does that work then?

When you sell your soul to “sales”, Satan can call you what he likes!! 😉

Depends how much scheming and manipulation you had to do 🙂

My last job title was Sales Engineer. How does that work then?

Simple that one

You sell the customer what they want regardless of whether it’s possible or even exists.

You sell the customer what they want regardless of whether it’s possible or even exists

Jebus, that’s so true….. 😆

😆

Here’s a genuine question to Pete.

If you take the example of a Typhoon fighter jet. The design of the jet is aerodynamically unstable whereby a pilot would not be able to control the plane with conventional hydraulically actuated controls.

It needs alot of software code to keep the thing in the air, so the machine has lots of carefully designed moving parts working in conjunction with lots of carefully designed software. Both of which were not designed and built in isolation of one another. They are were both designed in conjunction, so the software code becomes a component of the machine.

So the question is where does the “real engineering” start and end for such a machine?

I’d say that an engineer is someone who applies engineering principles to a technical problem. You work out what’s required, design a solution, inplement the solution and test it. That can be done for a variety of technical problems, yes, including software ones.

Plus as jimmers points out, in many areas the dividing line between fields is so blurry. Why are the people who designed the electronics for a smart phone be engineers while the softies who designed its firmware are not?

I would expect a Aero or Civil engineer to be able to rock up at my desk and we’d be, conceptually, talking the same language

That’s because you’re from the same branch of engineering.

the skill-set for engineering engines and bridges is broadly similar. Designing, optimising and implimenting software is a broadly different skillset – as, perhaps, a crass example, if I asked you to predict the fatigue life of an engine component, would your technical qualifications allow you to do that?

Having done a general engineering degree I’d have a good go. The question is, could you design a transmission line, a computer chip or an antenna? Or do you consider electrical, electronic and communication engineering also “not engineering”? Maybe you’re just a bit of a specialist in the same way a software engineer is.

Yeah.. it’s all about designing and making things that work, and do things or hold things up. Solving technical problems in a rigorous way.

Having done a general engineering degree I’d have a good go. The question is, could you design a transmission line, a computer chip or an antenna? Or do you consider electrical, electronic and communication engineering also “not engineering”? Maybe you’re just a bit of a specialist in the same way a software engineer is.

Two questions there – have been part of teams engineering RF and microwave antennas and, large very high voltage electrical equipment (think electric ship projects etc). The electrical theory is beyond me, but all I need is the input to do the electrical/mechanical interaction calcs. Electrical/electronic engineering is still part of most engineering degrees, so – at the interface – we still had the common language.

The other part – for the unis that I have input on – applications for electrical/electrionic/comms engineering arerapidly dwindling, so beyonds course units in either comp science or the other engineering subjects it could, unfortunately, be a nul-question soon 🙁

The wikipedia blurb makes sense to me, as a non-engineer:

‘An engineer is a professional practitioner of engineering, concerned with applying scientific knowledge, mathematics and ingenuity to develop solutions for technical problems. Engineers design materials, structures, machines and systems while considering the limitations imposed by practicality, safety and cost.[1][2] The word engineer is derived from the Latin root ingenium, meaning “cleverness”.[3]

Engineers are grounded in applied sciences, and their work in research and development is distinct from the basic research focus of scientists.[2] The work of engineers forms the link between scientific discoveries and the applications that meet the needs of society.[1]’

Non-comparision – you didn’t engineer the cambelt, you followed the instructions on how to do it. Likewise, I blindly follow the help manual like any fool when knocking up bits of code.

Which explains why you’re not a software engineer!

That approach stops working when you’re working on bigger more complex systems – in much the same way that bridge building by putting a bigger plank across a stream stops working somewhere before you scale it to take trains over the Forth…

On the original point, I wonder if SAS would consider somebody with an HND in computer science who started off as a computer programmer not to be an engineer, and what his distinction is?

as an engineer myself-I can only add that Helen is fit.

The electrical theory is beyond me

So your answer to that question is no – by your original criteria that makes you as much of a non-engineer as those you’re accusing. I’m probably the only real engineer on here by that definition – yet strangely my latest job title was “software engineer”.

Let’s dig into this a little more – would you consider somebody designing the test protocols to ensure the components you design perform how they’re supposed to an engineer? Somebody in charge of taking the parts you design and manufacturing them an engineer?

10^2

yay!

[video]http://www.youtube.com/watch?v=xAGT0GXERT4[/video]

Bill Hewlett and Dave Packard.

Both electrical engineers. Built a multi-billion dollar company up from just the two of them in a garage. Hugely savvy business men, with an innovative management style decades ahead of anyone else.

Making software is not engineering, and certainly not science.

As the conceptualisation of an abstract form that reflects reality, its clearly an ART.

I am a software artist

Real Engineering here: http://cgi.ebay.co.uk/Custom-made-BMX-/190545729426?pt=UK_Bikes_GL&hash=item2c5d691792

Real engineers drive at least 20 year old Landrovers. Software engineers drive Mondeo’s.

End of.

You’re all shit , we should have been on mars by now you lazy ****. Get back to work!

Can an engineer make a good businessman?

Engineers tend to be ‘thinkers’ (Check out NLP)

Thinkers weigh up the risks involved with starting a business, throwing their house/ relationships/ money into a ‘hair-brained’ scheme and most will turn away from that, preferring a little more security.

Entreprenuers, on the other hand may be ‘entertainers’ ignoring the risks and not caring about the facts in order to make their idea a reality. If the idea works, they become successful businessmen, and even if they dont they will likely try again.

I tend to agree with the Sugar.

And also Peter Poddy.
Engineers make stuff you can touch.
Software designers copy and paste.

bristolbiker – Member

Yeah, but you are applying the principals of strucural analysis/solid mechanics/materials science/thermodynamics/fluid dynamics/etc that are the key features of any engineering degree, using software as a means to an end – software engineering is something different, and of it’s own right, that has (unfortunately, IMO) adopted ‘engineering’ as part of the description.

Engineering is about abstraction, and if you don’t understand that then you’re not engineering.

Electrical/electronic engineering is still part of most engineering degrees, so -at the interface -we still had the common language[ /quote].

So is programming. If I met with a bunch of people I was writing firmware for, and they were hardware engineer types, they probably wouldn’t be able to do the actual firmware, but we’d have a common language relating to where our bits stuck together.

So
a)most engineers are like you, specialists, who can work well on one particular area, and can also keep up enough understanding to interface with areas where they need to. So are programmers.
b) the functionality of many products is 90% defined by software nowadays eg. Take the original ipod – nice shiny design, not very much innovative engineering, very elegant software, 90% about software, 10% product design, then hardware ‘engineers’ stuck some commodity components in a box. The big reason Apple consumer products are so popular is because they didn’t have the idiot engineer / software divide, whereas if you look at a lot of stuff, it isdesigned first by ‘proper engineers’ with the software fitted into what the engineers build (a lot of old Sony stuff really suffered from this, and I’ve seen this in action in some other big companies with a rigid hardware/software divide ).

Given that so much ‘hardware engineering’ is really just sticking a processor in a box, it’s futile to argue that there’s any real difference any more.

You’re all missing the point. Software Engineers are all geeks. And soft.

I don’t care what they call me as long as they pay my rate 🙂

I would say some some software is written by engineers using engineering principles and some is not.

A control control system lid a PID controller could need an understanding of 2nd order differential equations much like would be needed to control something in a mechanical way. The analysis would be pretty much the same as if you were to solve the problem mechanically with a mass, spring and damper solution. I think this would most definitely be an engineering exercise.

Engineering is about abstraction, and if you don’t understand that then you’re not engineering.

I think I’d like to add to / edit that.

Engineering is about abstraction, and if you don’t understand that and the consequence of that then you’re not Engineering, you’re following a recipe.

I’d like to edit that too 🙂
Engineering is not about abstraction, but about the utilisation of it.
Mathematics is about abstraction.

Engineering is not exclusively design based.
That’s just a claim spouted by prima donna designers to make themselves feel special.
Just check the dictionary.

Software designers copy and paste

Yeah, but WHAT do we copy and paste? 🙂

That’s like saying engineers cut metal and pour concrete.

Engineering is not about abstraction, but about the utilisation of it

To be a good Engineer you still have to understand and know the limits of the abstraction you are using.

Software designers copy and paste reuse existing good solutions.

FTFY

I presume when engineers design an engine or a bridge they start from scratch every time?

Alan sugars a first class knobber anyway, couldn’t give a stuff about what he thinks. Apprentice is all bollox anyway, done for good viewing – this weeks task being a prime example. No way in the world they could come up with an idea, run it past a focus group which happened to be ready, settle on an idea, develop it, design it, get it artworked, proofed and copies printed in the allocated time slot, especially given that none of them have particular expertise. It’s amusing to watch though 🙂

Amstrad – nuff said

I have a degree in Engineering Systems
I’m Chartered
I have specified, designed, coded and tested may software systems that operate radar, radios and spacecraft worth millions.

Don’t tell me I’m not an Engineer.

But Sugar may be on something 😉

Technician – follows instructions to get something fixed… like a car repair manual, or guide on how to install some software.

Engineer – has the ability to think creatively when the above doesn’t work. i.e. milling a part to fix the car, or hacking the registry to enable the software installation. The engineer actually designs a solution for the problem.

ould you please tell that ot our HR department? Our engineers seem to think they’re clever when all they can do is order and specify new equipment whereas a lowly tech I can make vintage equipment work in the freezing cold in the dead of night with just a hammer and some PTFE tape*

As regards the OP – that’ll be why Amstrad’s products are so diabolically ropey and have such a dreadful reputation then?

(*PTFE which the Engineers allowed the safety people to ban.)