11–18 of 18 posts
Nice piece of history, and hilariously/sweetly innocent/naive in its specificity and certainty, like only newbies' first "design document" could be.
Too bad there's nothing about handling recursion of the portal rendering.
- Precompute whenever even remotely possible.
- Measures must be taken to prevent copy paste errors.
- Measures must be taken to prevent copy paste errors.
- The STL is evil (most of the time).
- Unnecessarily virtual functions should be rewritten to remove virtual requirements.
- Sloppy code must be marked for recoding later.
- Unreadable code earns you a free punch in the face.
- Measures must be taken to prevent copy paste errors.
Nice piece of history, and hilariously/sweetly innocent/naive in its specificity and certainty, like only newbies' first "design document" could be.
I have issues with this 'longform word doc' format of design documentation in general. It's tedious, no-one bothers to do more than skim read it, it conveys method but not intentions, etc.
Earlier quoted context omitted.
I have issues with this 'longform word doc' format of design documentation in general. It's tedious, no-one bothers to do more than skim read it, it conveys method but not intentions, etc.
I assume this was a class assignment or project, wasn't it? The format was probably dictated by DigiPen instructors.
Coding guidelines - Precompute whenever even remotely possible. - Measures must be taken to prevent copy paste errors. - Measures must be taken to prevent copy paste errors. - The STL is evil (most of the time). - Unnecessarily virtual functions should be rewritten to remove virtual requirements. - Sloppy code must be marked for recoding later. - Unreadable code earns you a free punch in the face. - Measures must be…