Exactly. Especially when the reset to factory requires physical presence. In most cases it is exactly the right thing.

And yet, I see it happen. Nice to have a good clean recovery.

Or just pointing out that the girl did science and (in the same sense as saying Sir Issac Newton did not discover radium) the other scientists didn't do that particular science.

Yess, because of the HR and management problems I mentioned. There is no good technical reason for that.

def pickymethod(self, pickyobject):

"""Here there be dragons, beware"""

Problem is, A and the module that handles it is existing code used in multiple projects. IO don't want to do a cut/paste job and I don't want to risk breaking the other projects. B is from another existing module used by other projects. I REALLY just want to derive a Bprime that can serve as an A or a B as needed by the legacy modules.

Python does a decent job with multiple inheritance, but even so, it can get ugly so I might prefer duck typing and a compatible class.

True enough. As they say, it is possible to write a Fortran program in any language.

You sound bitter.

Based on the assignment and the response, flippancy is clear. Or did you suspect his neighbors somehow opened a rift in time to acquire a pet dinosaur? Perhaps they are witches?

Me lot? How many of me do you think there are? How about they blow the dust from their brains and act on credible threats rather than obvious non-threats? How about they do their job? How about they actually handle the situation like real adults instead of calling the cops every time someone sneezes?

So why didn't the hard scientists already know where the fungus was coming from?

That's right, because they didn't do the science. The girl in TFA did.

You can also cast things around until the compiler and IDE buy it and wait for the SEGV.

It's on the developer to know when they can and cannot get away with it.

If you don't KNOW if class A and Bs X methods are actually compatible, what in the hell are you doing passing them around? You're supposed to know that. If you have a case where it may or may not be true and it's all OK, wrap it in a try..except and pick up the pieces at runtime.

This would be a lot less of an issue if multiple inheritance was better supported, but it's not.If it was, I could write the module explicitly around class A. Later, given a class B that should work fine with the module, I could derive Bprime inheriting from A and B and it would be fine.

You question the conscientiousness of the programmers in the first paragraph and assume it in the second.

You should see the crazy type casting that happens in production code to please the IDE and/or compiler. It may or may not be the right thing.

Then there's the cases where it is actually OK if not all objects passed in support all of the methods. Not Applicable might be the right outcome of a method call if the caller is prepared for that possibility.

I would say more compromise is needed, particularly for smaller operations where one more or less person is significant to the operation, but at the same time, if the operation is large enough to claim they have permanent openings and need H1-Bs to fill them, they should jump for joy at the return of a pre-vetted professional.

Perhaps if employers made more concessions to work-life balance in the first place they wouldn't find themselves in this position today.

Actually, approval does not in practice require the new drug to be as good as or better than the original in any way. It has to show the basic safety and be more effective than placebo.

In many cases, the inexpensive generic isn't even tried before jumping to the expensive option unless the patient brings it up or, in some cases, insists.

My objection is not to the me too drugs in and of themselves, it is to the order they are tried in practice.

The insurance companies are right (for once) to push back when the generic isn't even considered first. They are wrong to keep pushing when the doctor has any articulable reason to go with the more expensive drug for that particular patient, especially when the patient was on the generic and had a problem that the me too might solve.