Wellp, if everything didn’t have to be done yesterday (even if only assigned today), there’d be more time to debug code and make sure it would be quite stable.
I did exactly that, regardless of when it was “needed”, and my boss snarkily called it “the G factor”. Ie, if it could take him 1 day to do something, it’d take me 3 days instead, at least according to him. Then again, he had no clue what built-in functions like memset() were, so he had his own function to clear string space (even if not even needed). :person_facepalming:
What I do now is ask, preemptively, “Do you want it done fast or do you want it done right?”. Answering “both” is unacceptable. If minutes count, and you need it now now now, I’ll do it fast, with emphasis on getting it done as fast as possible, with zero error-checking or sanity-checking. If you want it done right, it’ll take more time.
I’ll actually try to break it, to imagine the impossible happening, to check edge-conditions, etc. And even then, sometimes you just miss something.
Gotta admit, though, it was quite clever!
First, they designed to the test, based on the fixed and published driving cycle of the test. Then, check to see if the car’s likely on a treadmill or actually on the road.
James Kirk would be proud!