problemsolving   1440

« earlier    

If you want to tackle big problems, try thinking like a bee |
Honey bees can show us the power to be found in thinking small, says beekeeper Marianne Gee.
Creativity  problemsolving  ted 
19 days ago by jorgebarba
How to think like a programmer — lessons in problem solving
Good article to show outsiders the benefits and methods to "think like a programmer".

1. Understand.
2. Plan.
3. Divide.
4. Stuck?
4a. Debug.
4b. Reassess.
4c. Research.
5. Practice.
thinking  programming  problemsolving 
22 days ago by drmeme
The Systems Thinker – A Lifetime of Systems Thinking - The Systems Thinker
Improving the performance of the parts of a system taken separately will necessarily improve the performance of the whole. False. In fact, it can destroy an organization, as is apparent in an example I have used ad nauseum: Installing a Rolls Royce engine in a Hyundai can make it inoperable.
design  engineering  systems  innovation  philosophy  problemsolving  management 
24 days ago by whip_lash
One Giant Step for a Chess-Playing Machine - The New York Times
As machines become ever faster, and humans stay put with their neurons running at sluggish millisecond time scales, another day will follow when we can no longer keep up. The dawn of human insight may quickly turn to dusk.
deeplearning  chess  artificialintelligence  humanity  problemsolving  future  singularity 
7 weeks ago by vanevery
How Architecture Teaches Kids Patience, Problem-Solving - CityLab
"Through the organization Architecture for Children, Hong Kong architect Vicky Chan has taught urban design and planning to thousands of kids. Here’s why."

"Why should schools start teaching design to young kids?

What does urban planning have to do with education? Whether you’re a kid or an adult, I think the biggest challenge is often figuring out how to sift through information, deciding what information to use, and learning to make compromises. You have to understand that the best argument isn’t the loudest one. It has to be rational.

For example, we had a group of students decide to build a hotel at the top of the hill near the school, connected by a tram, because the location afforded excellent views. That’s good reasoning. But the next week, they realized that construction would be difficult, and decided to raze the hill! And I told them: “Wait, you had agreed last week that the hill was good for the hotel.” So it’s about teaching the students how to rationalize the process and to keep progressing from your original thinking to taking the next step.

Even if these students don’t end up going into the design field, these thinking skills are very important.

On the sustainability front, we also have to start teaching this from a young age. A lot of students think putting their plastic bottles in the recycling bin is what sustainability means. But there’s a broader way to think about it, [such as], how do you think about transportation to reduce car use? These are very broad and complex topics, and we have to simplify them for the students to get across the message that to make the future of cities more sustainable, you really have to think about a lot of different factors.

The students also learn how to draw as a form of expression. Nowadays, we’re surrounded by iPhones and iPads, but some students lack even simple mechanical skills. I think it’s very important to teach handicraft as a way to solve a technological problem.

With design, no solution is 100-percent right or wrong. It’s not like solving a mathematical problem. In sport, you can teach team spirit, but at the end of the day, it’s a competition and it boils down to winning and losing. But in design, there is no absolute answer, and it’s very much like in real life.

How might your students apply what they learn in their own communities?

I recently showed the students a photo of walled buildings [large buildings arranged in such a way that they form a wall, blocking an area’s air flow]. I asked the students whether they saw a problem with the wall effect. They didn’t see a problem; they haven’t yet been told what is good and what is bad. In fact, they might even live in walled buildings. But if we can teach them from an early age that there are better ways to build and construct, then perhaps flawed proposals will less easily find widespread support.

Here’s another example. In Kwun Tong, there’s Kwun Tong Road, which has multiple lanes and is very wide. When I used to live nearby, I thought, there’s the metro running overhead, so does the road really need to be this wide? But this question has to come from a certain doubt, a doubting of whether there’s a problem with the status quo. Sometimes after seeing the same thing day in, day out, you come to accept that it is right and just the way things are done.

But if you think more carefully, maybe you realize that Kwun Tong Road doesn’t have to be this wide, and that having more trees would be better. It’s about having a critical mindset. This is what we want to teach the students.

What do we lose by not teaching (and learning) design from an early age?

From a design perspective, I think you miss out on learning how to analyze a question. In math or science class, you learn to solve a problem formulaically. But you may not learn how to analyze the problem. Analysis is very important for students. In the working world, I sometimes come across very stubborn adults. It’s not that they’re not skillful enough, but that they can’t get to the core of a question and deconstruct it to find the different levels of reasoning. So I think design teaches kids how to creatively think out the reasoning.

The other thing is learning how to see opportunities. Once you discover a problem, you learn to see opportunities. Problems present opportunities. But if you can’t see the problem, then you can’t see the opportunity.

