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.
Your first new year celebration in the Netherlands?
Yes. But I am used to fireworks so noise was not a problem. Smoke on the other hand was a big problem. I felt the amount of smoke generated by fireworks here was way more than those in India. I could not see the house across our street. It was fun to see unhinged calendar independent people around.
Other than that, it was fun. Next year, I plan to do big fireworks myself (this year we only got little ones to not scare our little one) but I really need to find those which produce less smoke.
We have had a couple of incidents were people have entered our facilities with dubious intentions. So at all the card lock doors, signs were put up: "No tailgating" (as if that would make those spies say: Oh well, then we'll have to try to break into another hi-tech company).
It struck me that since we make chips, at least a third of our employees are hardware experts, shouldn't the sign display a NAND gate symbol?
Ah. I had no idea what that expression meant, as for here in the US, it's referred to driving too close behind another person or, at a football game, a tailgate party. Never heard it applied to people before.
The way I understood it is GKP1992 was referring to the OP's statement that when a spy sees the sign they'll leave. GKP1992 is pointing out that the sign isn't to deter the spy but rather so that the employees do not allow people to follow them in.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
Of course. But we have been joking a lot about these signs, like when we come a group of six people from the canteen and one unlocks the door and the guy behind tries to follow, he may be grabbed from behind: No no! with finger pointing at the "No tailgating" sign: You have to wait until the door has closed and locked up, then you can present your keycard and type your code!
We have had discussions about what to call it when someone comes from the other side, opens the door, and you slip through the other way before the door closes. Are you then headgating? Are you both headgating, or only you who didn't use your card?
With something like 400 people in the building, you do not know every face. If you see them wearing some name tag, you trust them, if they behave "normally". And there are people who do not work here, but nevertheless has a card: The fruit basket delivery guys, the newspaper boy, craftsmen doing e.g. electrical or plumbing work and several others (they obviously have restricted cards that won't let them into the high security areas). If someone behaves if they belong here, and carry a card that accidentally has been turned backside-out, they will not be stopped at the main entrance - "No tailgating" signs or not. So for all practical purposes, the signs are a joke in themselves. We catch people far more easily from their behaviour inside the building. Also, we know the people working in this floor, this wing. An unknown face amidst all the familiar colleagues is easy to spot. But not at the main entrance.
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.