←back to thread

903 points tux3 | 1 comments | | HN request time: 0.267s | source
Show context
jerf ◴[] No.43546861[source]
One of my Core Memories when it comes to science, science education, and education in general was in my high school physics class, where we had to do an experiment to determine the gravitational acceleration of Earth. This was done via the following mechanism: Roll a ball off of a standard classroom table. Use a 1990s wristwatch's stopwatch mechanism to start the clock when the ball rolls of the table. Stop the stopwatch when the ball hits the floor.

Anyone who has ever had a wristwatch of similar tech should know how hard it is to get anything like precision out of those things. It's a millimeter sized button with a millimeter depth of press and could easily need half a second of jabbing at it to get it to trigger. It's for measuring your mile times in minutes, not fractions of a second fall times.

Naturally, our data was total, utter crap. Any sensible analysis would have error bars that, if you treat the problem linearly, would have put 0 and negative numbers within our error bars. I dutifully crunched the numbers and determined that the gravitational constant was something like 6.8m/s^2 and turned it in.

Naturally, I got a failing grade, because that's not particularly close, and no matter how many times you are solemnly assured otherwise, you are never graded on whether you did your best and honestly report what you observe. From grade school on, you are graded on whether or not the grading authority likes the results you got. You might hope that there comes some point in your career where that stops being the case, but as near as I can tell, it literally never does. Right on up to professorships, this is how science really works.

The lesson is taught early and often. It often sort of baffles me when other people are baffled at how often this happens in science, because it more-or-less always happens. Science proceeds despite this, not because of it.