Recently, people have been debating different urban planning proposals [in Hong Kong], such as the East Lantau Metropolis [a $60 billion development plan to build a series of artificial islands in the sea]. The debates were very heated. But even after hearing the debates, I don’t fully buy into any of the proposals because at no point did anyone fully present all the pros and cons. I think if we can teach kids this from an early age, and they can as adults present ideas simply, we won’t have as many misunderstandings or misguided suggestions.

You also teach patience through architecture and design. In the first five classes, we were all planning and drawing. The students were getting bored and impatient. They were asking me, “When can we start building?” But then we started building, and no one knew how to begin. And I told them: “Didn’t we just spend five classes planning?” So we’re teaching them how important each step of the planning stage is.

What have you learned from teaching?

Once, I had some students build models of bridges. I went around and asked them what the Tsing Ma Bridge looked like to them. One student told me that it looked like a smile. I thought this was brilliant. It helped me see the bridge as a very simple message about a city’s smile. It showed me the importance of using imagination and creativity to simplify a concept so that even kids can understand it.

We architects spend a lot of time thinking about complex ideas, but sometimes you just need something simple and pure."
architecture  education  cv  teaching  making  howwelearn  vickychan  2018  design  howwethink  problemsolving  patience  howwteach  learning  schools 
8 weeks ago by robertogreco
Why we suck at “solving wicked problems” | More Beyond
"Problems: Wicked, complex, intractable or adaptive  … whatever we choose to call them, we seem to suck at solving them and we often get profoundly overwhelmed and stuck."
IFTTT  Pocket  economics  psychology  bias  society  problemsolving 
8 weeks ago by garrettc

« earlier    

related tags

2017  2018  2018outlook  abstraction  adolescence  advice  agency  agile  agiledevelopment  akia  alecnevala-lee  algebra  algorithms  america  analysis  anandgiridharadas  andréspicer  animals  answer  approach  architecture  art  artificialintelligence  basecamp  bathroom  bearings  bestpractices  bias  billburnett  birds  book  books  bullshit  business  c++  calculus  career  cartoon  chess  children  christophermckenna  classroom  clojure  cognition  collaboration  collaborative  colleges  comments  communication  competenceporn  complexity  computerscience  computing  consulting  control  corvids  courses  creative  creativity  crimescene  criticalthinking  criticism  crossdisciplinary  culture  curiosity  cv  daveevans  davidedgerton  davidhounshell  davidkelly  davidmowery  deeplearning  deepwork  deschooling  design  designimperialism  designthinking  development  discussion  disss  diversity  economics  education  elite  elizabethpoppberman  empathy  emptiness  engine  engineering  entrepreneurship  epistemology  esaleninstitute  essay  ethnography  europe  exposure  facebook  facilitation  fransdewaal  free  freedom  functionalprogramming  future  game  garethkay  georgeorwell  gettier  hackernews  hassoplattner  hbr  herbertsimon  highered  highereducation  highschool  history  holland  hotel  hotels  howto  howwelearn  howweteach  howwethink  howwteach  hucksterism  humanitariandesign  humanity  hype  idea  ideas  ideation  ideo  ifttt  imagination  innovation  inspiration  intelligence  interesting  interview  interviewing  jamesstigler  jimjones  jison  johnhennessey  k12  karaswisher  kateantonova  lawrencebusch  lcproject  leadership  leanthinking  learn  learning  leevinsel  liberalarts  lifehacker  machinelearning  maintenance  making  management  margaretbrindle  marianamazzucato  marketing  math  mathematics  maths  memorization  metalwork  methodology  models  mtbsuspension  multidisciplinary  multispecies  natashajen  nathanielcomfort  nathanrosenberg  netherlands  newage  notes  nthanemery  openideo  openstudioproject  parrots  patience  patrickmccray  patterns  people  petermiller  peterstearns  philipmirowski  philosophy  playpump  pocket  podcast  post-its  presentation  presentations  problem-solving  problem  problems  process  productivity  products  programming  psychologicalsafety  psychology  publicschools  purpose  puzzle  question  questionandanswer  rafranzdavis  reading  recode  reference  reflectivelistening  relationships  repair  research  richhickey  robertmckim  rootcause  scale  schooliness  schooling  schools  science  self-promotion  self-recognition  sfsh  shafts  simplicity  singularity  singularityuniversity  skills  snakeoil  society  software  softwaredevelopment  softwareengineering  solution  somedaymaybe  stackexchange  stanford  statistics  stevenklepper  strategy  studyhacks  systems  tcsnmy  teaching  teambuilding  teams  teamwork  tech  technology  ted  tedtalks  thinking  thomamoran  tips  tool  tools  toread  transdisciplinary  troubleshooting  tutorial  tutorials  universities  unschooling  us  usability  usercentereddesign  ux  vickychan  video  visualthinking  warc  whitesaviors  willthomas  wizard  wonk  work  workshop  zachgage 

Copy this bookmark: