Designing Solutions Through Programming

Thursday 10 February 2022 - Block 2
← previous note | most current note | next note →
 

Daily Note

  1. Please review how to ask for technical help
  2. Please note I made a small change to our help system. You can click on your help question to see any replies I wrote.
  3. Please use our  "ask for help system". The reason we are learning this is because many of you need a bit of help and this systems helps me keep track of who needs help.
  4. We will work section C. Please take a break half way through class for 7 minutes. Please do your best to help each other.

 

A little less comfortable

Content

Your plan should clear enough to be followed by someone else. Your plan should be realistic. Your plan should be detailed enough so it is very clear how your product will be developed. 

Process

As you are working, you should be strive to do your best work. You should work to create something high quality. Beware of working very quickly. You should follow your plan and constantly reflect how you are using your time. An important part of process is asking for help. Make sure you ask for help as soon as you think might need it. 

Product

Your product reflects your process. You should feel proud of your work! We get into this in section D, Evaluation, but at this point you should see a clear connection between your product and the problem you are solving. 

A little more comfortable

Content

Your plan should clear enough to be followed by someone else. Your plan should be realistic. Your plan should be detailed enough so it is very clear how your product will be developed. At a higher level, plans often include when a task will be completed. For example you might know a certain task will take 1.5 hours, but when exactly would you do this work? With this information, you can make very well designed plans.  This time works very well when you have multiple members.

Process

As you are working, you should be strive to do your best work. You should work to create something high quality. Beware of working very quickly. You should follow your plan and constantly reflect how you are using your time. An important part of process is asking for help. Make sure you ask for help as soon as you think might need it. At a higher level, we look for well-named variables, clean-code practices and clear logic in a program.

Product

Your product reflects your process. You should feel proud of your work! We get into this in section D, Evaluation, but at this point you should see a clear connection between your product and the problem you are solving. In a higher level, we see that you have followed your plan carefully, noted any reasons for change, and created a complex, interesting product. 

Our Big idea

The big idea for today is Design: Creating the Solution.

The essential questions for this topic are:

How do we plan and create a high-quality solution?

It takes time to explore and really understand a big idea. If you want to
learn more about design: creating the solution (which is connected to today's daily note), please click here .

We are learning this because as a designers must understand scientific and technical innovation. Designers use systems, models, methods, and processes to solve problems.



Reminders & routines:

IF (today ==  testing_day_for_me) {
     remember to go get tested!;
}

IF (this_block == first_block_day) {
     read_daily_bulletin;
}

IF (today == Friday) {
     current_event_activity();
}

As I am taking attendance:

  1. For students who are physically at ASW: Please check now: am I connected to the American School of Warsaw wireless network
  2. Please check now: is visual studio code working from my programming folder?

To remember: 

  1. All the files you need for this course can be found at this link. Please pay attention to the time the file was last updated. 
  2. You can access a web-based view of your database by clicking this link.
  3. Please be aware of course videos to help you understand our content.