Software approach, Top down design

One way of coding is to simply have a rough idea of what you want to do and then start typing a way to produce one huge source file.

This is a very bad idea.

The resulting code is likely to have many issues with it that include

• Poorly documented code, so very hard to maintain and update
• 'Spaghetti code' - which means a tangled mess of jumps and loops all over the code, very hard for someone to understand. Even by the original coder a few days later!
• Duplication of code, so wasting memory and running speed
• Very hard to develop by more than one person as there is only one file
• Very hard to debug - the file either works or it doesn't

Here are more issues, but hopefully the list shows that it is best to have a methodical, professional approach to coding which this mini-web will cover

Systems Thinking

What comes to your mind when you hear the word, system? What is a system? How does it work?

A system is multiple things working together to accomplish a goal. A small change in a subsystem can affect everything. It works by one thing helping another and then another or pieces from each thing coming together. Examples, a factory, a company, organization system, computer programming, school, kitchen

Name Card - Mission Reflection

1) Why is each step required?
Empathize was needed so that I could know what the user wanted from the namecard.
Define was needed so that I could give myself a theme as a starting point for ideas of my namecard and know what challenge I should focus on.
Ideate was need so that I could sort out my ideas and pinpoint a final one that I wanted to make.
Prototype was needed so that I could actually make the product.
Test was needed so that I could get final feedback on my product and know what I could improve as a whole.

2) I learnt that what I was imagining for a name card was different from what the user wanted so I had to change my thinking to his and her thinking and I learnt that I needed to keep asking for feedback so that I could get exactly what the user wanted.

3) My name card is disruptive because it does not show the boring things that people want but the interesting details that the user actually wants.

Name Card - Prototype/Test

Feedback:

Kenneth: It looks cool. I like the font of your name and the hummingbird.
Delaney: It looks really good.

Name Card - Ideate

Ideate Feedback:

Delaney: It's good.
Kenneth: It's looks great.

Name Card - Define

Theme: Water and Nature

Challenge: Expressing the horoscope and what it means

Name Card - Empathize

I am making a name card for Kenneth and Delaney.
My name card will have my information.

Favorite color?
Favorite sport?
How old are we?
Dream vacation spot?
Name?
Favorite activity?
Favorite Animal?
Favorite band?
Horoscope?
Favorite movie?
Which of the elements are you?
Spirit animal?
Favorite book?


Digging Deeper:
Name?
Vacation Spot?
Color?
Favorite band?
Horoscope?
Which of the elements are you?
Spirit animal?