The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
If you don't recognize ( god awful american spell checker ) the symbols for resistors and capacitors you are not worth your salt. Stay far away from anythings electronics, it will only cause grief and pain.
Well... OriginalGriff said 'engineer', not 'electronics engineer'.
In many countries, such as Norway, programming is considered an engineering discipline. My education is so old that I learned the symbols for both basic components and logic gates, but I am am far from sure that today's students learn them, though. In my professional work, I have never been close to know them or refer to them.
I do program hardware directly (so I stay close to the electronics), but I see the hardware as logical functions, not as components. I do not even use or refer to logical gates, but relate to registers, interrupt signals, hardware timers...
Those guys designing the chips obviously know component symbols, but the great majority of their design work is done at the level of logical gates (or even above that). I am quite sure that half of them couldn't read the size of a capacitor from the color bands without looking up the values in a table; they certainly know that the table exists, but it is far away from their daily life even if they do electronics design.
I would say that if you don't know the symbols for resistors and capacitors, stay away from electronics circuit design. You can still make a career even in, say, microcoding a CPU, which I would consider quite close to the electronics. Of course I would be surprised if I ever met someone doing microcoding but didn't know capacitor/resistor symbols, but that is not because they need it to do microcoding. Even microcoding doesn't relate to capacitors.
Rather, I just have to force myself to tolerate that people with a degree in programming says "Huh? What's that?" when you refer to the static link in the stack frame. That the only understanding they have of finite state machines is as a documentary tool of blobs and arrows. Even backtracking is a vague term for too many software developers ... All sorts of really basic software concepts.
It is not that they are not going down to that low level, but that the education has focused on a very narrow selection of solution methods. Like in networking: You could spend a lot of effort on explaining that you do not have to carry 32 bits of source and destination addresses in every single network package, that is just a choice made in the IP protocol. (I have been through that explanation a few times.) Or: You do not have to put the "if" condititon in parentheses; that is just because those who "designed" the C language weren't really language designers, and didn't know how to make the languge unambiguous without the parentheses. And so on. Lots of software developers seem to believe that C style syntax and the IP protocol and eight other commmandments were what Moses brought down from the mountain.
If you attend some on-job training course to obtain a certification that you master this and that tool or mehtodology, I don't expect you to know other tools or methodologies. But if you present a Master's Degree, I am equally disappointed whether the only thing you know is the gcc suite and open source tools, or what you know is nothing but the Visual Studio ecosystem. If all you get out of a university education is a detail knowledge of every single call line option to the gcc C++ compiler, then you have wasted a lot of time on that education. Too often I think that is the case. I think that is much worse than not knowing what a capacitor symbol looks like.
My degree in software is a few years old. In my days at the Tech U, even though were were not learning to be masters of digital logic, we certainly had an introduction to it, so that we would know how a flip-flop, a memory cell and that kind of things works. We even did microcoding on a 2903 evaluation board, routing signals to the various control lines to read two 4-bit switch banks into the registers, add them and display results on 4 LEDs plus a carry LED ...
So in my old University textbooks, I can find the full collection of gate symbols. It may be different today, though.
We've got a similar policy here but everyone from this area is too polite to actually confront someone who tries to follow behind them without an ID. Makes security a nightmare.
I've only done so myself once and that was about 30 minutes before the building was open for business. We've got a decent amount of homeless around where I work and some guy was standing near-ish to the front door. When I stepped through he tried to quickly follow without me noticing. Come on. It is still dark out, you were trying to not draw attention when I walked up, and tried to sneak in behind me? Even without coffee I'm going to notice you!
So I spun around and confronted him asked to see his ID. Didn't have one however assured me that he worked in the building. So I asked some pretty general questions, who he worked with, what team, etc., and he couldn't answer any of them. After that I threatened to call the police if he didn't leave, etc. etc. and he kept saying he worked there but no other details.
Long story short, it was his second day there, hadn't been issued his ID badge yet, forgot his temp ID at home, didn't want to be late by going back to get it. If he had simply said "It is my second day and I forgot my ID." I would have handled the entire situation differently, but no... he chose to say "I don't have an ID". Also explained why he didn't know anything about who he reported to, what floor his desk was on, or anything else.
Actually, I didn't look that far down - thanks for pointing it out.
Nor did I notice that this web page claims that it is Hell, Michigan. It is not, it is Hell, Norway.
(For those who have gone by air to Værnes Airport, Hell is the village next to it.)
The style of the sign is distincly Norwegian, European, rather than American.
I drive past it regularly; it certainly has been frozen over this way quite a few times.
The Norwegian name Hell has no relationship to Helvete, but comes from "helle" or "heller".
A "helle" is a flat stone, like a slab of slate, or any stone that is "flat", or even a flat surface on a large stone that is not so flat.
A "heller" is a stone that sticks out from a mountain so that it serves as a shield against rain and snow. In the stone age (and even hunters in more modern times) could make a dwelling under a "heller". This is probably the origin of the name of the place, being much older than Christianity and its hell, certainly in Norway, but the name may be as old as Christianity itself.
For the place outside Bergen, called Paradis, there is no similar old explanation; that is a Christian name. Unfortunately, the train stop at Paradis was closed down several years ago, so you no longer can buy a train ticket from Paradis to Hell, or from Hell to Paradis. I suspect that quite a few of those tickets were never used.
Hell - Gods-Expedition[^] uses a 100+ year old spelling for "cargo handling" ("gods", cargo, is unchanged, but today we write "ekspedisjon"), but everybody loves the old sign, so they will probably keep it for another hundred years...