And in a way, structured query language is the biggest part of this class we're going to learn what data base design. We'll going to learn like block said data base design, one to one relationships, foreign keys, join, select, delete, update. And you're like do it and there's a bunch of really simple kind of things that you construct orders and patterns and loops and that's what you're good at by now in SQL.

That you can say hey, what is the actual value for the letter H. And it's called ord, which stands for ordinal. So this was like, UTF-8 rocks, and that's really because, as soon as these ideas came out, it was really clear that UTF-8 is the best practice for encoding data moving between systems. And the nice thing is, is you can tell it what character set it is but by default it assumes UTF-8 or ASCII dynamically.

So this is kind of hiding abstraction, there's a lot of words that we use to basically say, don't worry about what goes on inside. And like I said, we have been using objects the whole time, strings, integers, dictionaries, lists, floating points, etc. But another way to say it is it's got code in it, and we call a function inside the object, and they're kind of equivalent, but sort of just one to some people seems prettier than the other.

But we're expecting you to be increasingly good at using classes that are built into Python. It's just kind of a, so far, it's like a clever way to hide or embed a function inside this template. So up next, we're going to look into a little more detail of this notion of constructing and destructing multiple instances of objects.

We have terms that we use to describe this, we call it constructor or construction of taking the template which is like a pattern and then building it. Because think of objects as small programs that we're sending stuff into almost like little mini applications that we got an API to talk to. And the key thing to start to realize is that the template is sort of replicated multiple times and then each one can have a different color frosting on it.

The parent class might be animal and then you might have a dog, a cat, and a bird, right? And that's probably the right logic to have right now, because you haven't written programs that are complex enough to require object orientation in terms of the code that you write. Those things are actually complex data and code and we don't have to worry about that, and so the benefit to us right now is it simplifies our programs to make use of objects that others create.

But they didn't really correspond to the kind of strict software engineering standards that my colleagues and I had learned to observe, so we developed our own language which was based on, well the full story would, of course, be longer. Which even UML which should be high level, didn't quite get right, so that's it's a whole set of seemingly small properties, that together make a, give a framework in which you can change your designs and integrate new ideas very easily and very quickly without suffering too much. And of course, as you pointed out, contracts, the use of formal precise specification elements in association with every piece of software, these ideas and a few more apply throughout the lifecycle, throughout the process, from the highest.

Hello this is Chuck here, and we are in London at the Hammersmith Tube Stop. Hi, I'm Jonathan, and I'm cheating slightly this course, because I remember a lot of this stuff, but with my history, it's been really good. Another successful Office Hours here in London.