Differences

This shows you the differences between two versions of the page.

--- 184_notes:comp_process [2022/04/20 15:46] – [Commenting] woodsna1
+++ 184_notes:comp_process [2022/04/20 15:55] (current) – [Logistics] woodsna1
@@ Line 28: / Line 28: @@
 </code>
 ===== Predictions and Evaluations =====
+Before you start coding, it is important to define goals, predict what the code's output should look like, and draw any necessary representations. These steps will guide your team through the project, and prepare you to evaluate your solution for accuracy.
+If the code is intended to create a visual, think through what that visual will look like and draw it out. It often helps to run the code once without editing it, to see what "scene" your team is provided with. Figure out what the changes you need to make will add to the scene, and draw out what that should look like.
+When your team has completed the program, assess how closely it matches your predictions. Are there errors in your prediction? In the coded model? Think through ways that the coded model could more closely reflect reality, and any improvements that your team can add.
 ===== Logistics =====
+An easy way to get very lost as a group is having each person looking at a separate computer screen with their own version of the code. Instead, pick a single person to type the code with input from all other group members. Choosing a coder with less programming experience will make sure that your entire group stays together. If you are a CS/CMSE/Computer Engineering major, you probably should not be coding.
+In class, one of the best ways to keep everybody on the same page is starting a zoom meeting, having each team member log in on their own device, and having the coder share their screen with the program up. Then you'll each be able to see what's going on without huddling around one small screen.