Name: CS50 2021 in HDR - Lecture 1 - C
Uploaded: 2022-04-27T11:39:34.000Z
Duration: 2 h 28 min 50 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

And this is week 1, the one in which you learn a new language, which

is something we technically said last week, at least if you had never

played with this graphical language known as Scratch before, which itself

But today, as promised, we transition to something

a little more traditional, a little more text-based,

not puzzle piece- or block-based, known as C.

But it's a language that underlies so many of today's more modern languages,

among them something called Python that we'll also

Indeed, at the end of the semester, the goal

is for you to feel that you've not learned Scratch,

you've not learned C, or even Python, for that matter,

but fundamentally that you've learned how to program.

Unfortunately, when you learn how to program

with a more traditional language like this, there's just so much distraction.

Last week I described all of the syntax, all of the weird punctuation

that you see in this, like the hash symbol, these angled brackets,

parentheses, curly braces, backslash n, and more.

Well, today we're not going to reveal what all of those little particulars

But by next week, will this no longer look like the proverbial Greek

to you, a language that, presumably, you've never actually seen or typed

But to do that, we'll explore some of the very same topics as last week.

So recall that, via Scratch-- and presumably via problem set 1--

we took a look at things called functions that are actions or verbs.

And related to functions were arguments like inputs.

And related to some functions were returned values like outputs.

Then we talked a bit about conditionals, forks in the road, so to speak,

Boolean expressions, which are just yes/no questions or true/false

questions, loops, which let you do things again and again, variables,

like in math, that let you store values temporarily,

So if you were comfortable on the heels of problem set 0 and last week,

realize that all of these topics are going to remain with us.

So really, today is just about acquiring all the more of a mental model for how

you translate those ideas into, presumably, a very cryptic new syntax--

a new syntax, frankly, that's actually more

simple in some ways than your own human language,

be it English or something else, because there's far fewer vocabulary words.

There's actually far less syntax that you might

But you need to be with these computer languages all the more precise

so that you're most, ultimately, correct,

and ultimately will see to your code is successful along a few other lines

So if you think about the last time you kind of wandered around not really

knowing what you were doing or encountered something new--

might not have been that long ago, entering Harvard Yard for the very

first time, or Old Campus or the like, be it in Cambridge or New Haven--

you didn't really need to know how to do everything as a first year.

You didn't need to know who everyone was,

where everything was, how Harvard or Yale, or anything else for that matter,

You sort of got by day to day by just focusing on those things that matter.

And anything you didn't really understand,

you sort of turned a blind eye to until it's important.

And that's, indeed, what we're going to do today.

And really, for the next several weeks, we'll

focus on details that are initially important

and try to wave our hands, so to speak, at details that, yeah, eventually

And by distractions, I really mean some of that syntax

So by the end of today-- and really, by the end of problem set 1,

your first foray, presumably, into this language called C--

And you'll be asking yourself-- we'll be asking yourselves--

Well, first and foremost, per last week, be it in Scratch

or phone book form, code ultimately needs to be correct, to be well done.

You want the problem to be solved correctly.

And along the way this term, we'll provide you with tools and techniques

so you don't have to just sit there sort of endlessly trying an input,

checking the output, trying another input, checking the output.

There's a lot of automation tools in the real world--

and in this class and others like it-- that

will help facilitate you answering that question for yourself, is my code

correct, according to our specifications or the like.

But then something that's going to take more time

and you're probably not going to feel 100% comfortable with the first week,

the first weeks, is just how well designed your code is.

It's one thing to speak English or write English,

but it's another thing-- or any language, for that matter.

But it's another thing to speak it or write it well.

And we spend all these years in middle school, high school, presumably,

writing papers and other documents, getting grades and feedback on them

as to how well formulated your arguments were, how well structured

And there's that same idea in programming.

It doesn't matter necessarily that you've just solved a problem correctly.

If your code is a complete visual mess, or if it's crazy long,

字幕リスト動画再生

CS50 2021 in HDR - Lecture 1 - C

literally

ultimately

sort

eventually