Name: CS50 2019 - リーディング8 - インフォメーション（プレリリース (CS50 2019 - Lecture 8 - Information (pre-release))
Uploaded: 2021-01-14T10:22:34.000Z
Duration: 1 h 10 min 30 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

過去完了形

And just eight weeks ago, 2/3 of you had never studied any computer science before.

And what we thought we'd begin with today is really a look back of truly how far you've come over just those several weeks.

In fact, it was just eight weeks ago when you first started tinkering with scratch this graphical programming language by which you could drag and drop puzzle pieces and making the computer do what you want.

And then a week later, you might have struggled with just getting Mario to ascend.

Appear mid by way of hash is that you were printing with at the time was perhaps quite non obvious.

But it's ever since has just been what a pair of nested four loops.

And then the week after that, you explored cryptography among other fields, and you learned how to encrypt.

And you've decrypted information like this snippet here.

After that, you explored some electoral processes and the implementation of algorithms that you might be familiar with from the real world, but perhaps didn't think about the trade offs and choosing one algorithm or another and then ultimately implementing it in code just a week later.

Did we transition to filters on instagram, implementing things like your own C P a filter so that moving forward, hopefully it won't take for granted.

When you click that button on the screen on your phone, you actually know where can presume we're in for what's going on underneath the hood as it changes from one setting to another.

And then, of course, big Board, where we handed you some 140,000 English words in a really large file.

And you had to implement your own spell checker a dictionary, so to speak with, using as few was using his little amount of time in his little space as you could, implementing ultimately your own hash table.

Thankfully, since then, we can all take for granted that those things exist.

Just a week later, we started handing you large files like this, and of all things you were able to deduce by writing some python code that this is Lavenders Deanna, among others in the class of whose files we handed you and then most recently, or perhaps quite soon.

Well, you learn to apply another language in this case sequel to questions like Who has starred in films with Kevin Bacon?

And so a number of tools are now in your tool kit.

And again, I would just emphasize that eight weeks ago, 2/3 of you had never done any of that before.

So even if it's felt like it has never let up in each week feels all the more challenging than last.

Consider the Delta and consider what we promised in the first week of the class that would ultimately matters in this course is not so much where you up relative to your classmates but where you end up relative to yourself when you began.

And it is indeed those eight weeks ago that you began.

And it's today and in the course is final weeks that you will ultimately be able to compare yourself.

So in trying to think today about what we hope your own takeaways are from not only the course, but computer science More generally, I actually pulled up some of my own notes you might recall from Week Zero that I mentioned I took this course myself back in 1996 and what happened to be the one that turned me from a government major to a computer science major, and I didn't take many notes at first.

It seems, in that first class, there were a couple of other pages, and so I started flipping through these And in fact, this was my second page of notes.

And if you focus what's on what's up here at the top?

Apparently one of my first notes to myself at a function for those unfamiliar today our instructions that do the work on.

Indeed, if I looked down further on my notes arguments, we introduce that same first day.

It's info that's passed from one function to another toe.

Have something done by or performed on it.

All right, so that actually maps wonderfully cleanly to what it is.

We indeed started ourselves doing those eight weeks ago just talking about what CS is problem.

Solving a problem is just something that's got input.

And the goal, of course, is to produce something with output.

And we had to agree from that very first week how we're gonna represent these inputs and outputs, and so we might do it symbolically with letters of the alphabet we know since then, with that, we might new do it numerically, as with decimal digits or under below that we might just use binary, a different based system using only zeros and ones.

Or we could even represent that same capital A just using some pattern of light bulbs or switches that you turn on in some order.

In fact, if you think back then to these first principles that we introduce those weeks ago 20 of the students now in the audience what does this say?

Why is that what we just agree in weeks ago, On what numbers map to what letters?

And so long as all of the humans in the world agree on that, whether sending e mails or text messages or the like, our computer systems can all present information that we ultimately understand.

What did this say way back when, If you need a hint, it was it was investing 128,514.

This was the face with tears of joy, Right, taking all of the fun out of sending emojis Anytime you receive or send an emoji, really, all you're sending is a pattern of zeros and ones or worse the number 128,514.

But your computer or phone are presenting it to you in a certain way based on that context, all based on just how we humans are.

Those before us decided how to represent this information.

But of course, we don't have just those inputs and outputs.

There are another piece to the puzzle in, so I actually look back on my own third page of notes here and focused on my first line here back in 1996.

An algorithm is apparently a precise sequence of steps for getting something done, and programming more generally is, ah, process of taking an algorithm and putting it into a language a computer can process.

And indeed, that really was the additional puzzle piece we first focused on in Week zero.

It was what was inside the proverbial black box, the sort of secret sauce that you provide your input to.

You get your output from those air the algorithms that we've been talking about ever since now, not just in pseudo code or in English, but in CNN Python and now sequel in the coming weeks.

But of course we used algorithms to solve problems.

And one problem is, isn't was rather old school, and we thought we'd reflect just a bid and perhaps reinforced that same week, zero it by taking a couple of volunteers, perhaps a student and one of their family members, voluntarily or forcibly, with them.

You have to be comfortable, though appearing on stage and in turn, the Internet in perpetuity is the catch.

Okay, I see one volunteer and either mom or dad fighting out who's not going to go up.

A round of applause, if we could for our volunteers.

You'll recall from week zero that one of the first problems we solved was looking up someone in a phone book.

Well, here I have a pretty thick yellow pages wherein there's a whole bunch of products and service is alphabetized from A to Z, and we can, of course, look up the number for someone in this book.

For instance, Supposed today we need Ah, plumber.

Could we ask Mariano to find us a plumber in this phone book?

Ah, dad and other parents here what you might have done instead?

And for those wondering, let's continue the algorithm, if you will.

And then if it's not on the it's like we'll need to is a little strong, but you can get rid of Yes, indeed.

So if you keep this process going, having and having in having what should you be left with?

A round of applause, if we could for both of our volunteers here.

字幕リスト動画再生

CS50 2019 - リーディング8 - インフォメーション（プレリリース (CS50 2019 - Lecture 8 - Information (pre-release))

ultimately

apparently

deliberately

flip