Auto news on Youtube Mar 1 2018

oh yeah, and

Generally speaking, we need to quit this, and how do I

instructions and signs for time travellers are here too

this is how you can quit smoking cigarettes

I think it worked

Here we even have a counter

It shows us how many cigarettes have we not smoked

since we started not smoking cigarettes

8134

...33

very nice

why do we glow into looking rectangles

wait, those are the wrong ones

why do we look at

glowing rectangles?

Sometimes I even think that this question is as simple as

"Why do we travel in time?"

But if I asked it right now it would divide the viewers into 3 groups

Usually it's because we can find people...

...doing things there

Usually it's because they are rectangular

and they glow

But what if

they don't glow because it's daytime?

What do you think, why do we look at glowing rectangles?

Because they are rectangles.

So?

They are just nice.

Like apartaments.

OK, do you understand this?

In some we can see, for example, the sun

if so, I had to somehow be looking at a glowing rectangle

because otherwise I would have no way of recording this

Oh, I think I just moved.

We look at glowing rectangles...

...because sometimes we want to see...

...what is it going to be about because we simply had the same idea

Sometimes it's because we see ourselves there

Or when we are with someone and want to show them something fast

Those are the servers

But we need to be VEEERY quiet when we say they are servers

or THE DATA WILL WAKE UP

But I think the main reason

is the fact that inside

we can find

a way to have a break from the mundane that's not meaningless

8142

this one doesn't glow at all

I think it's broken

bathroom pigeons

Episode 3

Episode 29

pigeon pigeon

this is a laboratory power supply

this is a HOT AIR soldering iron

here's water

and here's tea too

did you think you are the only one with tea at home?

For more infomation >> Why do we look at glowing rectangles, and also - Duration: 4:24.

-------------------------------------------

Ask the Aquarium — "Why Do Small Fish Matter?" - Duration: 1:07.

I'm standing in front of River Giants, and these have our big fish.

That's what everyone seems to be attracted to and notice, but our rivers and creeks are

full of small, little fish that are really important.

What are these big fish going to eat?

They've got to eat smaller fish.

What do these smaller fish eat?

They eat little aquatic insects.

The aquatic insects have to eat even smaller animals.

All of this is part of our aquatic ecosystem.

When we have a healthy aquatic ecosystem, we not only have big fish, we have little

fish and a whole lot of other cool, aquatic animals.

Not only does this help us have a healthy aquatic ecosystem, it helps humans.

This ecosystem pretty much cleans our water.

Having a healthy ecosystem helps all of us, from humans to big fish to those tiny,

but mighty important fishes.

For more infomation >> Ask the Aquarium — "Why Do Small Fish Matter?" - Duration: 1:07.

-------------------------------------------

Ehsan Sehgal Prose Poems - Awaiting Your Arrival - Why - Duration: 1:11.

A prose poem, Awaiting Your Arrival, by Ehsan Sehgal

I am, who lives, In heartbeats of your heart,

Who waves, In your eyes,

Who exists, In your thoughts,

Who interprets the illustration, And visibility of your dream,

Who breathes, In your breathing

I am golden truth I am your home, city, and land,

Peace, and confidence I am,

Love with its utmost reality I am life, within your life

Oh, my destiny I will await your arrival

In my entire life.

A prose poem, Why, by Ehsan Sehgal

You are a stranger I do not know you

I never met you, You didn't any promise

But why do I stay Waiting, for you?

For more infomation >> Ehsan Sehgal Prose Poems - Awaiting Your Arrival - Why - Duration: 1:11.

-------------------------------------------

Bursting the Westminster Bubble Why do MPs Bob? - Duration: 1:47.

Hello Plymouth, Luke Pollard here, I'm your Member of Parliament. In the second of my bursting

the Westminster bubble series I'm going to be dealing with why MPs bob up and

down in the chamber.

You might have seen me do this, bobbing

up and down trying to catch the speaker's eye to speak in the debate.

