I had a friend with a 2012 Leaf that experienced similar degradation. It was a problem with the early model year and Nissan's choice to use passively cooled batteries.
Yes, the Leaf uses passive battery cooling as opposed to Tesla and others with active cooling. Their first-gen battery chemistry was also worse in hot climates. The newer battery is a different chemistry that has held up better.
The 2011/2012 Leafs had major problems with battery degradation in hot climates so much so that Nissan was forced to offer a free battery replacement. So I got it replaced for free. The newer battery is lasting better, but still not great. I think Nissan screwed up by sticking to passive battery cooling.
For reference I live in southern Florida so we have hotter than average climate.
I own a 2012 Nissan Leaf which has had major battery degradation (first battery went under 70% in only 33k miles, second battery currently around 85% at 45k miles = 78k miles total on both). But on this site, the 2012 Nissan Leaf has less than 2 years of data and shows zero degradation during that time. So it seems like the data is questionable.
Every discussion or article I have read on dependent types assumes that the reader is a mathematician. I usually make it only a few paragraphs in before I am completely lost.
Right now the only thing that seems clear is that dependent typing adds significant mental burden on the programmer to more thoroughly specify types, and to do so absolutely correctly. In exchange for that burden, there must be practical (not theoretical) benefits but they do not come through clearly. All of the examples I've seen are about "index of a list is guaranteed in bounds". That is such a minor and infrequent bug in practice that it does not justify the additional complexity. There must be more, that I'm just not seeing.
Is there a "Dependent types for non-mathematicians" article out there somewhere, where I can learn about patterns and practical applications?