no doubt

My boss was one of those turbo wizards though, so that helped.

It's frustrating debugging bad connections

Especially when they're faulty by (bad) design

are you one of the fuckers that add a shitload of 0 ohm resistors unmarked so its imposible to reverse engineer?

Turns out that EEs aren't good mechanical engineers

I once had to diagnose a desktop which kept powering off for temp reasons

and eventually we just ruled that the temp sensor itself was fucking knackered

Which is really frustrating because the only way you can rule that is to stick your fingers in the heatsink and note that it's fucking cold even when the machine is 'overheating'

Imagine trying to do that for something like a guidance system

Horrifying.

And then convincing them "well, it's the motherboard's fault"

And you're shipping the built-in-test for the next contractor in the chain

can you change a temp sensor on a motherboard? , I thought most sensors are etched in silicon

And you can't do shit because contracts are already signed and you can't do a complete redesign because your little firm may be bankrupted

Yeah, sounds like it'd have you really backed into a corner.

software is comfy

You can always ship a patch

exceptvin embedded design...

Hardware is frightening and nightmarish in comparison

So you'd have to forgive if us hw guys are more autist

We literally have to have whole designs in our heads running in pseudo simulation casually

Which leads to cool a-ha moments

Fortunately, I've only been stuck with fault-finding and repairs.

But it's generally shitty

Either way, you do have to be a giant fucking autist with hardware, because it's like you said.

You have to be 100% with what you do.

Yeah repairing and hobby stuff is fun

I'd hate the fault finding thing

Well you need a better testing framework and harness

>Framework

lmao we just winged it.

So you can plug in a single test point and test mostly everything you care about

My boss would go "Are you 100% sure, 200% sure, etc."

jtag?

Until you crack and go "uh"

"fuck off then"

apprentice life

jtag is a thing sure for running incircuit tests but you may want for stuff for application specific passive components

We had a bad "cable" once kill months of testing

sheeit