Open Stanford Course: programming methodology 02

If you are stuck in the back, just come on down, have a seat.

summon students to sit down. now class begins.

 

that's a whole different issue.

 

which is due on Friday of next week, October 5th.

hand up the assignment before that day.

 

and then what do we want to do?

you see, it just uses the present tense.

 

notice at that point we could have actually done something else.

 

there's actually many ways to solve the problem.

you see, he didn't use there're, but there's, is he wrong?

 

we're just going to happen to pick one.

 

yeah, conceptually , what we'd like to do is turn right, right?

 

and you kind of think about it, and you say, "that's all right"

 

if you go around far enough to one side, you end up on the other.

 

that's equivalent to essentially turning 90 degrees to the right.

 

now at this point, we'd like to think, oh good times, we can just run this and it's a Karel program, and life is happy.

 

an algorithm is essentially the recipe for doing something.

 

the program is something that is valid syntactically according to the rules of the language.

 

Karel is defined in what we refer to as a class.

 

and even this brace over here gets tabbed one more spot.

 

because it's nicely tabbed in.

 

and then I will return back to where I left off.

 

we actually have a souped up version of Karel.

what is the downfall of the modern college student?

and I just pick up from right after the close brace.

so after im done executing a loop.

 

assuming that Karel has beepers in his bag.

 

does the part that's referred to by the else .

 

for the time being

it means temporarily

 

and this is what we refer to as a nested expression.

we refer to what as a nested expression

 

what's acctually going on there?

 

the reason why we call them steeples as opposed to hurdles is because some of them are big.

 

and I've seen software companies do this where some hotshot programmer comes along and they are like "ah, im a great programmer."

 

and it's written in terms of the code so badly.

 

that's the first major software engineering principle to think about.

 

some wall that goes up some amount that you dont know.

 

we can see if he's feeling up to the challenge.

 

so the important lesson that comes from that is to think about the generality of the program, right?

 

If you have any more questions, come on down.