Instead of putting our hands up to speak in the chamber or pressing a button as

you do in other Parliaments, in Westminster you have to bob up and down.

This is so we can catch the speaker's eye and so there's a very strict

hierarchy in the House of Commons, if the father of the House, the MP who's been in

there the longest wants to speak he gets called automatically. Then it goes in

order of seniority so if you've been in the House of Commons for a very long

time, normally meaning you're representing a

very safe seat, you get called next and new MPs like me get called right at the

end, but each time the speaker changes you have to bob up and down like this.

So in a big six hour debate and I've been in a few of them, where I'm the last

person to be called, I can bob up and down 50 to 100 times.

It's good for your legs, good for your ass in terms of your muscles, but it's not

always the easiest thing to do. It means you've got to pay attention and keep an

eye on the speaker and at the end of that there's no guarantee you're going

to get called by the speaker. So next time you see me in the House of Commons

and I'm bobbing up and down, that means I'm trying to attract his

attention, which means I've got something I'm trying to say or a question to ask.

Point of order, Luke Pollard.

That's why we bob up and down, it seems a bit silly really, but it is the

way that Westminster works. Thanks very much Plymouth, see you soon.

For more infomation >> Bursting the Westminster Bubble Why do MPs Bob? - Duration: 1:47.

-------------------------------------------

Why Do I Gain Weight If I'm Normal Weight? Gaining on 2000 calories. - Duration: 5:14.

Hi everybody it's Elisa here so today I'm answering another typical question I get and

It's about like when somebody is at the normal weight range

They think this is their healthy weight for their body

Then why in recovery they keep on gaining weight?

And they often think that this is because of the food because they're eating too much

But actually I want to say if you are truly at the healthy weight and your body is healthy

Then you should be able to eat to your full hunger the full hunger and satisfaction and have no more

Starvation symptoms, eating disorder symptoms, and then you would maintain your weight

eating whatever you want whenever you want however much you want and

And your weight should be stable, but if you are gaining weight eating to your full hunger

Then your body needs it, and it's not about the food

But it's what is the hormonal and metabolic state of your body, and this is the

this is the reason because if you come from past of restriction,

dieting, eating disorders your body is not hormonally and metabolically in a healthy environment

So yeah like if you eat the food and your body is not in a healthy state of course

it wants to store more weight because your hunger cues are higher

your metabolism is suppressed so

So yeah, but does it mean that

you should not eat then? Because you keep on weight gaining weight

No, actually if you keep on eating to your full hunger and satisfaction AND you never ever ever

diet, restrict, compensate, ever ever again

then actually your body will restore your normal metabolism your normal hunger cues it will restore the

like the hormonally and metabolically healthy environment for your body and

then you are able to eat to your full hunger and satisfaction and maintain your weight, your set point weight

So yeah, this is the basic thing. And also when somebody has gained weight

Let's say to their healthy weight range or whatever

And they have done it with restriction. Let's say they ate 2,000 calories and

they gained all the weight back eating 2,000 calories, but their hunger is still

You know so big they still have the "binges" and their metabolism is not healed so they think

That since they restored the healthy weight eating less calories so for them

The moment to eat to full hunger has passed because they don't need to gain any more weight

I don't know if it makes sense

But this is like what I hear all the time and people think like it's too late for me to eat to my full hunger

because I

technically have restored my weight, so I shouldn't eat more but actually no recovery is not about

the weight or having like "a normal weight range" It's also about

you need to restore your metabolism, you need to restore your hunger

your hormones and everything and for that it doesn't matter what's your weight, you still need to eat to your full hunger and

For example I was normal weight

throughout my

eating disorder and even recovery and I ate the minimum calories you know the

2500 to 3000 calories

and plus that extreme hunger and because my body also needed to restore

the health and the metabolic and the hormonal environment of my body

and I was normal weight

And I still, I had to eat my food hunger and satisfaction the mental hunger the emotional hunger

And the food thoughts and everything so it doesn't matter what's your weight

