Designing Solutions Through Programming
Friday 19 February 2021 - Block 2
← previous note | most current note | next note →Daily Note
Our plan for the day
- I am working on a new tool to help you see how long until you get help. please use it today: https://help.computersciencewiki.org/
- Please review asking for help
- Please remember, here is a video about debugging and how to debug. The code snippet we use is here.
- Some of you will need help. Please help each other, and ask me a question if you need help!
- We will work on section C
Homework
- All homework is listed in our Google classroom under the topic "Homework".
A little less comfortable
Content
You should have evidence your solution works. Evidence must come from anyone other than you.
Process
The key thing here is the quality of your evidence. Good evidence is specific and detailed. Here's an example of some bad evidence:
You program worked, cool! <-- the reason this evidence is poor is because it isn't specific and detailed.
Perhaps a better example might look like this:
I used your program to find a guitar amplifier. I didn't understand what made one amplifier better than another, and It was cool to use the quiz to help me find a good model. I wish there was more information about the amplifiers, and maybe a sound clip from different amplifiers. The user interface is also easy to use, I liked the slider feature so I could see my progress. I wish I could read reviews from people who used the amplifier so I could get an idea from actual customers. <-- this is good evidence because it is very detailed and specific.
Product
Your evaluation should:
- have detailed and relevant testing methods, which generate data, to measure the success of the solution
- critically evaluate the success of the solution against the design specification based on authentic product test
- explain how the solution could be improved
- explain the impact of the product on the client/target audience.
A little more comfortable
Content
You should have evidence your solution works. Evidence must come from anyone other than you. One of the key differences is to have many in-depth interviews with many people (2 or 3 people), which indicate you have really tried to deeply understand your clients point of view and perspective.
Process
The key thing here is the quality of your evidence. Good evidence is very specific and highly detailed. Here's an example of some bad evidence:
You program worked, cool! <-- the reason this evidence is poor is because it isn't specific and detailed.
Perhaps a better example might look like this:
I used your program to find a guitar amplifier. I didn't understand what made one amplifier better than another, and It was cool to use the quiz to help me find a good model. I wish there was more information about the amplifiers, and maybe a sound clip from different amplifiers. The user interface is also easy to use, I liked the slider feature so I could see my progress. I wish I could read reviews from people who used the amplifier so I could get an idea from actual customers. <-- this is good evidence because it is very detailed and specific.
If you want to reach higher, please watch people use your program without saying anything. Really listen and look as they are using your program. Ask open-ended questions such as "What would be most helpful to you?" and "How does this compare to other webistes you have used? What would make it better? "
Product
Your evaluation should:
- have detailed and relevant testing methods, which generate data, to measure the success of the solution
- critically evaluate the success of the solution against the design specification based on authentic product test
- VERY SPECIFICALLY explain how the solution could be improved
- explain the impact of the product on the client/target audience.
Our Big idea
The big idea for today is Design: Evaluation.
The essential questions for this topic are:
How do you know your design has solved the problem you set out to solve?
It takes time to explore and really understand a big idea. If you want to
learn more about
design: evaluation (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 (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:
- For students who are physically at ASW: Please check now: am I connected to the American School of Warsaw wireless network
- Please check now: is visual studio code working from my programming folder?
To remember:
- 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.
- You can access a web-based view of your database by clicking this link.
- Please be aware of course videos to help you understand our content.
If you want to meet with me:
- I am free blocks 2,6 and 8
- Send an email to make an appointment
- Don't ask me in person! Always send an email
- Ask me a question on our discussion forum.
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.