Okay.

You hear me?

Also.

Good morning.

This is working so many technical difficulties.

Hello.

Welcome to today's live stream.

The irony here is that it actually was a starting the lifestream five minutes early and it didn't work.

S o.

I'm just waiting till people see me, they consider this music is loud.

Okay, that I can, uh, that can be adjusted.

I see.

Greetings from Denmark.

Okay.

Who Here we are.

Oh, also so hard.

Life is so hard sometimes.

Technology.

I was so ready, so much energy.

Hate a plan.

I was prepared.

And now I feel like a complete and total loss because mentally I sort of, like, checked out.

I was like, It's not gonna work.

I'm gonna get going.

Just like stop.

I was I was like to To To our left.

You are minutes from giving up also, unfortunately, getting over a cold.

And, uh, but I felt the need to live stream today because 00 uh, I'm gonna discuss nature of code down.

Third stop.

I felt the need to live stream today because I am going to be mostly on hiatus for quite a bit of the summer hiatus.

for not from producing content but from producing video content.

Because I am hoping to focus my energy and efforts towards the second edition of the nature of Code book, which I hope to finish by the end of August and then be back full steam, live streaming in the fall and making videos that a company in a second dish of the book.

That's kind of the point.

So let me just a mute myself for a second here while I blow my nose.

What's happening?

I'm sure today sponsor Brilliant Hot or GE is thrilled to be sponsoring a YouTuber who is meeting their microphone and blowing their nose.

But I do want to thank Brooke dot or GE.

I'm excited about looking at billy dot org's a bit today because I won't talk about the nature of code book, and I looked this morning at blade dot org's Daily Challenge.

Take a look at it now sign up it for free and brilliant dot org's slash coating train.

The Daily challenge from today relates to examples from Chapter two of the nature of code, so I'm gonna look at that challenge and solve it with you at the third stop of today's trade.

All right, but let me go straight.

I have not moved to my new studio.

Asks for J uh, let me move first to the first stop.

So this is my This is my schedule for today.

I am now, unfortunately, behind by 30 minutes.

I have two and 1/2 hours.

I had two and 1/2 hours.

Not only have two hours, I probably should skip this 1st 1 but I always I'm putting the things that I always skip first and putting the things that I don't usually skip last.

So we'll see how this goes.

So hopefully this is gonna be a quick one.

I'm gonna just move full steam ahead, because, um, I lost all that time, so I will skip the usual pleasantries.

Um, uh, and I'm going to go to get hot dot com slash coating train slash websites, and I'm gonna go here.

Uh, so I need All right.

Okay.

Um, and let's let me fix this.

Okay?

Right.

All right.

So the first thing that I want to do today is actually walk through the steps to make a community contribution to the coding train got calm, especially if I won't be live streaming for awhile.

We can interact with each other by sharing more projects based on the existing coating challenges.

So also, move down a tiny bit.

There's, like, some stuff going on here.

What's over here?

There's something like but I feel like is showing up.

Oh, it's this, uh okay.

You know, it's one of the side.

There we go.

Okay.

All right.

So I'm just going to get started here with this.

Alright, here we go.

Uh, just before I do this quick tutorial, uh, Taser cake is asking What's the schedule?

Let me pull that back up.

This is my schedule for today.

I don't know that.

I'll get through all of it, but this is my goal.

All right?

Very loud.

And I do have a bit of a sore throat and still sniff.

Lee knows I just, like terrible cold.

It's so much better.

Today was completely incapacitated on Tuesday and today's Thursday.

So yesterday was a mild, and today I feel better about their some residual symptoms.

You brought here it in my gravelly voice.

Yeah.

I should be singing the ukulele.

My That would probably sound.

Excellent leader.

Hello And welcome to a quick tutorial on how to submit a community contribution, something you made based on one of my coding challenges to the coding train dot com website.

All right, so this is the code etrade dot com website.

You can see the most recent coding challenge as time.

This recording is number 147 147 of them, and it is the Google chrome dinosaur game.

But it was my own version with unicorns and that sort of thing.

So if I click here to up here, I'm gonna just click to coating challenges.

And now I'm on the page with all of the coding challenges.

So maybe you happen to make a project based on one of these, Let's find 10 print.

So I think this particular coding challenge has the most community contributions that broke the record, which whatever the record is.

But you know what?

Let's try a little experiment here.

This I shouldn't do this on my life streams, but I'm going to anyway, I'm going to record this with the green behind me and Matt, you So in the new studio that I'm planning to set up I'm gonna be.

My goal is to be able to record all the different views, cameras and screen captures two separate files so they could do more postproduction editing after the fact of the life streams.

Right now, I can't do that.

Let me do my description.

You know, you the viewer of this life stream right now, you know what the coding train dot com website looks like?

Or you could look at it yourself, So I'm going to just describe it.

And then Mathieu, who does video heading for the coating train will add it in the background after it.

Then why do the actual tutorial of showing you the steps?

I'll come back.

Okay, this is Dr This.

This is gonna find out.

Of course the camera goes off.

Yes.

And now you're all seeing my nice, green covered laptop.

This was the problem.

This is the problems folded in a weird way.

Hi Tech solution.

Here, everybody.

Hello and welcome to a Oh, this is a bad idea.

I could tell Hello and welcome to a quick tutorial on how to submit your own community contribution something you made based on my coding challenges to the coding train dot com.

So at the coding train dot coms home page, you can find the latest coding challenge.

You'll find a page there for that challenge that has the video itself links to the source code in with P five GS with processing with people I just Web editor, just the raw source code on Get up all of those things, as well as any links to other supplemental material I referred to in the video itself.

Then you'll find this section, my favorite section called Community Contributions.

And if you've made a project based on that coding challenge, you can submit your project to this page.

And what I want to do is show you how to do that in the context of this tutorial.

So there's two possibilities.

One is that the page won't have any contributions on it so far.

That's pretty rare, and you have to be the 1st 1 to add it.

Or if one if community contributions already exist, then you just have to add yours to the existing list.

So let's go to Let's pick a challenge.

I'm gonna pick the 10 print coding challenge because it happens to have the most community contributions, and I'm gonna show you how to add your own contribution to that page.

But the sink, the same techniques should, of course, applied to any of it.

The same technique, of course, replied to any of the coded challenge pages.

Editing, editing, editing.

All right, so now we go back to here.

I don't know if that was worth it.

Get a little extra work for Matthew.

Where am I?

Here.

Where's my mouth?

Serious s.

So let's go to a 10 print.

Okay?

All right.

Okay.

I just All right.

Oh, no.

I froze, Froze, froze, froze.

And I wasn't recording to disk.

Am I back?

I believe I am back.

Let me know when you see me back.

Hi again.

Okay.

So I don't have the chat up on the monitor that I look at over here that you can't see.

So I will get that in a second.

I'm just going to redo that explanation because it crashed in the middle of it, and I don't think it was recording properly.

Okay, boy, we're really not getting through anything today.

Thank you, Everybody, for your patience.

Welcome to Daniel Shipman's No, good.

Very terrible.

Horrible bad.

Bad day.

E.

Get that right.

Uh, no.

Good.

It's called terrible.