Designing Solutions Through Programming
Tuesday 8 November 2022 - Block 2
← previous note | most current note | next note →A little less comfortable
Content
You should design and construct a design brief, where you demonstrate that you really understand the problem you are trying to solve. Please remember: the better you understand the problem, the better your solution will be.
Process
The key thing here is the quality and depth of your research. Good research is specific and detailed. Here's an example of some bad research:
I asked a friend if my idea was good. <-- the reason this evidence is poor is because there isn't alot of it, there is no evidence you have actually really thought about this. You should also have multiple sources of research, never just one. I don't see evidence you really understand the problem.
Perhaps a better example might look like this:
I reviewed 4 different websites that solved the exact problem I was trying to solve. Each one had a very different interface and the way they displayed results was different. I started to understand that the way I ask questions and show results influenced how people framed the answer. For example, on the first website, I noticed there were....<-- this is good research because it is very detailed and specific.
Product
Your research should:
- have multiple sources (between 3 and 5)
- have detailed analysis (what did you learn, and what was different between the two research sources).
- how did your research inform your product?
A little more comfortable
Content
You should design and construct a design brief, where you demonstrate that you really understand the problem you are trying to solve. Please remember: the better you understand the problem, the better your solution will be. Your design brief should demonstrate you have ANALYZED your problem through your research.
Process
The key thing here is the quality and depth of your research. Good research is specific and detailed. Great research directly addresses the problem you are trying to solve. In addition to everything from the "less comfortable with computer science" you should look for primary sources, perhaps even interviewing people who have tried to solve your problem.
Product
Your research should:
- have multiple, high quality sources (between 5 and 7)
- have a highly detailed analysis about specific features in others solutions (what did you learn, and what was different between the two research sources).
- clearly link the research to your problem.
Our Big idea
The big idea for today is Design: Understanding a Problem.
The essential questions for this topic are:
How well do you really understand the problem you are trying to solve?
It takes time to explore and really understand a big idea. If you want to
learn more about
design: understanding a problem (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) {
careers_in_computing()
}
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.
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.