haas:fall2016:common:submitblurb
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:fall2016:common:submitblurb [2016/09/17 20:01] – wedge | haas:fall2016:common:submitblurb [2021/09/08 17:12] (current) – wedge | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| * Early submissions will earn 1 bonus point per full day in advance of the deadline. | * Early submissions will earn 1 bonus point per full day in advance of the deadline. | ||
| * Bonus eligibility requires an honest attempt at performing the project (no blank efforts accepted) | * Bonus eligibility requires an honest attempt at performing the project (no blank efforts accepted) | ||
| - | * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline. | + | * Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline. |
| - | * To clarify: if a project is due on Wednesday (before its end), it would then be 25% off on Thursday, | + | * To clarify: if a project is due on Wednesday (before its end), it would then be 33% off on Thursday, |
| * Certain projects may not have a late grace period, and the due date is the absolute end of things. | * Certain projects may not have a late grace period, and the due date is the absolute end of things. | ||
| * all requested functions must be implemented in the related library | * all requested functions must be implemented in the related library | ||
| Line 42: | Line 42: | ||
| * Any "to be implemented" | * Any "to be implemented" | ||
| * these "to be implemented" | * these "to be implemented" | ||
| - | * Commenting will be rated on the following scale (worth | + | * Commenting will be rated on the following scale (worth |
| - | * 4/4: Not only aesthetically pleasing, but also adequately explains the WHY behind what you are doing | + | * 3/3: Aesthetically pleasing (comments aligned or generally not distracting), |
| - | * 3/4: Aesthetically pleasing (comments aligned or generally not distracting), | + | * 2/3: Mostly consistent, some distractions or gaps in comments (not explaining important things) |
| - | * 2/4: Mostly consistent, some distractions or gaps in comments (not explaining important things) | + | * 1/3: Light commenting effort, not much time or energy appears to have been put in. |
| - | * 1/4: Light commenting effort, not much time or energy appears to have been put in. | + | * 0/3: No original comments |
| - | * 0/4: No original comments | + | |
| * should I deserve nice things, my terminal is usually 90 characters wide. So if you'd like to format your code not to exceed 90 character wide terminals (and avoid line wrapping comments), at least as reasonably as possible, those are two sure-fire ways of making a good impression on me with respect to code presentation and comments. | * should I deserve nice things, my terminal is usually 90 characters wide. So if you'd like to format your code not to exceed 90 character wide terminals (and avoid line wrapping comments), at least as reasonably as possible, those are two sure-fire ways of making a good impression on me with respect to code presentation and comments. | ||
| * Sufficient comments explaining the point of provided logic **MUST** be present | * Sufficient comments explaining the point of provided logic **MUST** be present | ||
| * Code must be appropriately modified | * Code must be appropriately modified | ||
| * Appropriate modifications will be rated on the following scale (worth 3 total points): | * Appropriate modifications will be rated on the following scale (worth 3 total points): | ||
| - | * 3/3: Complete attention to detail, original-looking implementation | + | * 3/3: Complete attention to detail, original-looking implementation- also is not unnecessarily reinventing existing functionality |
| - | * 2/3: Lacking some details (like variable initializations), | + | * 2/3: Lacking some details (like variable initializations), |
| * 1/3: Incomplete implementation (typically lacking some obvious details/ | * 1/3: Incomplete implementation (typically lacking some obvious details/ | ||
| * 0/3: Incomplete implementation to the point of non-functionality (or was not started at all) | * 0/3: Incomplete implementation to the point of non-functionality (or was not started at all) | ||
| Line 66: | Line 65: | ||
| * 1/3: Minimal error checking, code is fragile (code may not work in full accordance with project requirements) | * 1/3: Minimal error checking, code is fragile (code may not work in full accordance with project requirements) | ||
| * 0/3: No error checking (code likely does not work in accordance with project requirements) | * 0/3: No error checking (code likely does not work in accordance with project requirements) | ||
| - | * Any and all non-void functions written must have, **at most**, | + | * Any and all non-void functions written must have exactly |
| * points will be lost for solutions containing multiple return statements in a function. | * points will be lost for solutions containing multiple return statements in a function. | ||
| * Absolutely, positively **NO** (as in **ZERO**) use of **goto** statements. | * Absolutely, positively **NO** (as in **ZERO**) use of **goto** statements. | ||
| * points will most definitely be lest for solutions employing such things. | * points will most definitely be lest for solutions employing such things. | ||
| + | * No custom global variables! The header files provide all you need. | ||
| + | * Do NOT edit the header files. | ||
| * Track/ | * Track/ | ||
| * Filling out any submit-time questionnaires | * Filling out any submit-time questionnaires | ||
| * Submit a copy of your source code to me using the **submit** tool (**make submit** will do this) by the deadline. | * Submit a copy of your source code to me using the **submit** tool (**make submit** will do this) by the deadline. | ||
haas/fall2016/common/submitblurb.1474142465.txt.gz · Last modified: 2016/09/17 20:01 by wedge
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
