Was dissatisfied with existing crossword assistance sites, as they all seem to have 2010-era UIs and be so ad-heavy as to be almost unusable. This is my attempt at a fast, light crossword assistant that works well on mobile.
Author here. I did consider this, as others have reported getting ADS1015 marked as ADS1115. If it were an ADS1015 the readout would be truncated at 12 bits. These parts definitely delivered 16 bits of readout.
This happened to Lance Armstrong. As one investigator put it, his 1999 urine was meant to pass the drugs tests available in 1999. But when subjected to tests developed 5 years later, it failed.
It's hard. Because everyone claims to be doing TDD, just asking in the interview "do you do TDD" is pointless.
Example. Last year I consulted at an IC company, building a huge "moon-shot" chip. You might expect TDD to be an absolute certainty in such an operation. Not so, individuals had all sorts of justifications for not doing TDD.
Here is one idea. In the technical interviews, when the inevitable "and do you have any questions for me?" moment comes up, ask them to talk about their best test.
If they have a good answer, it's likely you've found somewhere that genuinely values TDD.
Yes, ICs age. Fissures in the subtrate expand with each thermal cycle. Delamination is a similar effect. That's how manufacturers prematurely age their parts -- by endless cycles in the oven.
The biggest culprit is flash memory. It's in almost everything, and has a much shorter life than the 10 years most manufacturers claim.
I have an asynchronous CPU cluster on my desk right now (a pair of GA144s). The performance spread isn't actually very dramatic; just a few percent. After all, the foundries aim for consistency so that synchronous devices get good yields.
I make chips for a living, and if I had screwed up this badly I would fully expect to be fired. Being fired for incompetence is much more demeaning than gentle mockery by people writing a workaround.
Instead of that complicated minute/day/week/year data retention scheme, why not just randomly replace an entry in a fixed-size store? So the probability of a datum being in the store is inversely proportional to the log of its age.
And it's a one-liner.
I write Forth code for tiny microcontrollers that are embedded in ASICs. They are ROM-based, and have to work first time. Size is a few hundred bytes, so C is out of question.