Re: Limped after Apple II
"The only other brand I can think of with such a turnaround is Audi."
What about BMW? Remember the Isetta.
43034 publicly visible posts • joined 16 Jun 2014
"Motorola workstation....the soldering on the original was terrible with dry joints all over the place"
Motorola H/W problems. That rings a bell.
I had a gig which involved adding some reports to a factory control system that ran on a Motorola server and then involved going to Italy to install them on site. Reports, no problem. Installation, no problem. But then the server kept crashing and what looked like leaving bits of memory dump in files in lost+found after running fsck. The client's client didn't want to let me go until it was all working & I was rapidly running out of Lira. I eventually escaped & heard later it was a hardware memory failure that was responsible.
"I'll click through to read the full story."
This is one thing that tends to be overlooked. I haven't followed the politics of this so I'm not sure just what line the newspapers are taking on this but ISTR that in some instances Google stopped quoting and the newspapers found their site traffic falling off which wasn't at all what they wanted.
"I suspect that what went wrong with the 23andMe samples"
According to the CBC article the 23andMe results agreed to within 0.4%. The substantial differences in interpretation must be down to that 0.4% and/or the possibility that, as someone else posted, each analysis covers a subset of the genome. The 99.6% agreement would then apply to the common sections that were analysed. The differences between the variability of the 23andMe interpretations and the consistency of, say, the Ancestry variations are probably telling us something about the differences in the nature of the combinations of the interpretive algorithms and their underlying data.
"Each test should have returned the same percentages for them."
Not so much each test, more the interpretation of the tests. The 0.4% difference (presumably experimental error in sequencing and/or mutations during development) seems to have thrown the interpretive algorithms of some vendors more than others.
To my mind the differences in interpretation between the other two vendors is interesting. They give very similar results between the twins but pretty substantial differences between the vendors in what these mean. It suggests to me that the real problem in all of this stuff is the data on which the interpretations lie. Any place in Europe has a population whose ancestors got there by a variety of different routes and which swapped elements of the population with other places. The result isn't entirely homogeneous but it's certainly fairly mixed and each of these businesses (and academic investigators also) are taking sub-samples of this mix and characterising them as some sort of type specimens and then using them to interpret subsequent analyses. I doubt the underlying data are really good enough to make proper sense out of this, nor will they be for a few more years.
It all reminds me of the situation back in the '60s/early '70s when we were starting to apply carbon dating to archaeology (and palaeoecology) but without a good enough corpus of dating material to make real sense of it. E.g. having some nicely dated pollen diagrams of the Irish late bronze age and a nice archaeological write-up of the Irish late bronze age which seemed to fit but without a single carbon date for the archaeology to test that fit.
"This article just shows a total lack of understanding by the author and by the originating source."
Did you read the originating source? Did you notice the bit where the downloaded 123andMe data had 99.6% agreement? Can you, from your alleged understanding, explain how closely the parents would have to be related to each other to produce a result like that from non-fraternal twins? I don't think even the Hapsburgs could have managed it.
"Most of various DNA companies allow you to download the genetic data they have."
TFA has a link to https://www.cbc.ca/news/technology/dna-ancestry-kits-twins-marketplace-1.4980976 Let's take a look:
"The team at Yale was able to download and analyze the raw data set that each company used to perform its calculations."
and
"According to the raw data from 23andMe, 99.6 per cent of those parts were the same, which is why Gerstein and his team were so confused by the results. They concluded the raw data used by the other four companies was also statistically identical."
I do, however, wonder about "identical" when qualified with the word "statistically". I'd have been inclined to say "indistinguishable" - and"were" rather than "was".
"Two tests for the same person vary by only a handful of SNPs. That is, there is noise, but it's not very loud. Different companies' tests report different SNP values, too. Again, very quiet noise."
Agreed. It must be the noise sensitivity of the "ethnicity" interpretation that accounts for the apparent difference between the sisters. In fact the major components are fairly close for any given pair of analyses. It's the smaller components which seem to be beneath the noise floor so to speak. Ancestry and MyHeritage seem to come out better on this basis.
The real problem is where the components get a geographical label attached. Humans have been wandering back and forth for some considerable time. Take any particular person from any particular place in Europe or round the Mediterranean (which seems to be what these figures are suggesting) and you'll have picked someone whose ancestors will of necessity have taken a long route - and a variety of long routes - to get to that place. Take a second person from some other place and their ancestral routes will also be long and varied and some of them will coincide with the first person's.
Add that up over the the European and Mediterranean area and then reflect how much sense it makes to try to work out what Greek or Italian or Balkan or any other of the labels means. It's no surprise that although Ancestry and MyHeritage can match the twins to each other within the noise limits they differ wildly from each other in what those mean when they try to sort out Italian from Balkan from Greek from Eastern Europe from Russia.
My ethnicity? 90% sceptic, 10% others.
"Truth is, the multi-species conventional wisdom is looking more and more pants."
Did anyone catch the 2018 Royal Institutional Christmas Lectures (only 3 - there used to be 5, everything goes downhill)? This year it was a two hander, the anatomist Alice Roberts and a geneticist guest lecturer, Aoife McLysaght. Roberts was presenting the usual Neanderthalis vs Sapiens when McLysaght interjected "it's all one species". It's the old splitters versus lumpers all over again.
"Frankly, I won't trust an English website on French grammar or literature."
I would, however, trust it on French phrases adopted in English. As far as I can see it makes sense with either verb. The OP version, if my long-ago French classes can be relied on, means "the more things change the more they are the same" which makes the same point, arguably more pithily.
"I get stick about this every day because it causes them inconvenience, mainly as they need to e-mail something to a group rather than e-mail a link."
Have you wondered if providing mutually acceptable users' problems might be part of you job?
"Coloured text on a coloured screen; colour-blind user."
It's surprising how this can get overlooked. In my area of forensic science we tended to do a lot of colour matching of fibres in microscopy. My initial boss couldn't do that part of the job, he was colour blind*. About 4 years later when I'd got to the level of doing recruiting my office-mate & I decided we really should screen candidates for colour vision.
*He'd come in via a medical lab-tech background where microscopy tended to use red/blue staining.
"Programmers bear some responsibility for this, using unexpected jargon etc., and few companies seem prepared to review all user-facing text for clarity."
They're probably in a cleft stick here. On the one hand you can give a short message and have complaints about jargon or use descriptive terms and have complaints about it being too long to read. A good idea, however it to avoid messages such as "ERROR SJIWEK00000340000SDIJKEW".
On the whole one probably should be able to expect users to understand the basic terminology of whatever it is they're dealing with. Try driving a car if you don't understand "brake" or "starter", or using your TV if you don't understand the word "channel".
"would have expected the Lib Dems, Greens, SNP and PC to have done much better in 2017 election"
The LibDems were still being punished by their erst-while protest-voting supporters for actually taking responsibility and joining a coalition government rather than being ineffective.
"Many error messages (even in Windows) tell you exactly what you need to do to solve the problem at hand. Instead of heeding the message to reboot, add paper to printer, enter a missing value where the glaring red line of text tells them to, they call our (only slightly less clueless) helpdesk."
To be fair the users probably have difficulty distinguishing between these error messages and the huge number that don't.
I've probably also left the odd button lying around that does nothing but print "WIBBLE" or "BLAH", because that is just something I do as one of my program development stages.
Years ago I wrote a code generator. It dug into the database's system catalogs for a table descriptor, generated a data structure to hold a row, added code to emulate a scroll cursor which the database engine didn't have at that time, added a menu including some stubs and default code for queries, updates etc. The generated code had a default but harmless name on the menu with the idea that the generated code would then be edited to give the menu, prompts etc sensible text and flesh out the stubs as required. I took it with me on various jobs.
I was working with it on one job when I got an offer elsewhere I wasn't going to refuse and left PDQ.
Forward 11 years, now freelance, I had a gig to oversee some acceptance testing prior to a machine migration (Y2K). It turned out that they were using the now mature product from that old job. And there was a menu with the unchanged default text. I didn't look too deep but they were probably still running the no longer needed emulated scroll cursors. (We had the source on site and I suppose I could have finished that little task from way back but it would probably have caused confusion.)