IB Year 1 Higher Level Computer Science
Tuesday 27 September 2022 - Block 4, Room C152
← previous note | most current note | next note →Daily Note
Hello,
I'd like to hack through objective 7 and 8.
I'd also like to have a programming quiz covering objectives 1 through 9, let's choose a date.
Let’s get signed up for github
- Please create an account at github
- Please use a personal email address
- Please DO NOT EVER use any personally identifiable information
- Please ensure you are fully registered with github, confirm your email
- Please email bmackenty@aswarsaw.org your github username
- Open terminal and type: git config --global user.email "email@example.com"
- Please use your email that you registered with git.
- Please use your email that you registered with git.
- Again, in terminal, please type: git config --global user.name “your first name only"
- Please close all folders in visual studio code. There are 2 ways to do this:
- Push command-K and then push F (don’t push command-f)
- Click on file and then click on close folder
- Please watch this video
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.
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.