1,092 karma · joined March 13, 2012
Furthermore, if you aren't against patents in general, there is no principled argument that can be made against software patents in particular. Software is just as inventive as other realms.
Also, there is a problem with the hypothetical, since there are other means of reducing disease than vaccination, e.g. aggressive quarantine and disinfection, trending toward telecommuting or smaller school classroom size, etc.
Why?
http://en.wikipedia.org/wiki/First_to_file_and_first_to_inve...
Glad you agree.
Should a company should be able to...
Contract theory is far more rich a subject than you realize. In your example, a rational theory of contract wouldn't be enforced based on mere promise, but would allow contracts to be broken so long as it puts both parties more or less back to where they were before. E.g., if you promise to paint my home for $100, but then you don't paint my home, I can't then enslave you and force you to paint the home, rather, I get my $100 back.
This is of course an approximate explanation.
This is just a bald-faced non-sequitur.
This is going to stifle innovation.
Now, can we see some real-world statistics by the government-licensed medical profession? I wonder what a side-by-side analysis of the errors 23andMe has made vs. those the medical community has made might look like. I wonder how the real-life consequences might stack up.
As far as I know, 23andMe has never accidentally amputated the wrong limb, so it's at least go that going for it.
Interesting tidbit: you can always double-check the reports 23andMe gives to you by getting followup tests someplace else.
On the other hand, governance by the FDA is tantamount to punishing for a crime not committed. It'd be like putting cameras in your home because you might abuse your children someday. And surely, a lot of stupid people abuse their children, right?
I don't think any sensible person from any paradigm would have objected to the code as it was originally written. The substantive arguments between paradigms happen at larger scales of code organization.
So it comes across to me that the "agnostic" is trying to make other schools of thought look ridiculous. The trouble is he's done it by cheating.
I think the true source of the problem lies not in the EE degree or lack of a CS degree, but in a specific, weird distrust of abstraction by in the institutional culture of embedded systems development. This opposition (and it is opposition, not merely ignorance) isn't coming from the degree per se but from the field as it is sometimes practiced.
My guess is that the reason for this culture is that long ago, there was a history of "fancy newfangled compilers" screwing up the code, engineers getting repeatedly burned, and learning not to trust such "fancy" tools. This attitude may have made some sense a long time ago, but now it's an institutional relic.
So the irony is: the engineers are avoiding abstraction in order to increase reliability, but they wind up decreasing it because the code becomes impossible to manage.
Anyway, this is not a defect in the way EE's are educated, it is a very specific subculture of embedded systems development, which traditionally happens to tend to hire EE's.
I have a ton of music and that's what I put on the microSD. If I lose it, no big deal, but it's really nice to be able to have all my music there.