you still need to your full hunger like no matter what and

and yeah, and then your body will restore, and then you are able to maintain your

setpoint weight by eating however much you want and never worry about

You know the weight

fluctuations, or you won't just keep on gaining gaining gaining, so so yeah

so I really hope it makes sense and

Thank you for watching and see you next time! bye!

For more infomation >> Why Do I Gain Weight If I'm Normal Weight? Gaining on 2000 calories. - Duration: 5:14.

-------------------------------------------

The Secret of Numbers. Why do we need numbers. CHANNELING - Duration: 18:36.

For more infomation >> The Secret of Numbers. Why do we need numbers. CHANNELING - Duration: 18:36.

-------------------------------------------

Why Do I Get Turned on When I Have to Pee? - Duration: 2:34.

For more infomation >> Why Do I Get Turned on When I Have to Pee? - Duration: 2:34.

-------------------------------------------

Why do markets seem concerned about inflation? - Duration: 5:11.

For more infomation >> Why do markets seem concerned about inflation? - Duration: 5:11.

-------------------------------------------

Why Do We Suck at Making Passwords? | NBC Left Field - Duration: 3:07.

Has it happened to you yet?

Have you had to redo a password this week?

If so, you join some of the 37 percent of people who have to redo a password each week.

And, contrary to popular belief, it's not the words 'love,' 'sex,' 'secret' or 'god'

that are getting us into trouble.

It's a little more complicated than that.

And it involves:

A letter.

A lower-case letter.

A number.

At least 8 characters.

A symbol.

Another symbol.

A special character...

We are SO bad at making passwords.

The top 10 worst passwords of 2017 are:

'123456'

'password'

'12345678'

'qwerty'

'12345'

'123456789'

'letmein'

'1234567'

'football'

and 'iloveyou.'

If you think about it, passwords are related to distance.

Once you used to use your face as access to the things you wanted.

You'd show up and go 'Hello, can I have that please?'

Now you need something to stand in for your face virtually.

This graph shows the rate at which the world got online.

It also shows the rate at which we put our private information online as well.

In 1994, the first web purchase is made,

and of course it's a pizza because people don't change.

In 1995, banks start offering account services online.

In 2004, Gmail is launched.

In 2007, the iPhone is launched and by 2012,

one billion people are active monthly users on Facebook.

And we need passwords for all this stuff.

And we need to remember them.

Studies show that if we want to remember something, we have to pay attention to it.

That's how it's moved from working memory and into the

long-term memory part of the brain.

We're invariably not paying attention when we get the 'update password' email,

so we just plonk in any old thing.

And we often end up using passwords we've used before.

When you're online, your brain is so full of new information, some of it spills out before

becoming long-term memory.

So the internet keeps asking us for passwords, which we have to remember to make strong enough,

but at the same time it's the internet, which makes it so much harder to form

long-term memories.

Today we have as many as 81 passwords.

That's a lot to remember.

And boy, do we try.

Sixty-five percent of people memorize them in their head.

Clearly, they don't.

Eighteen percent of people write them down on a piece of paper, which isn't actually a bad idea.

Three percent use a password management program.

Gold stars for you.

Historically, we've been told to make our passwords stronger by making them more complicated,

but the human brain online just isn't up for it.

So instead we put in something simple again.

Now the advice is, make it longer rather than what you think is random.

The internet is changing our memory, so it's likely you're gonna have to redo a password

in the next few days.

Just remember, when you do, just make sure it's better than these.

Thanks for watching! If you'd like to see some more videos, then follow NBC Left Field.

And if you want to see some more mixed reality, check out the film we made about marriage.

For more infomation >> Why Do We Suck at Making Passwords? | NBC Left Field - Duration: 3:07.

-------------------------------------------

Why do We Have Repeatable Read and Serializable Isolation Levels? - Duration: 10:00.

Welcome to Repeatable Read and

Serializable Isolation Levels in SQL Server. I'm Kendra Little

