Designing Solutions Through Programming

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

Daily Note

  1. We will review how to ask for help correctly. Use this document to help you remember
     
  2. We will review our understanding about github
     
  3. I try to avoid changing files, but sometimes I notice little errors or make improvements:
     
    1. Please replace your current store_navbar.php with the file linked here: store_navbar.php
    2. Please repalce your current store_setup.php with the file linked here: store_setup.php
    3. Please create a new file, store_search_results.php
       
  4. Please request store_setup.php in a web browser. IF you have any errors THEN please fix them. 
     
  5. We are going to review the three parts of using a database with PHP: 
    1. We will review databases:
      1. I can describe a database
      2. I can describe why people use database
      3. I can use a web-based tool to see my database by clicking this link.
    2. connecting to the database
    3. query the database 
    4. do something with the results
    5. Please be aware of course videos to help you understand our content.
       
  6. We will understand how search works
     
    1. We will look for the three parts of "using a database with PHP"  in the file store_search_results.php
    2. We will PREDICT how this code works

       
  7. 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:

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.