Quote:
Originally Posted by ChrisH
Quote:
Originally Posted by CMSD
...of course, the code was automatically blamed, and later proved to be completely flawless  |
I find this very hard to believe. Flawless code would violate the First Law of Programing. There must be a flaw, you just haven't found it yet  |
Well, of course: performance issues. Fortunately, we are dealing with an RTS, which means it doesn't need to perform well, just `well enough'.
Seriously though, missing features. We made this code work, so we didn't get to the [x cool feature] (camera, gyros, accelerometers)
There will always be flaws, however, it is a skill to control where they are. What he means is that the relevant portion of the code was flawless.
Quote:
Originally Posted by Andrew Schreiber
The programmer should not rule out a code issue in any circumstances that they cannot back up that with definitive proof. No, "Because I wrote it" is not proof.
|
When I say this, it is said in good humor, although it usually ends up being true. And, even while I say it, I am usually running though the code, checking out if it could be a code issue. (It's even become sort of a good humored routine to blame programmers, then for us to retort).
What bothers me is when we know it can't be code for whatever reason (see the 2nd part of my above post), and people still insist it is. When I say, ``Look, trust me, I have considered this. It's not code.'' please trust me. I know what I'm talking about. Sure I'll check it again, but that's not going to be it, so don't waste both of our time, have someone else be checking other stuff too. Don't make them move so I can prove to you that it is not code.