from SQLWorkbooks.com. Today we will be answering five questions:

we'll be talking about why we need repeatable read and serializable

isolation levels; we'll be doing demos of how we can get

incorrect data in the read committed isolation level; and if we're using

repeatable read and serializable, under different situations we say we have to have correct data or

we're just not going to finish our query;

we will talk about ways that the serializable isolation level may sneak

in, even if you aren't using it on purpose! Even if you if you haven't changed your isolation level

to serializable, or use a hint, there's some scenarios where SQL Server will

escalate your isolation levels behind-the-scenes. And we'll talk about

How to tell if your apps are even using these -- as well as a very important question:

what's the way to make sure that you get correct data in SQL Server?

So, first up: why do we need repeatable read and serializable?

In fact there can be clowns and ghosts -- or phantoms-- that

are sneaking into your data! The default isolation level in SQL Server is

called read committed. This is the default isolation level

in what's called the "boxed product" of SQL Server. If you install

SQL Server yourself in a virtual machine or on a server-- I'm not talking about

Azure SQL Database-- but if you create a database on a SQL Server you install yourself,

the default isolation for your queries is called read committed. In

Azure SQL Database, it's different, because read committed has some issues. "Read committed"

sounds really good, right? Okay, I'm going to read committed data. That sounds like it would

be great, but read committed is lock based.

When we read, say from an index in read committed, we run through

that index getting locks as we go and releasing them right away. That also

sounds good, but when you look into the details, what this means is: since we let go of the

locks as soon as we read them, and our query may still be running, data

can move around on us. We may read some rows twice:

if we read it and passed it and then it jumped ahead, we may see it again. We may miss

a row entirely: if I'm running through the data and a row is updated and moves

behind me, I may never see it as I traverse that index.

And, we even can return

combinations of data that never existed. Just plain

part "before data", part "after data." And we'll dig into this last one. It's the

weirdest one, we will dig into a demo in detail and see how that can happen in read committed.

When we talk about isolation levels, not just in SQL Server, but when it comes

to relational databases altogether,

isolation levels are actually defined by what phenomena

can happen in that isolation level. These phenomena

are different types

of weirdness that can happen-- different "issues" if you will

that can happen under that isolation level. Under the default isolation level of

read committed, the phenomena of dirty reads...

Represented here by the poop emoji... that is not possible. So

read committed at least has the virtue of not allowing the dirty reads phenomenon. But there

are other phenomena that can happen in read committed: we can

have non repeatable reads, which we will see as a clown. And we can have

phantom reads. Non-repeatable reads: the name, at first didn't make any sense to me.

But it really means what it says. It means: I read this data and

if in my transaction I were to read it again,

I would not get the same value. This can be a huge problem, and the data will just look

wront to users. Phantom reads are a little different: if I read the same set of

rows again, I won't get the same set. Maybe there is a row inserted,

maybe there were three rows when I read the data first, maybe there were four rows one I read

the data again. Nothing was *updated*, but a phantom

row appeared.

What are some examples of this?

Well, when we think about is not that hard to imagine. For

a non-repeatable read, imagine that I'm running a

report. I'm running this in read committed, and I do begin tran.

My first SQL statement selects the SUM

of my revenue from the table.

I've summed up my revenue.

After that first statement completes, another transaction updates

a row in that table, and it changes some of the data. My report

it has the summary data at the top, and it has a detail section below it. So

I then run a statement that's getting all the detail data. In

read committed we are going to get the updated information in that second

query. So, when we selected the sum of revenuel we

have a non repeatable read in there. We read some data that changed after that.

We read it again and it was different.

Phantom rows are similar.

We're running our same report. We select our summary data, and then after we

select that summary data, but before we do anything else,

another transaction along. They insert a new row into the same data

we're selecting. In this case we don't even have a where clause, we don't even have any predicates. They just insert

a row into that table. Now when we run the detail data, now we've got an extra row in there

that isn't accounted for in our sum. In both of these cases,

