We have different ways of solving problems

Where should we start on solving these problems?

I wanted to say that it feels to me that design is about solving problems and providing elegant solutions, and information design is about solving information problems.

So you aggregate all these computers together and now they're solving big problems

So the unexpected is always unexpected.

Let's just look at something like, you know, solving problems with making airlines safer.

Unexpected Connection

unexpected character

unexpected end

Very unexpected.

He didn't just write code, he also got people excited about solving problems he got.

The search is not for the solution of the problem, but for problems themselves worth solving.

So it doesn't look like we're actually on the path of suddenly solving all big problems.

Unexpected Program Termination

Unexpected versus habitual.

That is unexpected.

I'm solving this.

Can we get people to wake up in the morning and feel energized about solving these problems?

Now, before we jump in to actually solving some problems, we're going to do the experiment ourselves.

Received unexpected connection, abort

Unexpected end of input

unexpected end of file

Disappointing, but not unexpected.

Unexpected, wellplanned, brilliantly executed.

But something unexpected happened.

Evoked an unexpected response.

From An Unexpected Source.

Something unexpected has happened.

Always do something unexpected.

I'll be very short on genetic algorithms. It's a powerful way of solving intractable problems using natural selection.

You know, it's true, the cathedrals, as unexpected, will always be unexpected.

And this shows that engineers, medical people, scientific people, have an obsession with solving the problems of reality, when actually most problems, once you reach a basic level of wealth in society, most problems are actually problems of perception.

Action Puzzle Solving Game

Problems, no problems.

Unexpected response from POP3 server.