Solving Complex Problems Through Programming
Monday 12 September 2022 - Block 7
← previous note | most current note | next note →Daily Note
Welcome back. I missed you at the end of last week.
We will learn about jamboard
We will learn about the standard library in Python:
- We will start with a brief description of the standard library
- We will look at a long list of all the different python modules included in the standard library
- We will use the statistics module, which is helpful
- You will then look and practice a tour of the standard library in Python
- You will continue by looking and practicing part 2 of the standard library
- We will learn how to install other libraries using pip.
We will then take a bit of a break, and move onto iteration and loops.
- We will watch a video about iteration
- We will learn and practive three different types of iteration
- We will learn about breakpoints in vscode
- We will observe how variables change as we step through our program
We will spend the rest of class working on objective 5.
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.
Statement of Inquiry
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.
Reminders & routines:
IF (this_block == first_block_day) {
read_daily_bulletin;
}
IF (today == Friday) {
computing_careers
}
As I am taking attendance:
- 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.