- #4,166
Klystron
Gold Member
- 1,160
- 1,794
Thanks for the corroboration. Forty to fifty years since my hands-on RF lab work. Your second point contains the corollary that inputs from another engineer not invested in the outcome can help clarify one's thinking; true for many professions such as medical diagnostics.DaveE said:Yes, me too. I was sooo much smarter 30 years ago. I knew a bunch of stuff I never used much, or ever, which has now drifted away.
But, a couple of related points.
1) This is the sort of problem that can have several solutions from simple (buy the right instrument) to complex (PLLs to filter, demodulate and sample etc.). Which are really based on how much you care, how hard is the problem, and how much time and money you have. This causes a bit of confusion to people that understand the options but not the all of the constraints.
Which leads us to:
2) Working engineers are working. They will spend much more time and effort thinking about their specific problems than we will. When I was actually paid for this sort of thing I probably would have spent at least a day thinking about the solution, sometimes much more. OTOH, we won't. We toss out ideas based on our previous experience, learned by actually solving these things. If you cared more because this was your problem, not someone else's, you would sort all of that out.
Good point about cost as an aspect of problem solving. Scale also limits solution sets. For example, I would design a full-scale data center with an ATS (automatic transfer switch) between municipal power and emergency generators, while a DIY homeowner might rely on manual switching.
Last edited: