News for hackers. Stuff that matters.
Re:Reviewing Bad Schematics as EE Interview Tactic by userbinator on Monday December 23, 2019 @04:32PM (#21867615)
My example of this: I have yet to meet a junior EE candidate who understands the need for decoupling capacitors in digital circuits

That says a lot about the state of education. I'm not even officially an EE, and only did some embedded hardware stuff and some electronics as a hobby, yet I know what that's about.

Re:Reviewing Bad Schematics as EE Interview Tactic by rightbyte on Monday December 23, 2019 @04:54PM (#21867783)
It seems strange that the author has not met a single one that understands that concept since it is quite basic. I am guessing he just is bad at interviewing and asks trick questions till he meet someone who know the interviewing game inside out.

Examples he gives:

"Current limiting resistors missing (BJTs, diodes, etc.)

Shorting a potentiometer node to a rail

Voltage regulators missing capacitors at input/output

Missing pull-up/pull-down resistors on digital buses

Missing decoupling capacitors"

I mean ... looking at a schematic how should you know that the voltage regulator doesn't have internal caps without seeing the specs? Missing pullups? How do you know those are not internal? It is stupid.

Re:Reviewing Bad Schematics as EE Interview Tactic by userbinator on Monday December 23, 2019 @05:03PM (#21867863)
how should you know that the voltage regulator doesn't have internal caps without seeing the specs?

Can you name one voltage regulator that has them? Maybe you've worked with a few, but just off the top of my head, the 78xx, 317, and 1117 don't, and neither do all the other miscellaneous ones that I've seen in consumer electronics.

Re:Reviewing Bad Schematics as EE Interview Tactic by rightbyte on Monday December 23, 2019 @05:29PM (#21868063)
Traco Power has some. I don't know which one we used on the top of my head but kinda like this with fewer pins: https://www.tracopower.com/products/browse-by-category/find/...

It's not my field and I had little clue what was happening at the EE level. Maybe you could argue they are not what is normally meant by saying voltage regulators.

Re:Reviewing Bad Schematics as EE Interview Tactic by ohazi on Monday December 23, 2019 @10:52PM (#21869700)
That's a module, not a chip. If it's one of those 1mm x 2mm sot packages, it almost certainly doesn't have embedded switching capacitors.
Re:Reviewing Bad Schematics as EE Interview Tactic by dogma1138 on Monday December 23, 2019 @09:35PM (#21869398)
Integrated Switched-Capacitor Voltage Regulators will definitely be a thing in a few years they have already been produced in research labs and quite likely reached even limited production for low power <10W applications.

In general I agree with the GP look at how many unpopulated areas exist on modern boards.

How should you know if the lack of input filtering is because of poor design vs the fact that the spec of the power supply changed and you no longer need it?

If it’s not universally true and obvious it’s not a good test.

Modern boards are super complex I’m not an EE but I would more likely flag lacking probe points, probe points which are too far or too close apart or too far from common ground as bad design choices than try to figure out if there are enough caps for the voltage regulator without knowing the full specs of the damn thing.

For all i know that voltage regulator isn’t even being used anymore because the IC or PSU specs have changed mid production but because it was wave soldered with a different soldering method than the other SMTs they already had them on a bunch of boards...

If you can’t reverse engineer the board or the relevant within a few min it shouldn’t be in an interview.

Not an EE but I do a lot of HW RE if anyone puts a modern multi layer doubled sided board on my lap and tells me to point out what’s wrong with it in an interview I would ask them what’s wrong with them.

Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @02:41AM (#21870554)
78xx/79xx don't need caps for stability either, according to their datasheets. Still seems a bit janky to leave them out.
Re:Reviewing Bad Schematics as EE Interview Tactic by SilasX on Monday December 23, 2019 @05:30PM (#21868074)
>It seems strange that the author has not met a single one that understands that concept since it is quite basic.

That's exactly what everyone says when candidates fail FizzBuzz.

The best explanation I know is that good candidates get hired quickly, so at any given moment, the candidate pool is dominated by people who keep failing questions like this.

Re:Reviewing Bad Schematics as EE Interview Tactic by TrackerFF on Monday December 23, 2019 @08:34PM (#21869138)
There are some variables at play.

- Stress-levels of the candidate - Tone / demeanor of interviewer - Communication prior to interview

I mean, sure, if you fail fizzbuzz interviews 10 times in a row, there seems to be some pattern going. But you could might as well fail it the first time, and get blackballed as incompetent.

Re:Reviewing Bad Schematics as EE Interview Tactic by rightbyte on Monday December 23, 2019 @05:44PM (#21868156)
He is saying that all juniors fail EE-FizzBuzz, which makes me question his interviewing skills.
Re:Reviewing Bad Schematics as EE Interview Tactic by SilasX on Monday December 23, 2019 @06:07PM (#21868305)
And a lot of interviewers report that all juniors fail FizzBuzz.
Re:Reviewing Bad Schematics as EE Interview Tactic by xvector on Monday December 23, 2019 @08:57PM (#21869235)
I just refuse to believe this. It can’t be.
Re:Reviewing Bad Schematics as EE Interview Tactic by klyrs on Monday December 23, 2019 @09:33PM (#21869389)
Lately, my company has been looking for folks who can, essentially, compute the sum of items in an array in JavaScript. Seniors continue to fail this.

It would be great if they'd stumble over conundrums like "what if there are non-numeric entries in the array." Most often, they just stare and don't even start on the problem.

Re:Reviewing Bad Schematics as EE Interview Tactic by xvector on Tuesday December 24, 2019 @09:08AM (#21872127)
Could you elaborate on the problem? No offense, I find it very hard to believe that no one knows how to sum the items in an array.

Are you expecting some map-reduce-like parallel sum, or something else?

Re:Reviewing Bad Schematics as EE Interview Tactic by klyrs on Wednesday December 25, 2019 @09:34PM (#21881718)
I can't really elaborate, but it's only barely more complicated than I'm representing. I'm with you. I can't believe it. Boggles my mind every time. And no we're not expecting a complicated solution.
Re:Reviewing Bad Schematics as EE Interview Tactic by SilasX on Monday December 23, 2019 @09:14PM (#21869300)
Join the club! Or rather, search for Fizzbuzz on HN and read the accounts and theories of similarly-baffled interviewers and posters.
Re:Reviewing Bad Schematics as EE Interview Tactic by Chris2048 on Tuesday December 24, 2019 @07:45AM (#21871650)
Perhaps they only interview roles below a certain salary threshhold?
Re:Reviewing Bad Schematics as EE Interview Tactic by crtlaltdel on Monday December 23, 2019 @05:13PM (#21867958)
I think it makes sense depending on the nature of the role in question.

If the role's primary function is to do validation prior to manufacture this seems like reasonable. it assumes that new circuits will have some number of fairly common mistakes. in my experience this is very true, despite the skill of the engineer who designed the circuit. missing termination, pullup/downs missing, etc. if the role is applications engineering...well...its far less likely you would be troubleshooting common circuit design issues so much as you would be troubleshooting common system design issues. im sure you can extend this to other functional roles an EE may take on. if the job is to design a MCC and size breakers to minimize arc flash hazards i doubt the applicant will be up on a correctly build half-bridge rectifier.

in that list quoted i've encountered all of it in new designs, including missing stuff plainly stated in the part's application notes (like those regulator caps).

Re:Reviewing Bad Schematics as EE Interview Tactic by jdsully on Monday December 23, 2019 @05:46PM (#21868166)
Decoupling capacitors need to be within a few mm of the integrated circuit consuming the power. It really doesn't matter if the voltage regulator has them or not.

This is different than for bulk capacitors, but even those should still be on the same PCB assembly because connectors have higher resistance and this will limit their ability to handle transient surges.

Re:Reviewing Bad Schematics as EE Interview Tactic by mbell on Tuesday December 24, 2019 @06:58AM (#21871420)
> It really doesn't matter if the voltage regulator has them or not.

Not all LDOs are stable without external output capacitance in a particular range / ESR.

Re:Reviewing Bad Schematics as EE Interview Tactic by jdsully on Tuesday December 24, 2019 @03:18PM (#21874622)
The point is the LDO's capacitance or lack there of has no bearing on whether decoupling capacitors are required.

Understanding that the capacitor and the trace form an RC circuit and that distance matters is what separates a professional from a beginner.

Re:Reviewing Bad Schematics as EE Interview Tactic by spatular on Monday December 23, 2019 @05:05PM (#21867880)
I've yet to see a voltage regulator IC with built-in caps. DC-DC modules sure, but author argues that this kind of info (module / ic) should be present in schematics. BTW, some linear regulators can't handle ceramic and low-ESR capacitors at output, and may be better with none if that's the choise.
Re:Reviewing Bad Schematics as EE Interview Tactic by rightbyte on Monday December 23, 2019 @05:33PM (#21868092)
I hate to maybe be proving his point by showing that I'm not into the EE field and thinking of a board mounted DCDC-converter as a voltage regulator (which it is but not what you usually call it in english?)

I would still argue that logic IC have alot of internal pull ups. Or that eg. "Reset sequence of digital component is wrong" is a bad whiteboard question.

Re:Reviewing Bad Schematics as EE Interview Tactic by spatular on Monday December 23, 2019 @05:46PM (#21868169)
I believe that without qualification "linear regulator" could be just anything that regulate voltage. Usually you can easily tell from schematics around it if it's some switching IC, an LDO or a module. And if you have layout or 3d render of the board it'd be almost certain.

Otherwise the person may just ask: "where are caps, or is this thing a module or what?"

Re:Reviewing Bad Schematics as EE Interview Tactic by msds on Monday December 23, 2019 @09:31PM (#21869376)
No, a linear voltage regulator is well understood as something with a transistor pass element in linear mode and a (probably dumb) control loop.

Definitely not a switcher or module, could be an LDO.

Re:Reviewing Bad Schematics as EE Interview Tactic by mkeeter on Monday December 23, 2019 @09:02PM (#21869250)
In my experience, "linear regulator" refers specifically to voltage regulators which drop from a high voltage to a lower voltage by burning all of the power in between (e.g. the venerable 7805).

They're useful if the voltage drop isn't too large and/or if you need a particularly stable output voltage; contrast them with switching regulators, which are more efficient but have some amount of output ripple.

One design that I worked on used a switching regulator to generate 5V, then linear regulators to generate something like 3.7V and 2.9V for various sensitive analog circuits.

Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @02:44AM (#21870561)
No, switchers aren't “linear.” And on a schematic the regulator isn't going to be a box labeled “regulator”! It will have a part number, probably a familiar one.
Re:Reviewing Bad Schematics as EE Interview Tactic by spatular on Tuesday December 24, 2019 @05:18AM (#21871033)
Sorry, I meant to write "voltage regulator" about which parent asked about, not sure how I ended up with "linear regulator".
Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @07:38AM (#21871607)
Yeah, a switching regulator is still a regulator.
Re:Reviewing Bad Schematics as EE Interview Tactic by sitkack on Monday December 23, 2019 @11:21PM (#21869847)
ICs with multiple power domains have a boot sequence that must be followed or the IC isn't in the proper state. Many interview questions fall into the "assumed assumptions" category. Simply saying, "lets reset to a known good state and modify one variable at time disqualifies many candidates". Because we don't teach science like we should. We should be teaching the scientific method before we teach the three Rs.
Re:Reviewing Bad Schematics as EE Interview Tactic by barbegal on Monday December 23, 2019 @04:57PM (#21867822)
It's not that stupid. If a candidate asks the questions you are asking then you know they are on the right track. It isn't about getting the right answers but about having the knowledge to ask the right questions.
Re:Reviewing Bad Schematics as EE Interview Tactic by wiredfool on Monday December 23, 2019 @05:12PM (#21867953)
I'm looking at that list and checking the mistakes I've made in electronics classes.

I think my best one was shorting a (slow) clock to power, which made the whole thing blink on and off.

Re:Reviewing Bad Schematics as EE Interview Tactic by PascLeRasc on Monday December 23, 2019 @10:51PM (#21869696)
My EE education didn’t cover decoupling caps, and from talking to others from different schools they didn’t learn it either. It's something that only comes out in DIY projects, and unfortunately most schools don't care about projects or fostering independent/continuous learning.
Re:Reviewing Bad Schematics as EE Interview Tactic by esmi on Tuesday December 24, 2019 @03:18AM (#21870686)
Are you an analog EE? If so that’s surprising. Did you have any microelectronics classes where you essentially build up your own opamp, one stage at a time? Bypassing is usually covered in this class, or in its lab, especially when discussing PSRR of the system.

Digital systems classes can cover it too, when going over power distribution, but that’s usually a graduate level class.

The digital VLSI or signal processing tracks of EE might not require this stuff anymore.

Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @02:46AM (#21870564)
It's in Horowitz & Hill. What was your introductory textbook?
Re:Reviewing Bad Schematics as EE Interview Tactic by PascLeRasc on Tuesday December 24, 2019 @09:55AM (#21872409)
Thomas/Rosa/Toussaint. Horowitz's book is way better though.
Re:Reviewing Bad Schematics as EE Interview Tactic by TheOtherHobbes on Tuesday December 24, 2019 @05:03AM (#21870992)
This astounds me. Trained as an EE in the early 80s. Can't imagine teaching digital design without mentioning decoupling.
Re:Reviewing Bad Schematics as EE Interview Tactic by Sanzig on Monday December 23, 2019 @05:17PM (#21867986)
I'm an EE. My first job out of university had a pretty good whiteboard interview (I know - we're not supposed to say good things about whiteboard interviews on HN). I thought the process was pretty straightforward. The first exchange went something like this:

Interviewer: "Can you draw me the schematic symbol for an LED?"

Me: Draws LED schematic symbol.

Interviewer: "What would you say the forward voltage is on that LED?"

Me: "That depends - maybe between 1 and 4 volts depending on the color?"

Interviewer: "Good, let's call it two volts. What would you say would be a reasonable current if we're just using it as a power indicator?"

Me: "I usually set it to around one milliamp on my boards."

Interviewer: "That sounds good. Can you show me how you would connect that to a 5 V supply?"

Me: Calculates ballast resistor size for 1 mA current from a 5 V supply with a 2 V LED drop, then draws a circuit with an LED, resistor, and 5 V source.

---

And on it went. We ramped up through complexity: next we did simple BJT and FET switches, then basic op-amp circuits including single-pole filters. I stumbled on a differential BJT amplifier question, but the interviewer helped me through it. And so on. I didn't nail everything, but I got most things right. I ended up getting the job.

When I asked the interviewer later about his experiences using test for hiring, he told me a sizeable chunk of new graduates flunked out on the first question, which I found pretty shocking. A lot of students with excellent resumes didn't even know how to hook up an LED!

As to the cause - it's just a guess, but I think many "good students" these days are very good at regurgitating information and memorizing procedures to complete formulaic exam problems, but aren't very good at actually developing the physical understanding of what's really going on. When I was in my senior year, I designed a buck converter as a small part of my capstone project. One of my team members remarked that he didn't realize a buck converter was a power supply, and that he had seen it in his power electronics class but had no idea what it was used for. He could do the duty cycle calculations for one all day long, but he didn't even realize it was a DC/DC power supply!

Universities these days do not seem to successfully evaluate deep understanding. Rather, they seem to optimize for the superficial appearance of understanding. Even "lab courses" when I was a student were formulaic: plug this wire in here, put your probe here, read this value here, do this calculation here for your report. There were very few courses that were actually designed to encourage real experimentation and practical learning. A good EE needs to develop a mental model of the underlying physics and be able to relate it to practice, and that is a tricky thing to teach in the classroom.

Anyway, all that said - I really like the idea of the "bad schematics" approach for an interview question. If I ever find myself in a hiring role, I am 100% using it.

Re:Reviewing Bad Schematics as EE Interview Tactic by artemonster on Monday December 23, 2019 @05:34PM (#21868095)
"Universities these days do not seem to successfully evaluate deep understanding" If you (as Uni) try and do that, you'd immediately find your quota of those who have finished a degree to plummet.

At our university we had basically only TWO courses that required you to "understand" to pass them and not just mindlessly puke out formulas and insert values. These were theoretical electrodynamics and integrated analog circuits. These were exactly the exams that kicked people out of university, since you had only 3 attempts to pass them.

So, no, uni's will never try to force understanding, since so few are actually capable of that. Unis teach you to know the basic set of symbols, be a mindless symbol manipulating monkey and hope that industry would pick you up and enlighten you afterwards.

Re:Reviewing Bad Schematics as EE Interview Tactic by JadeNB on Monday December 23, 2019 @07:50PM (#21868955)
> If you (as Uni) try and do that, you'd immediately find your quota of those who have finished a degree to plummet.

Indeed: as a teacher, I have had the experience that there's pressure to pass underachieving students in the elementary courses (we don't want to scare everyone off by flunking them out of their first courses!) and then there's pressure to pass underachieving students in the advanced courses (it's not fair to pass them to this point, and then suddenly hold them to higher expectations!—or even, directly, "if we don't pass them then they won't be able to graduate").

Re:Reviewing Bad Schematics as EE Interview Tactic by userbinator on Monday December 23, 2019 @05:38PM (#21868118)
The closest standard value for that resistor would be a 3k3, if I'm not mistaken...

In the software industry we have a similar problem; alot of people can follow instructions on how to glue together lots of libraries and frameworks, but have no idea how to go beyond that --- or understanding of how computers work in general --- much less debug it when something goes wrong. There's a classic article about this:

https://blog.codinghorror.com/why-cant-programmers-program/

Re:Reviewing Bad Schematics as EE Interview Tactic by mlyle on Monday December 23, 2019 @09:02PM (#21869251)
Yah, but IMO 1mA is on the "low end" of lit, so you want to round down the resistor value to get a little more current. Pick 2k7 instead.

Most small LEDs will tolerate per datasheet 20mA; 4mA is "well-lit". A little less than 1mA is going to be pretty anemic looking on lots of LEDs.

So I'd be more inclined to put down 470 to 1k5.

Re:Reviewing Bad Schematics as EE Interview Tactic by Sanzig on Tuesday December 24, 2019 @01:20PM (#21873869)
If it's just a bare LED on a board (ie: not in a case going through a light pipe or diffuser), 1 mA is actually pretty bright with modern LEDs. They're a lot more efficient than they used to be.

For use as indicators for firmware debugging under typical office lighting, I find 1 mA to be the "sweet spot" - bright enough that I can tell it's lit with a quick glance, but not so bright that if I'm staring at the board it becomes uncomfortable to look at, or distracting out of the corner of my vision.

However, if it's for indication for an operator of a device, and it's inside a case going through some lossy elements (eg: aforementioned light pipe or diffuser), I'll definitely use more current to make it a bit brighter.

Re:Reviewing Bad Schematics as EE Interview Tactic by mlyle on Tuesday December 24, 2019 @01:29PM (#21873930)
I can't be sure it's "on" unless it leaves little 0603-sized purple spots in my vision. ;)

(Maybe I'm biased because I often have my office window open and it's bright... and having couple orders of magnitude of current above what a microcontroller pullup/pulldown will source/sink has been nice sometimes-- that or I'm just stubbornly trying to justify following the very-old 4mA rule of thumb).

Re:Reviewing Bad Schematics as EE Interview Tactic by avip on Monday December 23, 2019 @05:49PM (#21868187)
I did 0.5 EE degree in the best Uni in my country with very good grades and my level of insight wrt how ICs work borderlines a Golden Retriever.

But I'm modestly good at math and the EE classes were essentially an elaborate sequence of math riddles (complex functions? Fourier? I'm great at that), superficially excused as representing some "circuit".

Re:Reviewing Bad Schematics as EE Interview Tactic by TrackerFF on Monday December 23, 2019 @08:45PM (#21869182)
When I got my BSEE, there were unfortunately only two types of professors:

1. Extremely theoretical, minimal practical elements (labs, demos, etc.). These would have classes in Electromagnetism, Signal and systems, ICs, RF, Optics, etc.

2. Very practical, but only skin deep on theory. Power systems, electrical circuits, electrical machines, etc.

The very few classes where we had a nice 50/50 ratio of theory / work were perfect, but I always felt like missing out on the other classes. Unfortunately the coursework was quite heavy, so you didn't get much time to do self-study either. Labs always crammed, always some projects / HW / home exams / labs that needed be handed in.

Re:Reviewing Bad Schematics as EE Interview Tactic by gizmo686 on Monday December 23, 2019 @09:49PM (#21869460)
Do EEs have to do any projects as part of their curriculum. I'm just an SE by training, but have done some electronics purely as a hobby. A power, resistor, LED circut is bassically my hello world for any electronics project I do. I cant imagine getting through any of my hobby projects without calculating an LED resistor at least 1. Although, at this point I always use the same LEDs, so I could get away with just looking at what I used last time.
Re:Reviewing Bad Schematics as EE Interview Tactic by alexhutcheson on Monday December 23, 2019 @11:39PM (#21869915)
Yeah, every EE program that I’m aware of has lab courses where you build things on a breadboard, learn to use the oscilloscope and logic analyzer, and probably accidentally let the magic smoke escape from a couple ICs.

However, you’re often working in groups, so it’s not uncommon for one person to really “get it” while the other members of the group nod along but don’t fully understand the choices being made. In addition, TAs in the lab probably don’t have industry experience, so there are basic practical circuit design practices that aren’t taught or enforced.

Labs are a good way to get initial experience, but I think there’s a lot that you inevitably have to learn on the job. There’s a reason you can’t earn a license as a Professional Engineer until you have 4 years of work experience.

Re:Reviewing Bad Schematics as EE Interview Tactic by cushychicken on Monday December 23, 2019 @11:02PM (#21869750)
I didn't expect when I wrote this post that the decoupling caps comment would be the one that starts the HN flame thread. XD
Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @02:50AM (#21870583)
It's pretty bizarre, you have to admit, for junior EEs not to know this — isn't it?
Re:Reviewing Bad Schematics as EE Interview Tactic by esmi on Tuesday December 24, 2019 @03:31AM (#21870728)
I don’t know. If junior = lack of experience implementing circuits in practice then I don’t think they should. After all, in theory you don’t need to bypass. In practice, you might. :)
Re:Reviewing Bad Schematics as EE Interview Tactic by cushychicken on Tuesday December 24, 2019 @08:53AM (#21872032)
The more I think about it, no - it's not.

For one thing, many of my professors (in fact, probably all of them) were very theory focused, and had very little experience implementing electronics. I think they figured that practical topics like this were too specific to lecture about, and we'd pick it up on the job anyway. I'd have to assume that mindset is not wholly exclusive to my undergraduate degree.

For another thing, I find that commonly, large employers are frequently not doing much to train their new grad EEs, or even let them near much design work. As a result, they miss out on practical experience that would teach them about concepts like decoupling.

Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @01:13PM (#21873827)
Well, I've definitely taken a pre-EE class where we breadboarded a bunch of logic circuits without decoupling caps. But #electronics on Freenode, Horowitz & Hill, and EEVblog are all pretty emphatic about them, so I figured everybody would know by the time they considered themselves a junior EE.
Re:Reviewing Bad Schematics as EE Interview Tactic by cushychicken on Tuesday December 24, 2019 @03:54PM (#21874848)
>I've definitely taken a pre-EE class where we breadboarded a bunch of logic circuits without decoupling caps

Same! I didn't realize you needed them until I entered industry. I think that's a little disappointing - it's a very simple explanation, just one that most professors don't choose to spend time on.

I'm trying to put together a good demonstration of why you need decoupling capacitors in a lab setting. Best one I can think of is paralleling a bunch of inverters with no decoupling caps, and then measuring the current draw on the rail using a shunt resistor.

Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Tuesday December 24, 2019 @05:32PM (#21875388)
Breadboard parasitics don't help. Or, rather, they do.
Re:Reviewing Bad Schematics as EE Interview Tactic by cushychicken on Tuesday December 24, 2019 @10:34PM (#21876593)
They help, until they don't. Or they don't until they do! XD
Re:Reviewing Bad Schematics as EE Interview Tactic by kragen on Wednesday December 25, 2019 @01:10PM (#21879697)
Maybe you should involve an ADC or DAC in your demo. Shitty audio is a more convincing problem than a VCC current measurement, and even tens of mV of ground bounce should be quite audible.
Re:Reviewing Bad Schematics as EE Interview Tactic by esmi on Tuesday December 24, 2019 @03:05AM (#21870636)
It’s not obvious that you need them. In modern hw especially, often you don’t. Most people add them because it is (usually) not harmful and it can be helpful and they don’t care if it’s wasteful. https://youtu.be/P8MpZGjwgR0
Re:Reviewing Bad Schematics as EE Interview Tactic by quasse on Monday December 23, 2019 @04:55PM (#21867789)
Seems like it says more about the writer's hiring pool.

I can't think of one junior EE I've interacted with who couldn't have told you what decoupling caps were for. Sizing them correctly (instead of just sprinkling the 0.1uF magic fairy dust on your board) might be another matter but I've yet to see someone fail to grasp the purpose.

Re:Reviewing Bad Schematics as EE Interview Tactic by bsder on Monday December 23, 2019 @05:12PM (#21867950)
> Sizing them correctly

Explain please?

Yes, there are some considerations when you're dealing with RF, but a modern 0402 0.1uF cap works pretty much everywhere because it has such a great frequency response due to its small size.

Now, explaining to people that their 10uF 6VDC 0402 across the power rails probably doesn't have as much capacitance as a 2.2uF 15VDC 0402 is a little subtle.

It is also an issue that decoupling caps can hold too much energy and keep a power domain operating when you wanted it shut down. That makes for some interesting debugging. Power domains now require discharge circuits because IC's use so little power.

Re:Reviewing Bad Schematics as EE Interview Tactic by detaro on Monday December 23, 2019 @06:21PM (#21868408)
There's also a difference between "can tell you what decoupling caps are for" and "when given a circuit will call them out as missing", especially in an interview situation. (Parallels probably apply to software interviews: under stress it's easier for many to answer "define X" than to identify how/if to apply X when not prompted for it)
Re:Reviewing Bad Schematics as EE Interview Tactic by rasz on Monday December 23, 2019 @08:46PM (#21869183)
I know few who never touched soldering iron.