Hacker News new | ask | show | jobs
by luckydude 3223 days ago
I use the phrase "that's an impedance mismatch" all the time. Software guy who has done some hardware stuff. I use it in the context of humans: "Sending $ENGINEER to do that job is an impedance mismatch, they'll screw it up". Stuff like that. Love that phrase, might be misusing it, still love it.

On "is it the flip side of the same problem of an Engineer who complains management doesn't get it" I'm not seeing it. I mean, maybe, but management usually gets it in my experience. It's a much more rare event to see a manager not understand all of the costs of doing something, that's a big part of their job. So maybe it's the flip side but it's just not that common (in my experience, I've had mostly good managers).

Here's maybe why I don't see it: I see good engineers screw up on the money stuff all the time, it's very common. I very rarely see good managers "not get it". In the engineer, it's like a blind spot, it's not because they are stupid. When managers don't get it it is usually a sign they aren't a good manager. So to be the flip side, you'd have to have good managers not getting it and I believe that's uncommon.

1 comments

> Stuff like that. Love that phrase, might be misusing it, still love it.

Yeah, love those concepts that lend themselves well to other systems (signal to noise ratio, inertia, etc).

What I meant, I may have "packaged" my message clumsily, was the following: is an Engineer's duty, in the context of their job, to package "technical" information for the manager not the flip side of the manager's duty to package "managerial" information for the Engineer.

The Engineer complains that management doesn't get "obvious technical" information the same way management complains an Engineer doesn't get "obvious management" information, which might cause mutual disdain, and ~°we all know°~ it's easier to have disdain for people with questionable hygiene and appearance, so there's that.

I guess an Engineer's struggle with money stuff is really the same as the inability of someone to solve a Physics problem: one needs to have the data in the right dimensions, the laws that apply to them, and know how to apply them. Then practice doing so.

An Engineer's inability to "get money stuff" is one or more of the above missing (cash vs cash flow for figures of the right dimension, for example), knowing the rules to apply to money, and then the practice of applying them.

I dunno. It seems more weird to me that the engineer, um, "engineer" as in good at math, good at seeing a whole system, doesn't apply those skills to their own compensation package.

It would be a whole lot less weird to me if we were talking about, I dunno, anyone who isn't good at systems/math.

It's just a big blind spot, at least it is in the USA. I don't get it.

It should be the case.. Then again, there's the "conjunction fallacy"[0]. There's the case where the staggering majority of participants who were trained in probability got the test wrong.

Anyway, thanks for the input. Fascinating how we function.

[0]: https://en.wikipedia.org/wiki/Conjunction_fallacy