in the case of the non-repeatable read and in the case of the

phantom read, if your CEO is reading this report,

she's going to look at this and

be like, "This data isn't right. These numbers don't match."

So, we either look

like a clown, or we're seeing a ghost in our records, neither of which are good.

The isolation levels repeatable read

and serializable were introduced

to make sure that if we don't want to have these

phenomenon, if we don't have these issues, we don't have to. We can prevent

them. If we aren't worried about phantoms and we only want to prevent non-repeatable

reads, we can set our isolation level to repeatable read. You can also use

a query hint, but this as for my entire session, for everything right, you know, I want to use repeatable

read unless I hint otherwise. We start our report,

we select the SUM of our revenue. The difference is, now that I'm in repeatable

read, I am, after I select this data, I going to hold on to some locks on that

data that protects it and says if anyone comes in and they try to update a

row, I have a transaction that is -- if I

read this data again, it needs to be the same. I need to protect it. So

while my transaction is ongoing, somebody else comes in and tries update that row. They are going

to be blocked, and they can't read until I'm done, until I commit my transaction or

roll it back. So now, when I select my detail data, my

read are repeatable, they are all the same.

My CEO sees data that matches. I do not look like a

clown. This is good, right? But there was an impact. There was a tradeoff.

That transaction that came in to update a row,

it was blocked, and it had to wait. What happens if in the rest of

this transaction I'm doing stuff that takes a whole lot of time?

And, what if the update is really important and there's

an executive from one of my clients waiting for that update to complete on a screen?

So, there are tradeoffs here, if we're using

this method to make sure our data is correct. Because if we are using a disk-

based table, repeatable read is going to protect this

with locks. And with locks can come blocking.

What if I'm worried about inserts?

Well, repeatable read isolation level is holding locks on

what I read: it isn't doing anything to prevent against rows being inserted. If

I'm worried about those phantom rows, I need to set my transaction isolation level

to serializable. Serializable says: you won't have any non-repeatable reads, and you won't have any

phantoms. So it includes the protections

of repeatable read, and then adds additional protections.

In this case, I run my first query and I acquire

key range locks that are held to the end of my transaction. I'm

not just protecting exactly what I've read, but I'm protecting a range

that says-- new stuff cannot be inserted into this range.

If an insert happens, the insert will be blocked. Same thing for an update, if an

update happens it will be blocked. If an insert happens, it will be blocked. So when I

run my last statement, I can get

data consistent with the first statement. But again, this

is a pessimistic-- what we're talking about with repeatable read and serializable

are pessimistic isolation levels. We're collecting

key range locks,

and, our tradeoff is blocking. But we get corrected data!

And that is a good thing!

For more infomation >> Why do We Have Repeatable Read and Serializable Isolation Levels? - Duration: 10:00.

-------------------------------------------

Why Do We Foam Roll? | Stowe Training Systems | Personal Trainer 78751 - Duration: 1:12.

- This is Nate at Stowe Training Systems,

and I wanted to talk a little bit today

about why it is that we foam roll.

Basically, when a muscle is quote unquote tight,

we can't actually change the length of that muscle,

every muscle has a defined beginning and ending position.

So my bicep will start here and end here,

and no amount of stretching is really gonna change that.

What I can do is get that muscle to relax,

and that's what foam rolling is.

It's basically the same concept as a massage

or acupuncture or something like that,

we're just getting the muscles to relax.

So instead of having the muscle always flexing,

and it's like, oh look at how tight my bicep is,

it's like, no dude, relax.

So that's all that's going on with foam rolling,

we're getting the muscle to relax,

and that's why it's so effective,

because it is just this relaxing,

it's more a neuromuscular in your brain issue

versus a physical change to the body,

it works crazy fast.

So we can get the change of motion,

we can get that motion out to here,

increased very, very quickly, which means

that you're gonna feel better very, very quickly,

and you're gonna be able to get

into more complicated exercises

that require the full range of motion much quicker.

So there you go, why we foam roll.