403 karma · joined July 30, 2014
I own several Raspberry Pi’s. One of them is taking time lapse photos of a skyscraper going up two blocks away from my office. It had trouble uploading the photos every morning around 7am. It tended to catch back up at night. The problem went away once I replaced my 2amp power supply with a 2.5amp model. Day photos produce larger image files than night photos. My theory is the Raspberry pi had trouble processing and uploading the larger image files while running under voltage.
I wonder what happens to the scooter after that. Landfill? Recycle?
On a related note, I see Renovo Hardwood Bicycles shut down earlier this year.
That can’t possibly be correct.
Now I only work for companies that use their software to provide a service. There is more of an incentive for the software to actually work.
That aside, you can't tie all of life expectancy to health care. For example, diet, life style, genetics, and environment are all factors too.
I also disagree that whether an integration test can cover some part of your code is the litmus test for whether the code is relevant. There are types of errors that are relevant but complicated to simulate in an integration test, or at least in an automated integration test.
An example would be a network partition. It's involved to code a test to cause the partition, wait for the various timeouts to take place, then heal the partition, then wait some more for things to start talking and recovering. And depending on who owns the test environment and how your organization is managed, you may need to negotiate with a DevOps / Operations / Security person to get permission to run iptables in the appropriate machines.
On the other hand, unit-testing what happens when a connection fails is probably pretty easy.