Designing Solutions Through Programming

Wednesday 16 September 2020 - Block 1, Room C152
← previous note | most current note | next note →
 

Daily Note

Learning to code & accepting input

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();
}

  1. Please read and follow these reminders:
     
    1. 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?
    2. This short video will help you remember how to use moodle
       
    3. We will discuss an important idea:
       
      1. look for a component on bootstrap documentation you would want on your website
      2. copy the code into visual studio code
      3. modify the code so it fits your needs
      4. save and upload the code
      5. verify the code works the way you want it to function
         
    4. We are going to keep building our store: 
       
      1. We will use this file as a starting place: You will build a simple page using bootstrap
      2. If you would like a nice clean empty template with a navbar and footer, please use this file
         
      3. Today we will make sure we have a working front page 
         
        1. Your table-partner will check: 
          1. Does my partner have 6 different products listed?
          2. Does my partner have a navbar which makes sense (is it related to the store)?
          3. Does my partner have a footer which makes sense (unique to my store)? 
      4. We will then work on a login system, so your customers (and you) can login. 
        1. You will create a new file named store_login.php
        2. You will copy this file and paste it into your IDE
        3. You will save this file and confirm it has uploaded to our webserver
        4. You will look at this code and predict what it does, using a think-pair-share model
        5. You will edit this code so it looks the way you want it to look
      5. If we have time, we will work on the registration code, for new customers.
        1. You will create a new file named store_register.php
        2. You will copy this file and paste it into you IDE
        3. You will save this file and confirm it has uploaded to our webserver
        4. You will look at this code and predict what it does, using a think-pair-share model
        5. You will edit this code so it looks the way you want it to look
           
  2. We will review our work
     
  3. Homework is always posted on google classroom (and only google classroom)

 

 

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: