help queue

Class wiki

Github

Class library

Class syllabus

All notes for this course

Solving Complex Problems Through Programming

Monday 5 October 2020 - Block 5, Room C152
← previous note | most current note | next note →
 

Daily Note

Our plan for the day:

  1. We will use a new system to collaboratively code http://develop.computersciencelearning.org/
     
  2. We will learn about dictionaries
     
  3. Read this: https://computersciencewiki.org/index.php/Computer_modeling
     
    1. watch this: https://www.youtube.com/watch?v=w0eRkhR1z6A
    2. Read the specs here: https://starwars.fandom.com/wiki/TIE/LN_starfighter
    3. Read the specs here: https://starwars.fandom.com/wiki/T-65B_X-wing_starfighter
       
  4. Please construct a model - I advise you to aim small to get started.
     
    1. I have identified important features of whatever events I hope to represent.
    2. I identified rules that control those features and their relationships.
    3. I have expressed those rules with math.
    4. I have adjusted for how likely each factor is.

Homework

  1. All homework is listed in our Google classroom under the topic "Homework".

 

A little less comfortable

Content

Programs must solve the problem they were create to solve. We can worry about how effieciently or elegantly they solve the problem later on; not right now. The content of a program entails input, processing and output. All three of these elements must be clearly observable. A key question you will be asked (and you should ask yourself) is: to what extent does your code implement the features required by the specification?  

Process

Within the process, we are looking at six guiding questions: 

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?
  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?

Product

As opposed to content, this section we focus on how well you solved the problem. A key question here is to what extent is your code free of bugs?

 

A little more comfortable

Content

Programs must solve the problem they were create to solve. You should ask yourself "Am I solving this elegantly?". The content of a program entails input, processing and output. All three of these elements must be clearly observable, and we must see evidence of sanitizing input and raising exceptions.  A key question you will be asked (and you should ask yourself) is: to what extent does your code implement the features required by the specification?  

Process

Within the process, we are looking at six guiding questions: 

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?
  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?

For those more comfortable programming, we expect succinct, secure and effecient problem solving. 

Product

As opposed to content, this section we focus on how well you solved the problem. A key question here is to what extent is your code free of bugs? The real difference here is the complexity of the problem you have chosen to solve and how well you solved it. 

Our Big idea

The big idea for today is Programming.

The essential questions for this topic are:

How do we plan, write, execute, and test instructions a computer can understand and process?

It takes time to explore and really understand a big idea. If you want to
learn more about programming (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.



Tags

 

Reminders & routines:

Reminders: 

  1. IF today ==  testing_day_for_me:
         remember to go get tested!

    IF today == first_class_of_day:
        read_daily_bulletin

    IF today == Friday:
        current_event_protocol()

  2. Always start every class by reviewing our daily notes
     
  3. 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

 

 

Our learning

This is a beta feature. Please let me know if you have any feedback.

Please click here to reflect on our learning for today's class.