help queue

Class wiki

Github

Class library

Class syllabus

All notes for this course

Designing Solutions Through Programming

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

 

The plan for our class:

  1. Please read and follow these reminders:
     
    1. Always start every class by reviewing our daily notes
    2. 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?
    3. This short video will help you remember how to use moodle
       
  2. We will quickly review:
    1.  IDE (integrated development environment)
      1. IDE's have line numbers to help you organize your code and discuss code with friends
      2. Syntax highlighting is a way of coloring different reserved words so they are easier to read
      3. Syntax highlighting also helps you identify errors
      4. Autocomplete will help you by filling in functions, variables, and other identified names, so you don't have to type the whole thing (and avoid misspelling)
    2. HTML
      1. HTML element
        1. opening tag
        2. closing tag
        3. content
        4. attributes
      2. block vs in-line tags
      3. anchor tags
      4. image tags
         
  3. We will carefully review:
    1. Forms and input types
      1. We quickly remember input-process-output
      2. You will understand the structure of an HTML form
      3. You will understand the required attributes of an HTML form
      4. You will understand what happens after a form has been submitted
      5. You will understand how forms pass data from one HTML page to another page.
      6. You will understand input types
        1. The HTML  element is used to create interactive controls for web-based forms in order to accept data from the user; a wide variety of types of input data and control widgets are available, depending on the device and user agent. The  element is one of the most powerful and complex in all of HTML due to the sheer number of combinations of input types and attributes (source). 
      7. You will learn and practice with text, password, textarea

         
    2. We will review your homework
       
    3. We are going to start learning about bootstrap, and building a school store. 
    4. We will look at bootstrap documentation
       
    5. We will discuss an important idea: look for a component, copy and modify the component. 
       
    6. You will build a simple page using bootstrap.
       
  4. We will review our work
     
  5. 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:

 

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.