A forced rehashing of previous missed opportunities, enhanced with fruitful discord participation and the asking of questions to fill in gaps.

Do note, the productive way to go about this project involves taking the following steps:

• starting early
• reading any relevant project page(s)
• asking questions regarding things you do not know, are not clear on, or are confused about
  • fruitful interaction is meaningful back and forths on the discord, not simply “I don't know, give me the answer”. Use these resources to help you clarify misunderstandings and enable you to make progress on the selected items.
• as information, concepts, processes become clear, that is something you can contribute to the project documentation (as appropriate, so you can better remember)

If you start too late, and do not ask questions, and do not have enough time and don't know what is going on, you are not doing the project correctly.

I do plan on being rather stringent on compliance with the activities present on this project. The aim is to attain a whole class interaction and participation, ideally what should be experienced each and every week.

Your task is to revisit a prior project, and current letter division puzzle, and over the course of at least FOUR (4) days, be suitably active and interactive on discord, asking questions and providing informative responses to queries.

Any editable documentation should also be reviewed, polished, and updated, to improve its value (make it what you wish it was when you started).

For project-related communications, you are to use the class channel. For the letter divisions, use puzzle-y-tastic.

Your submission is to be (suitably identified) corrected project files for the chosen project, along with indications of which puzzle you chose to associate with this project (those files will be submitted as usual in relation to the puzzle in question).

To be successful in this project, the following criteria (or their equivalent) must be met:

• Project must be submit on time, by the deadline.
  • Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
• All code must run cleanly (no warnings or errors)
  • all requested functionality must conform to stated requirements (either on this document or in a comment banner in source code files themselves).
• Executed programs must display in a manner similar to provided output
  • output formatted, where applicable, must match that of project requirements
• Processing must be correct based on input given and output requested
• Output, if applicable, must be correct based on values input
• Code must be nicely and consistently indented
• Code must be consistently written, to strive for readability from having a consistent style throughout
• Code must be commented
  • Any “to be implemented” comments MUST be removed
    • these “to be implemented” comments, if still present at evaluation time, will result in points being deducted.
    • Sufficient comments explaining the point of provided logic MUST be present
• Track/version the source code in your lab46 semester repository
• Submit a copy of your source code to me using the submit tool

Let's say you have completed work on the project, and are ready to submit, you would do the following:

lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN

You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.

I'll be evaluating the project based on the following criteria:

156:skbD:final tally of results (156/156)
*:skbD:discord interaction related to chosen project, day 1 [13/13]
*:skbD:discord interaction related to chosen project, day 2 [13/13]
*:skbD:discord interaction related to chosen project, day 3 [13/13]
*:skbD:discord interaction related to chosen project, day 4 [13/13]
*:skbD:discord interaction related to current puzzle, day 1 [13/13]
*:skbD:discord interaction related to current puzzle, day 2 [13/13]
*:skbD:discord interaction related to current puzzle, day 3 [13/13]
*:skbD:discord interaction related to current puzzle, day 4 [13/13]
*:skbD:chosen project files submitted [13/13]
*:skbD:chosen project files commit to semester repository [13/13]
*:skbD:current puzzle identified in some submitted file [13/13]
*:skbD:current puzzle files commit to semester repository [13/13]

• Solutions not abiding by spirit of project will be subject to a 50% overall deduction
• Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
• Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
• Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction
• Individuals who have not participated at least 50% will be subject to a 50% overall deduction.