richx
Joined 9 years ago
Joined 9 years ago
I think one very important aspect is requirements collection and definition. This includes communicating with the business users, trying to understand their issues and needs that the software is supposed to address. And validating if the actual software is actually solving it or not (sufficiently).
All of this requires human domain knowledge, communication and coordination skills.
https://www.bbk.bund.de/SharedDocs/Downloads/DE/Krisenmanage...
https://www.tesla.com/ownersmanual/model3/en_us/GUID-E95DAAD...
Edit: interestingly, the German link seems to show something else: https://www.tesla.com/ownersmanual/model3/de_us/GUID-E95DAAD...
It’s such a great vehicle, I smile every time I can ride it. It also helped me to use the car less.
Im also pretty happy with my Plumelabs Flow, a small device that constantly measures air pollution. We used it to find a new and better home:
https://plumelabs.com/en/flow/
I also replaced my Android HTC U11 with an IPhone XS. I was always an Android user, but to be honest, I think IPhones are much better.
But there are two other things that make it a bit unfair for Tesla in comparison to other brands:
Often the cars fail official inspections because of rotten breaks - this happens when your drive carefully and the Tesla is using regenerative breaking instead of the real breaks. Simple solution is to force breaking from time to time (I.e. breaking in neutral). Another aspect is, that all the other brands have a mandatory inspection from the manufacturer before the cars will be tested by the independent check. This avoids that they will fail it, because the car will be repaired before it is checked by the independent inspection. This is not mandatory for Teslas.