than actual skillsets.
I've seen applicants unable to configure an op-amp as a unity gain buffer.
I've found that good interview questions identify how a prospect
*approaches* a problem. As such, they don't require pencil and paper but, rather, a conversation in which the questions asked (by the applicant) reveal whether they can *think* about a problem, not whether they can recall a particular skillset in that setting.
CompSci doesn't teach programming.
As far as voltage dividers go, I'm sponsoring/mentoring some senior capstone projects at a couple of nearby universities. That will give me a chance to possibly meet and work with the rare kid that actually understands electricity.
This problem will get worse because I'd have to admit that although I wouldn't take long to write and debug such a program myself, I'd do the following because it may provide ideas for doing it more efficiently than I did.
for num in range(1, 101): output = "" if num % 3 == 0: output += "Fizz" if num % 5 == 0: output += "Buzz"
# If output is still empty, print the number; otherwise print the string print(output if output else num)
Which was tested here.
With any luck you will meet one of the even rarer kids who can identify a pompous creep and know how to send him up.
Sure. However:
1) To have a proven track record you need the first time. 2) PhD is really not a binary thing. One needs to write thesis, which may be only words. But thesis may be also a substantial project delivering tangible things and showing sucessful execution in technical area.
Of course! But there need only be *one* "first time". In most places, the "tech" community is relatively small; it's not uncommon to bump into the same people at many different places, over the years.
I think most schools require a "senior project" of some degree of originality, even for a BS. And, that not counting any "lab" courses that you took along the way.
[I designed a CDI in one; a two-player "Breakout" in another.]Part of that being a means of showing you can take a project (idea) through to completion, beyond just "homework assignments" (which often just test how well you can regurgitate material in a different form).
Not exactly. A Ph.D. requires a fairly serious engagement with the published literature - it has to include a literature review that sets it in context with earlier published work and has to be be original enough to be publishable in it's own right, though not necessarily in any kind of high-prestige journal.
I never published mine, but that was because I was never able to write a short enough paper to be remotely publishable. By the time I'd mastered the art of writing publishable papers, my Ph.D. work was too old to be all that interesting, and I never came across a journal where it would have been a good fit. Still haven't.
My interns, so far, have wanted to come back for a second summer session. Well, we do pay them a lot.
They have said that they learned a lot, and one recently said that he was honored to be allowed to intern with us. He went to a 2-year community college and has just got into UC Berkeley for his last 2 years; that almost never happens.
What shocked me is that the recent EE grads that I've met don't know what a transmission line is. I have to teach them.
John Larkin Highland Tech Glen Canyon Design Center Lunatic Fringe Electronics
Try asking them to draw a bridge rectifier.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required