4 ms·
For a lay person, sure. But these are experts at automotive engineering. Imagine if you were reviewing a new developer's code, and you were puzzled by a particu
by falsedan 8y ago
For a lay person, sure. But these are experts at automotive engineering. Imagine if you were reviewing a new developer's code, and you were puzzled by a particularly non-idiomatic implementation where you can't see the reasons for avoiding the idiomatic version. Are you going to think that maybe this is some technique you're unfamiliar with, or that the person who'se still quite new to developing might not be aware of the idiomatic verions?
- rando444 8y agoI get where you're coming from, but Tesla engineers have seen those flanges and that extra steel in crash tests where these engineers have not. Your example would be more akin to assessing someone's code and pointing out potential flaws without ever executing it.
- sangnoir 8y ago> Your example would be more akin to assessing someone's code and pointing out potential flaws without ever executing it. You've just described a code review, which is standard practice and not controversial. If an expert doesn't understand your code, maybe the criticism is informed by their experience.
- andrewflnr 8y agoOn the other hand: "take note that I have only proven this code correct, not tested it." Code review is performed in the understanding that its results are basically heuristic. Everyone knows that actual behavior trumps anything you get from just looking at something.
- derekp7 8y agoSo a good example of this in code would be: a = a xor b; b = a xor b; a = a xor b; In this case it is a technique for swapping two variables without using a third variable. But it really serves no efficiency purpose in most applications (however it is fun to use).