IB Year 1 Higher Level Computer Science
Wednesday 18 September 2024 - Block 1
← previous note | most current note | next note →Daily Note
Hello!
Today we will review your survey feedback from our LMS:
Keep Doing:
- In-depth explanations, programming assignments, quizzes, and code examples.
- User-friendly navigation, organization, and clean UI.
- Structured content with clear headings and images.
- Focus on Python programming and encourage game development.
Stop Doing:
- Long, unnecessary writings that can overwhelm users.
- Avoid opening multiple sections or sidebars simultaneously.
- Make uploading code and navigating within lessons simpler.
Start Doing:
- Add short lessons on different programming languages.
- Bold or highlight key information for clarity.
- More coding tasks with actual code writing.
- Provide video examples and direct integration with tools like VSCode.
- Enable messaging for private feedback and support.
- Improve connection between LMS and Google Classroom.
- Introduce courses on lesser-known programming languages.
I will review your homework.
Please complete this feedback about our classroom LMS
We will learn about dictionaries
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.
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.