| General > General Technical Chat |
| Why do "programmers" call themselves... "engineers"?! |
| << < (4/45) > >> |
| magic:
It wasn't always like that. "Software engineering" was a movement which intended to apply methods of engineering to software (design, specification, QA, validation, testing) in order to hopefully ::) make software more reliable, designable and predictable. Originally it was associated with people sitting, drawing "blueprints" of software and trying to get programmers to follow them. Then the name kinda leaked into the mainstream and today every code monkey who copy-pastes together JavaScript snippets found on Stack Overflow calls himself a software engineer. --- Quote from: blueskull on November 16, 2019, 07:50:45 am ---Oh, and he is the "EE" in our team whom my boss intends to train to replace me after my upcoming leaving for China. --- End quote --- :-DD |
| tggzzz:
--- Quote from: eti on November 16, 2019, 05:21:09 am ---If a programmer can call themselves an "engineer" through manipulation of text and digits, then I, as an engineer, get to claim my title as "programmer" since I can set the temp on my soldering station, and type WhatsApp messages. :p --- End quote --- Please define where hardware stops and software begins. Without that your questions are built on not comprehending modern systems. You should include, but not be limited to, consideration of: * microcoded processors - is the microcode hardware or software * how intel can issue bugfixes to its x86 processors that are installed on motherboards in customers premises * whether a finite state machine specification (e.g. to control traffic lights) is hardware or software - or both or neither * is someone implementing a function in an FPGA a hardware or software engineer * is someone implementing a DSP function a hardware or software engineer * is someone implementing a mechatronic product a hardware or software engineer And that is without even mentioning fundamental theoretical concepts that dictate what the technology-du-jour can and cannot achieve. |
| magic:
Half of those "software engineers" don't even know what "a microcode" is. Stop splitting hair. Besides, tying engineering to hardware is silly. You can social engineer people and you can build hardware in complete violation of any accepted engineering practice. Is it engineering if I whack together a house from cardboard joined by shoestrings which is collapsed by the first wind because I have no idea what I am doing? ;D |
| iMo:
To become an "Engineer" of something does not guarantee she/it/he is a knowledgeable Expert for something. Engineering education "should" guarantee it/she/he is a person who was taught end examined by an authority about "latest and best" theories/methods/processes/tools/practices/ethics on how the good engineering in the particular field of interest should be delivered.. |
| tggzzz:
--- Quote from: magic on November 16, 2019, 09:11:00 am ---Half of those "software engineers" don't even know what "a microcode" is. Stop splitting hair. --- End quote --- If someone wants to try to make a distinction between hardware and software they have to split hairs! |
| Navigation |
| Message Index |
| Next page |
| Previous page |