(But jerf, my teacher... Yes, you had a wonderful teacher who didn't only give you an A for the equivalent but called you out in class for your honesty and I dunno, flunked everyone who claimed they got the supposed "correct" answer to three significant digits because that was impossible. There are a few shining lights in the field and I would never dream of denying that. Now tell me how that idealism worked for you going forward the next several years.)

replies(46): >>43546960 #>>43547056 #>>43547079 #>>43547302 #>>43547336 #>>43547355 #>>43547446 #>>43547723 #>>43547735 #>>43547819 #>>43547923 #>>43548145 #>>43548274 #>>43548463 #>>43548511 #>>43548631 #>>43548831 #>>43549160 #>>43549199 #>>43549233 #>>43549287 #>>43549330 #>>43549336 #>>43549418 #>>43549581 #>>43549631 #>>43549681 #>>43549726 #>>43549824 #>>43550069 #>>43550308 #>>43550776 #>>43550923 #>>43551016 #>>43551519 #>>43552066 #>>43552407 #>>43552473 #>>43552498 #>>43553305 #>>43554349 #>>43554595 #>>43555018 #>>43555061 #>>43555827 #>>43676296 #
don-code ◴[] No.43548274[source]
This is, more or less, exactly what happened when I took Electronics I in college.

The course was structured in such a way that you could not move on to the next lab assignment until you completed the one before it. You could complete the lab assignments at your own pace. If you failed the lab, you failed the class, regardless of your grade.

The second or third lab had us characterize the response of a transistor in a DIP-8 package, which was provided to us. If you blew it up, you got a slap on the wrist. That DIP-8 was otherwise yours for the class.

I could _never_ get anything resembling linear output out of my transistor. The lab tech was unhelpful, insisting that it must be something with how I had it wired, encouraging me to re-draw my schematic, check my wires, and so on. It could _never_ be the equipment's fault.

Eight (!) weeks into that ten week class, I found the problem: the DIP was not, in fact, just a transistor. It was a 555 timer that had somehow been mixed in with the transistors.

I went and showed the lab technician. He gave me another one. At this point, I had two weeks to complete eight weeks of lab work, which was borderline impossible. So I made an appointment to see the professor, and his suggestion to me was to drop the class and take it again. Which, of course, would've affected my graduation date.

I chose to take a horrible but passing grade in the lab, finished the class with a C- (which was unusual for me), and went on to pretend that the whole thing never happened.

replies(17): >>43548368 #>>43548469 #>>43548484 #>>43548871 #>>43549249 #>>43549256 #>>43549629 #>>43549683 #>>43550176 #>>43550399 #>>43551048 #>>43551251 #>>43551551 #>>43553532 #>>43554766 #>>43554936 #>>43556056 #
orlp ◴[] No.43548484[source]
What I don't understand is why it took you 8 weeks to distinguish a timer from a transistor. That doesn't make your professor's reaction alright, I just find it puzzling.
replies(7): >>43548759 #>>43548763 #>>43548830 #>>43548967 #>>43549241 #>>43552038 #>>43553256 #
Isamu ◴[] No.43548967[source]
Same package. 555 is typically a DIP-8, transistor packages are available in the same. So you would have to examine the cryptic markings and compare them with the other students, and that’s only if you suspected some fuckup on the part of the knowledgeable people.
replies(2): >>43549362 #>>43550301 #
cycomanic ◴[] No.43550301[source]
But that's the thing that both students and often the teachers forget. We don't run labs to go smoothly, we run labs because you'll have to troubleshoot. There is no learning experience in a lab that works without issues, in fact IMO if lab instructions are of the step by step type, they should always have some deliberate errors in it to get students to troubleshoot.

To play devil's advocate, just imagine the previous posters Story at a company, i.e. a junior engineer not being able to make some simple tasks work and telling their supervisor "it doesn't work" and it turns out after 8 weeks they grabbed some wrong part. Should they have expected their supervisor to check all the parts? Should they expect a good performance evaluation?

replies(5): >>43550498 #>>43550532 #>>43550709 #>>43552039 #>>43557473 #
CodeMage ◴[] No.43550498[source]
> Should they expect a good performance evaluation?

They should expect that particular incident to not affect their performance evaluation, since it was very much not their fault.

In your hypothetical scenario, your hypothetical junior engineer went to the senior engineer repeatedly for advice, and the senior engineer did not do their job properly:

The lab tech was unhelpful, insisting that it must be something with how I had it wired, encouraging me to re-draw my schematic, check my wires, and so on. It could _never_ be the equipment's fault.

This is a huge failure in mentorship that wouldn't be ignored at a company that actually cares about these things.

replies(1): >>43550959 #
cycomanic ◴[] No.43550959[source]
> They should expect that particular incident to not affect their performance evaluation, since it was very much not their fault.

What do you mean not their fault? I've seen wrong parts delivered by suppliers, so yes responsibility of an engineer who puts together a circuit is definitely checking that the parts are correct.

> In your hypothetical scenario, your hypothetical junior engineer went to the senior engineer repeatedly for advice, and the senior engineer did not do their job properly:

>> The lab tech was unhelpful, insisting that it must be something with how I had it wired, encouraging me to re-draw my schematic, check my wires, and so on. It could _never_ be the equipment's fault.

Again _never_ the equipment's fault? It wasn't the equipment it was a part. So maybe it was an issue of miscommunication? I find it hard to believe that the lab tech said it could never be the parts, considering how those things are handled in student labs, small parts break all the time.

Maybe, it's true and it was a crappy lab tech, maybe they could not imagine the part being broken, but I've seen the other side of the equation as well, when things don't work students often just throw their hands up and say "it doesn't work" without any of their own troubleshooting expecting the tutor/lab tech/professor to do the troubleshooting for them (quite literally, can you check that we wired everything correctly...).

In my experience this does not get accepted in industry. I acknowledge though what the other poster said, generally in industry incentives are different and someone would have intervened if a project gets held up for 8 weeks by a single person.

Regarding the story, I wonder what would have been an acceptable solution (apart from the lab tech possibly being more helpful?), I as a teacher would have excepted a report which would have given a detailed account of the troubleshooting steps etc. (but it needs to show that a real effort to find the cause, simply saying the lab tech couldn't help is not sufficient). Simply saying "it wasn't my fault because I had a wrong part" shouldn't just give you an A.

replies(2): >>43551831 #>>43552023 #
1. CodeMage ◴[] No.43552023[source]
> What do you mean not their fault? I've seen wrong parts delivered by suppliers, so yes responsibility of an engineer who puts together a circuit is definitely checking that the parts are correct.

Let's not move the goal posts, please. If you're going to use a hypothetical situation as an analogy, make sure it's actually analogous. Yes, an engineer who puts together a circuit has that responsibility, because they're an engineer. They went through the required training that makes them an engineer and not just an engineering student.

> I find it hard to believe that the lab tech said it could never be the parts, considering how those things are handled in student labs, small parts break all the time.

And therein lies the problem. You "find it hard to believe" that the lab tech could have been that unhelpful, just like the lab tech found it hard to believe that the student wasn't doing something wrong. Both you and the lab tech are behaving in a way that is inappropriate for a senior mentoring a junior.

In my experience mentoring others, the first assumption should not be that the person you're mentoring simply didn't do enough and that they should try to do better. Yes, that might end up being the case, but most of the time there's also something else that could have been done better. Maybe the documentation is not clear enough, maybe the process didn't help catch the mistake, maybe the expectations I set weren't clear enough, maybe I didn't communicate well enough.

"Go check your work again" is rarely helpful, even in the extremely rare cases where that's the only thing that needed to be done and no other improvements exist. If you're really convinced that they merely need to check their work again, guide them to it.

That's why they are junior and you are senior, because they need more guidance than you do. They will not develop the necessary insights and instincts without that guidance.

> I've seen the other side of the equation as well, when things don't work students often just throw their hands up and say "it doesn't work" without any of their own troubleshooting expecting the tutor/lab tech/professor to do the troubleshooting for them (quite literally, can you check that we wired everything correctly...)

And in turn, you're arguing that the mentor should merely throw their hands up and say "go check your work yourself". Again, even that can be said differently: "Can you explain what you have checked so far and how you've checked it?"

> Simply saying "it wasn't my fault because I had a wrong part" shouldn't just give you an A.

You are drawing a lot of your own conclusions from what hasn't been said. In this comment thread, you have repeatedly and consistently shown bias through your assumptions. Yes, what you're saying could have been the case, but I see no evidence of it and no reason to simply assume it without at least inquiring about it.