0:01

Monday. Monday. Monday. Open

0:03

wide depth fans. Get ready

0:05

to stuff your

0:06

face with JavaScript CSS. Load

0:08

Module. Barbecue tip. workflow. Breakdancing,

0:11

soft skill web development. The hasty

0:13

s, the craziest, the tastiest

0:15

web development traits coming in

0:18

hot. Here is Where? Sarah

0:20

CUDA, bars. And Scottsdale,

0:22

Toro, lungo, Tolitzky.

0:27

Oh, welcome. two

0:29

syntax on this

0:32

Monday hasty treat. We're gonna be talking

0:34

about some of the cool new

0:36

things announced and on the roadmap

0:39

from GitHub, there was a

0:41

big GitHub yearly

0:43

conference it's sort of like a a big

0:45

showcase where they show off all the cool stuff. And

0:47

we all know GitHub is constantly working

0:50

on cool stuff. And so this year's

0:52

was had no shortage of really neat

0:54

announcements. So we're gonna be talking about a lot of

0:56

the stuff going on in there and what it means for you

0:58

as a developer My

1:00

name is Scott Tielinski. I'm a

1:02

developer from Denver, and with me,

1:05

as always, is Wes Bos.

1:07

Hey, everybody. There's some really

1:09

neat stuff here. Somebody

1:13

sent me a link to this. And at first, I thought,

1:15

like, Is this a real website? because it

1:17

sounds like its own domain name. But

1:20

I obviously, it is a real stuff. And there's

1:22

some stuff that we've been talking about how we

1:24

would love for this to happen. So

1:26

I'm pretty excited about all these new projects.

1:28

We're just gonna kinda go through them and talk about

1:30

what we think about them and explain what they

1:32

are. I think GitHub is going to

1:34

be much more than a

1:36

git repo in the coming years. Yeah.

1:39

Hey.

1:39

I

1:40

just saw some of them cut off the presses

1:42

in unrelated to today's topic, which is

1:44

always great for us. But something

1:46

in relation to one of our recent episodes,

1:49

So recently, we did our episode

1:52

on the techniques for

1:54

responsive web design. One

1:57

was that. That was episode number five hundred

1:59

and forty. So

1:59

we did a five Now we're we're doing

2:02

a five forty, and we're having just a four more degrees

2:04

of rotation in there. and

2:06

here we are, or

2:07

five more degrees. And container

2:10

queries have been enabled in

2:12

Firefox nightly.

2:15

We were just saying when is Firefox gonna

2:17

get onboard with container queries and

2:19

here is a closed issue

2:21

on bugzilla, where container queries

2:24

have now been enabled on nightly.

2:26

So this is totally unrelated to the

2:28

topic,

2:29

but man,

2:30

that is That

2:32

that is great news for me today.

2:34

I'm super excited about that. I

2:36

would love to be able to say now

2:38

is the time to start really getting

2:41

hard into container queries, and Firefox

2:43

was that last missing piece. So --

2:45

Yeah. -- sorry for the detour, Wes. No.

2:47

I'm I'm into that. I'm just reading the

2:50

reading the bugzilla thread here.

2:52

It says there's only one worrying

2:55

time out.

2:56

It isn't a hard thing to hang on.

2:59

So it looks like

3:01

the container carrier is, like, almost ready

3:03

for prime time. I I think so. And

3:05

we we saw that. Once they're in Firefox, it's

3:08

Go Go Go Let's go -- Yeah. -- green.

3:10

Yeah. Look man. No.

3:14

What's what's the deal with everybody saying let's

3:16

go reason I think that's like I think

3:18

you're like maybe a two years. Somebody

3:21

literally just tweeted and in response

3:23

to that tweet, Let's go. That's

3:27

just Look at it. Urban Dictionary. That's

3:30

just but no. It's it's definitely

3:32

like a gamer thing or like a YouTuber

3:34

thing. Yeah. Definitely, there's like several YouTubers

3:36

who'd be like just just making

3:39

that their thing and then a you

3:40

know, kept

3:42

going going and going. Urban Dictionary says,

3:44

let's go. Things cringey eight earl's

3:46

Fortnite players say when they win a game.

3:48

Exactly. Yeah. That's it's definitely

3:50

out of, like, gamer usage. It is too. You're

3:52

right. Yeah. Oh, yeah. I've

3:54

been hearing it for a lot longer than that. Absolutely.

3:57

Me too. But, like, you start hearing

3:59

it like I'm hearing it

4:01

IRL now, you know. Oh, yeah. I

4:03

heard it a lot in believe it

4:06

or not, like, video and lighted

4:08

YouTube. There'd be like this camera

4:10

is a one. Let's go.

4:14

It's just the next gen version of the same camera.

4:16

Everybody else had the year before. yeah,

4:18

I always thought that was funny. I can't wait until

4:21

my kids are my kids are almost old

4:23

enough now or you can start

4:25

saying stuff like that. Oh, yeah.

4:27

Like, my So, like, I hear them. My

4:29

old no. Even my oldest daughter starting

4:31

to starting she

4:33

called somebody a noob the other day, and I was like,

4:35

oh, yeah. Yes. like, it's it's

4:37

starting. It's starting like and

4:39

she's you could tell that she's watching some YouTube

4:41

videos because of the things she says. Uh-huh.

4:44

And both of my

4:46

kids came into my office the other day, and

4:48

they said, what's that? I'm like, the the pointing at

4:50

the YouTube hundred thousand subscriber

4:52

button. and I sent us my

4:54

my YouTube play button. They said, you have

4:56

a YouTube play button. And

4:59

I said, yeah. I don't. Yeah. And and

5:01

those they said that they understand what it is.

5:03

And they said, you have a YouTube channel.

5:06

And I was like, yeah. They're like, you're

5:08

you're famous. What? Yeah.

5:11

My kids do have no idea. My

5:13

my kids love YouTube, but they

5:15

think all YouTube is is just

5:17

YouTube kids were there's other kids

5:19

playing with toys or blippy. Yeah. So

5:21

when I am I trying to tell them what dad does? And

5:23

it's like, yeah. But it's it's

5:25

not that It's not the kind of thing. I'm not like

5:27

in my office playing with toys. So it's

5:29

not it's not that fun.

5:32

Alright. We are sponsored

5:35

by two awesome companies today. First one

5:37

is Lenode. Lenode

5:39

is a cloud computing that developer's trust.

5:41

They provide hosted Linux

5:43

servers for pretty much anything. You

5:45

need high CPU, high memory, high

5:48

availability scaling. They do

5:50

all of that stuff. So if you've got a project

5:52

that you need to throw up on a Linux

5:54

server, Linode is for you, and

5:56

they're gonna give you one hundred bucks in

5:58

free credit linode dot com forward slash

6:00

syntax. Thank you, Linode for sponsoring. This

6:03

episode is also sponsored by Log

6:06

Rocket. which is a great place

6:08

to really understand how

6:10

your website is being used.

6:12

Now they really came out of the gate with their

6:14

session replay tool for finding bugs.

6:16

But their session replay tool is not just

6:18

for finding bugs because that would be

6:21

that would be excellent, but Logocket

6:23

is beyond excellent. They are

6:25

out of this world. And

6:28

with log rocket, you get access to more than just

6:30

a session replay for finding bugs, but you

6:32

can surface issues faster, optimize your conversion

6:34

and increase adoption by truly

6:37

understanding where your users are clicking,

6:39

what they're getting hung up on, and

6:41

what they are trying to do. and you

6:43

can do all of this in a very visual

6:45

way. You know me? I'm a visual person. So

6:47

this really brings well in

6:49

my brain. and works all of the tools you know

6:51

and love. Any kind of front end context that

6:53

you're working with, but not only that, it also

6:55

works with things like iOS apps, of

6:57

React Native, Expo, Android. It

6:59

works really well with all that stuff too. And

7:01

it integrates with all of the tools you

7:04

know and love whether that is your error reporting

7:06

software, your customer support software,

7:08

your a, b testing software, analytics

7:11

observability, and your voice of

7:13

consumer software as well. So if you

7:15

want to try all of that, Edmore, head on

7:17

over to log rocket dot com

7:19

forward slash syntax and you'll

7:21

get Fourteen. Days

7:23

four. Free. Thank you so much to Law

7:25

Crockett for sponsoring. Alright.

7:28

GitHub. GitHub, they're they

7:30

have AAA neat little URL

7:32

here called get hub next dot

7:34

com and get hub next dot com is

7:36

showing you kind of all of their interesting

7:39

product projects that are either

7:41

in the pipeline coming out or have

7:43

been released with a date attached to them.

7:46

And not only that, one of the coolest

7:48

darn things that this thing does is it has a

7:50

little interface and it shows you

7:52

who made it. So which of the the

7:54

members of the GitHub team are actually

7:56

working on these tools. I

7:58

gotta love that because it's not like

7:59

some faceless

8:02

Corporation being like, here by our

8:04

stuff. It's like, here are the actual folks.

8:07

Here are the actual developers making

8:09

the tools for developers that's

8:11

going to improve your life and your workflow.

8:13

And I I gotta say, well done on

8:15

that regard because that's really cool. Yeah. There are

8:17

some pretty neat projects here. I don't

8:19

even think we'll go into to to all of

8:21

them. But let's let's pick a

8:23

couple that we're pretty excited about. I think the most

8:25

the one that I'm most excited about is

8:27

get up co pilot for the CLI. And

8:29

this is something we talked to Jared

8:31

from Fun About is I

8:35

want GitHub co pilot to figure out what

8:37

I'm gonna finish typing

8:40

in in my CLI. Maybe the stakes

8:42

are a little higher when you're deleting something,

8:44

but there is a

8:46

I think a whole world that could

8:48

could be done there. And the fact

8:50

that I was, like, maybe, Warp is gonna

8:53

do it, you know, like, I'm not sure who's

8:55

who's gonna, maybe, Fig will do it.

8:57

But it looks like GitHub GoPilot is

8:59

going to be doing it. So I am

9:01

putting myself on the waitlist for that one. And

9:03

maybe one of you out here is listening,

9:06

could, you know, be inspired by this to

9:08

say, hey, maybe I should try using

9:10

this. See if I can get on the the wait

9:12

list here and give this a try to

9:14

make something really neat. You know what I would

9:16

really like? West would be a a GitHub co

9:18

pilot for recipes. You just start

9:20

typing a recipe and then it finishes it for

9:22

you, that'd be sweet. You know

9:24

what? One use of GitHub

9:27

copilot that I've been using that crazy now that

9:29

I'm recording my TypeScript course

9:31

is I'm using it to just

9:33

generate data. So you

9:35

can say a little

9:37

comment, an array of I

9:39

I did this. I said an array of web development

9:41

podcasts with their hosts and their

9:43

ratings. Mhmm. And

9:45

then you have to open you have to open up the

9:47

GitHub Copilot UI because

9:50

otherwise, it just gives you line by line. Yeah. But

9:52

it gave me an entire array,

9:54

including syntax being the best one,

9:56

which is correct. And

9:59

that's unreal.

9:59

And then I did like a I

10:01

did like a really complicated one

10:04

where I said a list of

10:06

products with their

10:08

ratings, with a nested list

10:10

of comments, the side

10:12

of that, and it literally

10:14

figured it out. it it did it. It

10:16

was amazing. And I was like, this is

10:18

key for doing

10:20

you wanna Adam, you did a bunch of dummy data

10:23

all the time. and you want it

10:25

to be, like, somewhat relevant or somewhat

10:27

interesting because you're staring at this dummy data all

10:29

day while you're doing your thing. So

10:31

don't want to be a food bar baz. We're

10:34

Exactly. Exactly. We we get access to

10:36

whatever. Do you should have you should

10:38

have done most handsome

10:40

podcast hosts sorted by most

10:42

handsomeest. And then Wait.

10:44

Can we how should we do that once that call

10:46

then? I gotta touch your file open right

10:48

now. list of most

10:50

handsome web developers.

10:55

God's most handsome web developers is

10:57

equal to. k. So I'm gonna open

10:59

GitHub copilot, synthesizing

11:02

solutions. Oh,

11:04

my god. You're right. You're

11:06

not gonna you're not gonna believe

11:08

this, Scott. I actually don't believe it

11:10

just because of how you're already presented.

11:13

So it says, handset webhooks

11:15

equals number one, West Boss --

11:17

Yep. -- I push thirty five. Is

11:19

that true? How old am I? Yeah. How old

11:21

are you? I'm I'm born

11:23

in eighty 8II thought I was

11:25

thirty four. Yeah. You I'm thirty

11:28

six. It says you're thirty

11:30

five. So Okay. Pete Hunt

11:32

coming in at number three, Ryan

11:34

Florence. Number four, Michael

11:36

Jackson, number five, Kensey Dodds,

11:38

number Six. Wow.

11:40

Interesting.

11:40

Very interesting.

11:43

Well,

11:43

yeah, that's fun. Co pilot CLI

11:46

I gotta say I'm excited for this. I, you know, I

11:48

I have not used the

11:50

synthesizing results. Can

11:52

you maybe for those of you out

11:54

here who are like me who have not used that. Can you

11:56

-- Yeah. -- just a a quick second about

11:58

that? So if when you're using GitHub,

12:00

Copilot, it gives you line

12:02

by line. But if you want a larger

12:04

thing, maybe you want a bit an entire I

12:06

guess it it it it doesn't give you line by line. Sometimes

12:08

it'll give you a whole function. But if

12:11

you want a lot of a lot of data,

12:13

you basically type your

12:15

comment or whatever it is that you want. and

12:18

then you open up your command palette and

12:20

just say open GitHub Copilot.

12:22

And it will show you

12:24

the ten solutions that it it

12:26

thinks to thinks to give to

12:28

you based on your

12:30

comment based on your comment and it

12:32

doesn't change so that if you

12:34

if you keep typing something, it's not gonna

12:36

change it. So it's kind of a way to just

12:39

preview what the possible options

12:41

are. Yeah. That seems like way

12:43

better to me than the

12:45

just, you know, having it pop up

12:47

in as a comment. completion

12:49

kind of thing in your time? Yeah. It

12:51

it depends on, like, like, what you're doing.

12:53

I think I I think if

12:55

you're just doing a couple lines here and there. Bam.

12:57

Bam. That that's what you want. But if you wanna be

12:59

able to maybe review what it's

13:01

going to give you, that

13:04

is probably a better approach. Oh,

13:06

here's another list of hands and web devs.

13:08

West Boss, first

13:10

quarter, David Walsh, Sean Larkin, Ryan

13:12

Florence, Adias Mani, Jake Archibald,

13:14

Paul Irish. I'm getting snubbed in this

13:16

one. Brendan Ike. Yes.

13:19

I'm sorry to say you're not on this one. Brendan

13:21

Ike coming in at number twenty five

13:23

kind of I don't know what I would have put them

13:25

higher, honestly. Could we get my mom's

13:27

list of the most handsome web devs?

13:30

Okay. Let's

13:32

talk about the next one here. which

13:34

I'm gonna start at the the actually, the first one

13:36

on their list. That's the most recent, which is

13:38

hate GitHub, which sounds

13:41

like you know, hey, Siri or anything like

13:43

that, but this is right code without

13:45

the keyboard, which is it's

13:47

really relevant for us because

13:49

we've had a a couple folks on

13:51

talking about repetitive stress injuries and

13:53

voice coding. So this is

13:55

GitHub's kind of own co

13:57

pilot based voice

13:59

coating solution. Use your

14:01

voice to code without spelling things

14:04

out by talking to GitHub copilot. So

14:06

you're not having to be

14:08

like, open brackets,

14:11

closed brackets -- Yeah. -- now

14:13

making clicks and pops and stuff,

14:15

you're able to talk

14:17

to GitHub co pilot. And

14:20

their examples are really interesting. Get

14:22

Titanic CSV data from the

14:24

web and assign it to variable

14:26

Titanic data. clean records

14:28

from Titanic data were ages

14:30

null. Fill null values

14:32

from column, like, this

14:34

is cool.

14:36

I like,

14:37

this is how I think in my brain. And

14:39

then I have to go in and then write the comment

14:42

and then then type it out myself to

14:44

say, filter out all

14:46

of these things from this array, even

14:48

though I've written that same filter code a

14:50

hundred times and I know how to write

14:52

it, this is gonna give you the option

14:54

to talk to GitHub.

14:56

And as long as you know

14:58

kind of the way GitHub copilot

15:01

wants to hear these things, it's going to

15:03

return back code. And I

15:05

gotta say,

15:06

I'm really impressed by this. You know,

15:09

this actually would be a really great use

15:11

case for our our last guest kind

15:13

of had one of those like

15:14

gamer headset mics with a

15:17

mouthpiece in front of it. That would be

15:19

like a really nice thing to have on and just

15:21

talk or even I guess AirPods too if you got them

15:23

in your ears. Yeah. A nice close

15:25

microphone up to your mouth and you just talk

15:27

to copilot. Wow. This

15:29

is really pretty neat. Yeah.

15:31

Honestly, I I bet that

15:33

this is there all

15:35

the examples that they

15:37

have are just adding

15:39

code. So at what point like, how do you

15:41

edit code with that? You know? Like, how do you

15:43

-- Oh, yeah. Right. -- change or something?

15:45

because remember, we had what was his name?

15:47

We had him on. We talked about it. He's like, go

15:49

back to he basically had little

15:51

stoplights over every single syntax,

15:53

every bracket, every word and

15:55

then you could just jump around to there.

15:57

But I bet if we're gonna eventually

15:59

get to some

15:59

sort of

16:00

accessible voice

16:03

to code, I bet that it has to

16:05

include some sort of AI in there and

16:07

this totally seems like it might be

16:09

it. That was a episode number

16:11

four hundred and eighty one of voice

16:13

coding with Pokey Rule,

16:15

which I I believe oh, no. It wasn't our

16:17

first separate club. That was, like, pretty early

16:19

on in our separate club. Yeah. So

16:21

that was the the really cool episode

16:23

if you wanna hear what the,

16:24

like,

16:26

really awesome intense world of

16:29

of voice coding. It's like, Yeah. It does it

16:31

I wonder, like, how much of this is,

16:34

like, one, interpreting

16:36

your text as comments and then using

16:38

those comments. to then

16:40

generate the code. But two, I wonder

16:42

also how much of it has to be

16:44

context aware of what you're doing already

16:46

what exists on the current page. And like

16:48

you said, what is that editing experience

16:50

like? Or is this just generating code

16:52

with your voice? Either way,

16:54

pretty darn cool development. Yeah.

16:57

Next one we have here is GitHub blocks.

17:00

This is kinda

17:02

cool because it's going to allow you

17:05

to add custom

17:07

interactive blocks into

17:09

GitHub. So you think probably

17:11

the simplest example is you have a read me and you

17:13

wanna be able to put some sort

17:15

of interactive table or

17:18

chart or

17:20

even like even if you have, like, a color

17:22

picker and you want to be able to show how it

17:24

works or or show someone how to generate

17:26

something, being able to embed

17:29

interactive stuff into your actual

17:31

your read me or

17:34

into a, like, a build. Maybe if

17:36

someone were to you

17:38

you have a bot that runs a build on a pull request

17:40

and you have some information

17:42

that needs to be outputted. Right?

17:45

this is really cool because you'd be able

17:47

to to do that type of stuff with

17:49

it. Scott, you said you've been

17:51

actually had access to this before it was

17:54

even announced. Yeah. Yeah.

17:56

As a GitHub Star Wars, I get access

17:58

to all this stuff really pretty early.

18:00

They let you preview

18:02

it. They they give you a little presentation

18:04

on it or they have chat

18:06

rooms where you can go in and and, you

18:08

know, ask questions about it and stuff. Yeah. and

18:10

our member being presented as kind of like a

18:12

big deal. But at the time, I didn't necessarily

18:14

get it as much as I get it today.

18:17

where, like, even just the tagline here, read me's

18:19

don't have to be static. That

18:22

right there should be the

18:24

selling point here. We we all create

18:26

readme's that are this or that. But

18:28

again, readme's aren't static and what we end

18:30

up doing is we end up creating this is a

18:32

tool for isolation development, but we end

18:34

up doing storybooks to document or

18:37

really deeply interactive examples

18:39

to document our components. And

18:41

we live in this world where you're just creating little widgets and

18:44

components, and now we

18:46

can create rich and

18:48

interactive repositories directly

18:51

in our code base without having to spin

18:53

up on an entirely second website just to

18:55

show that kind of stuff off. And I think that's

18:58

really pretty neat. You know, one thing that

19:00

GitHub rolled out recently that's not on

19:02

this list is the new GitHub code

19:04

search. I was like a beta test search for

19:06

it for six or seven months, and

19:08

I was using it, like, crazy.

19:10

Yeah. And now they've they've rolled it out. I think they

19:12

might even have some some more stuff coming down

19:14

the pipe, but being able to

19:17

search all of GitHub in super

19:19

fine grain control is

19:21

amazing. I use it all the time. If

19:23

I'm like, I don't know how to use this

19:25

API or I wanna know how are other

19:27

people using this specific method,

19:29

I can do that or somebody tweeted the

19:32

other day does anyone have an example of a

19:34

a GitHub repo that uses

19:36

that's built in JavaScript and

19:38

uses four tabs or

19:41

sorry. No. It uses four spaces as a as

19:43

a tab. And I

19:45

was just like, all I did was just go

19:47

into Hub and say, type JavaScript

19:50

file

19:50

editor config,

19:53

and

19:53

then I searched for

19:56

the config that would show that. And

19:58

I just replied immediately and they're like, how did you know

20:00

that? And it's like just

20:02

GitHub code search as is superpower

20:04

to be able to to

20:06

get those things up and running? Yeah. What

20:08

a a just a tremendous

20:11

platform. Whenever remember when Microsoft

20:13

bought GitHub and so many

20:15

people are freaking out about it. And now

20:17

here we are with what is

20:19

very clearly the best GitHub that we've ever

20:21

had. Yeah. The best GitHub features,

20:23

and it doesn't really seem to be slowing

20:25

down at all. No doubt. Even

20:27

I I also think a really cool

20:29

use case for GitHub code search

20:32

soon will be how many people

20:34

are using container

20:36

queries? Yeah. And you could be able to

20:39

maybe chart how many container queries are going up? Or what's

20:41

the most common container

20:43

query size? Or how

20:45

are people using like, those those

20:47

kind of, like, basically,

20:50

data science on top of how

20:52

our people coding, Google had

20:54

a a code search years ago and they shut

20:57

it down. And there there has never been anything other

20:59

than the the

21:01

web archive every

21:04

year. for us to, like, dig into and

21:06

learn these things ourselves. You know what? It sounds

21:08

like to me, Wes. It sounds like some

21:10

really great potential syntax exploration

21:12

episodes where we dive into

21:14

some fun fun stuff. I'm I'm totally

21:17

in. That sounds like great time.

21:19

we had so much fun talking about the web all the next

21:21

stuff. I feel like I could just

21:24

really love it. We haven't even dipped into

21:26

the Java stuff yet. We'd still have

21:28

a lot more data. Yeah. I I

21:30

enjoyed those very much. Yeah. By

21:32

the time we finished the twenty twenty two web,

21:34

Almanac, it's gonna be the twenty twenty

21:36

three web. Alright. Next step

21:38

that we had here is the collaborative

21:40

workspaces, which is a really interesting concept.

21:42

They describe it as I love

21:44

this. They have, like, stages for each of these, like, where they're at works

21:47

in progress, they're released, whatever.

21:49

This is described as a napkin sketch.

21:51

Not just like an Explorer. It's

21:53

a napkin sketch, which we all have

21:55

done napkin sketches. They're some of the best times

21:57

you ever think about something. It's one of the reasons why

21:59

I keep a piece of paper or

22:01

digital piece of paper handy at all times. just for

22:03

when you wanna start writing stuff down.

22:05

And this is really super

22:07

cool. I would imagine

22:09

this video that they have here of

22:11

showing this working is probably

22:14

it's probably

22:17

just faked. But I who

22:19

knows with them? That's right above it.

22:21

Using visual studios, liveshare

22:23

extension. Yeah. But I'm wondering if,

22:25

like, how much

22:27

of the features they're showing off.

22:29

in general, are, like, actual features out

22:31

there, like, what they imagine them to be,

22:33

like either way, it has, like, a column

22:36

that says session details,

22:38

participants, shared servers, shared

22:40

terminals, con contacts. So you

22:42

have all the people. If they're

22:44

available, they have, like, if they're break

22:46

or if they're green, if they're red, or

22:48

they're on do not disturb. It has little

22:51

multiplayer tabs to show who's typing

22:53

where it shows It's

22:55

it's really fun because it's talking

22:57

about, like, how do web developers work

22:59

in the same team, the same code base,

23:01

the same project, and they have a nice

23:04

little diagram. how people are working

23:06

so good in in their cert yeah.

23:08

All of these little websites are so good. They kinda

23:10

have a besides having a team to develop

23:12

these features, they have somebody or some

23:14

team out there that is making these

23:16

little little exploration websites

23:19

look so good. What's

23:21

going on with that? It's just incredible.

23:23

Between this and some of the other tools

23:25

that we've seen in

23:28

in this episode, man,

23:30

man being

23:31

able to collaborate on a code base

23:33

in about a year or two is

23:35

going to look very different than

23:37

it looks right now, regardless if you're

23:39

using this or whatever. and that

23:41

to me is exciting. Next one we have here

23:43

is get up co pilot for your own

23:45

code base. This one's kinda

23:48

interesting is they want to be able

23:50

to give co pilot

23:52

suggestions that are in

23:54

line with the idioms

23:56

and the formatting

23:58

and everything that you use with your

24:01

own code base. How

24:03

they do this will be

24:05

very interesting because

24:08

people do not trust

24:12

AI scanning your your own code base. So I'm

24:14

very curious to see what

24:17

how will they will oh, they have a whole paragraph here is

24:19

the in the machine learning

24:21

literature, the key concept is a retriever,

24:23

a precompile index that allows

24:25

quickly look up data items, etcetera,

24:28

etcetera. So they will

24:30

probably have to run it entirely

24:33

on your computer. We'll see how they do

24:35

that. There's there's like

24:37

the technical, and then there's the

24:39

people are gonna freak out and not actually

24:41

read -- Mhmm. read

24:43

that. It's like there's tooling your code. Like, this

24:45

hundred percent for sure is gonna happen. People are

24:47

gonna lose it. So they're

24:49

they have some certainly

24:51

some work cut out for themselves. They should,

24:54

you know, to to get people to trust it a

24:56

little bit more, Wes. And this is a free tip for

24:58

you GitHub if you wanna use some of my star

25:00

power here. instead of calling it a

25:02

retriever, they should call it a golden retriever.

25:04

because everybody loves golden retriever

25:06

base. They do. Sure. They're

25:08

like Retries are the golden retriever.

25:10

Yeah. Yeah. doesn't like a golden retriever.

25:12

Alright. Next question is or next

25:14

question. Next one of these things is from

25:16

the GitHub GitHub co

25:18

pilot radar. And this is

25:20

basically like navigating

25:22

your code. And they say it's

25:24

jumped to definition on steroids,

25:27

which to me personally

25:29

sounds really great. You know,

25:31

just being able to get

25:33

where you want to get is it

25:36

always slow, but it's not

25:38

always it's not always

25:40

super fast. And even now with, like, v s

25:42

code when you click through the functions Sometimes it

25:44

just takes you right to the TS types instead

25:46

of the actual function. And other

25:48

times you're doing a, you know, command t,

25:50

you're looking for symbols, you're looking for

25:52

files, you gotta figure out based

25:54

on, like, context where you are and what you're

25:56

actually trying to get to. And sometimes you have things

25:58

named the same things. So this thing

26:00

says it combines static analysis

26:03

with copilot AI.

26:06

So it knows what you're talking

26:08

about in any given file. And if then you

26:10

go to look for something else in

26:12

relation to that file, it's going to

26:14

present you with a

26:17

more relevant options and better

26:19

options even when it's not necessarily

26:21

as explicit as it is. So it's

26:23

it's basically taking that that

26:25

idea of your tech expeditor

26:27

knowing where you are and where you want to go

26:29

and putting into it's

26:31

with some AI to help you get there

26:33

in a more meaningful way. Pretty

26:35

much all of this is just add

26:38

AI and machine learning. Yeah.

26:40

Hey, you like your thing. We put AI

26:42

AI in it, and now it's even better.

26:44

Yeah. This is something that's been around for a while,

26:46

is the GitHub Copilot Labs,

26:49

where you give it a hunk of code,

26:51

and it will try to spit

26:53

out a human readable

26:56

explanation of that.

26:58

And in in my experience, it's

27:00

always been fantastic. You

27:03

could just basically you could take a

27:06

huge loop,

27:07

which

27:08

with reg x's inside of it and

27:10

and incrementing and all that stuff,

27:13

and it will convert it to text.

27:15

I don't think that this is

27:17

never like, I used it a couple times and

27:19

that that's really cool, but, like, I've never

27:21

gone back to it. to actually

27:23

solve any problems other than to just, like,

27:25

make people smile and and it's a

27:27

cool demo

27:29

the because because

27:31

I

27:31

don't know. I I hate being the guy being, like, oh, your code

27:33

should be readable, but

27:35

between comments and readable

27:38

code, not I don't think

27:40

I've had to I've needed this. What do you

27:42

think? I have not had the need

27:44

for this. But I

27:46

also, you know, I I think it's I

27:48

think it's a worthwhile thing

27:50

to have. I think it's worthwhile that existed.

27:52

Maybe there's a time where I'm gonna be like, oh, yeah.

27:55

That'd be that'd be great to have this. But, no, I've never

27:57

really had a a situation where this

27:59

is really made a ton of sense for

28:01

me. That's it. I I Yep.

28:03

It does seem like an important step if you

28:05

could imagine using AI to get

28:08

code

28:08

from natural language to get natural

28:11

language back get

28:11

into or code to back into natural language. Right? Yeah.

28:13

Does seem kinda seem like a back and forth, like a you

28:15

get it for free. Maybe if I was

28:17

in, like, Ruby or Rust

28:20

something that I didn't understand as

28:23

well. Yeah. What was happening? Because --

28:25

I don't know if you're learning tools. -- methods too.

28:27

Yeah. Yeah. That's true. You get you

28:29

get a a code example, you highlight, you say, what's

28:31

this do? Remember?

28:34

What was that our our

28:37

one of our syntax live games that we

28:39

did was, like, here's some old syntax. Like,

28:41

what does this do? You could give it -- Yeah. -- some

28:43

old syntax and be like, what does this

28:45

do? that that'd be very fun. Oh,

28:47

that that's their next product is

28:49

the GitHub whiteboarding

28:52

AI. where

28:54

you upload three hours of your

28:56

face, and it will do

28:58

the interview for you, and

29:01

it will craft a video of you

29:03

talking to the interview and get you

29:05

A77

29:07

figure job at fifty I

29:09

thought you were being honest at that point. And then I was like, oh,

29:11

and then when you said, like, the three hour video and

29:13

I was like, oh, no. Okay. That's

29:16

not. real. We'll do one last one and this one will be essentially

29:18

what we've been saying for the AI for

29:20

poll requests where you're just dumping

29:22

AI into any of the given things.

29:24

is the thing everybody uses on GitHub, poll

29:27

requests. So let's dump some AI

29:29

into it and make it even better.

29:31

This is kind of neat. Right? So

29:33

you you often get poll requests. We have to do code reviews. You

29:35

have to pause through. You have to look

29:37

at issues. And this

29:39

says it's helping you review poll

29:42

requests of AI. See

29:44

how it

29:46

makes actionable suggestions for

29:49

improvements. You can just click to

29:51

accept. Okay. Sure. It's

29:53

like an instant AI driven

29:55

code review. That seems

29:57

really great, especially for,

29:59

you know, you work in big teams and

30:01

many times there's people submitting things

30:03

that don't fit maybe his coat

30:06

styles or using a variable

30:08

that already

30:10

got function that already exists somewhere

30:12

else or remaking something and maybe this is

30:14

going to step in in there and say,

30:16

hey, if you consider doing

30:18

this or perhaps You'll want to do this

30:20

instead. Who knows? How

30:22

this ends up looking? It's a work in

30:24

progress still at that stage. But again, a

30:26

lot of this is just using

30:28

AI and they're already given their

30:30

co pilot, which, you know, and I'll ask the functions

30:32

very well except for that one time it didn't put

30:34

me at the top of the Hance Miss developers.

30:37

And you gotta say I

30:39

gotta say it works. It's it's gonna be an

30:41

exciting world when some of the start stuff to

30:43

hit the early previews that you can

30:45

actually use. That's great. I think we should

30:47

have try to find out who

30:49

from GitHub we

30:50

can have on our

30:52

podcast to talk about. all

30:54

of this co pilot stuff because we'll look at

30:56

who is look just look

30:58

at who's in just about every single one

31:00

of these co pilot related

31:03

Things, Matt, Matt, Rothenburg.

31:06

Matt, Rothenburg. If you know Matt,

31:08

Matt, or Matt if you're listening, hit

31:10

us up. We'll hit up you and see if

31:12

we can get you on the show. Yeah. There's gotta

31:14

be. Gotta be somebody

31:16

listening. Or if not, we

31:18

will we'll try dick

31:20

amount. So this is some cool stuff.

31:22

Future cool stuff. We got a lot of it. That's one of

31:24

my favorite things we do here. We definitely see

31:26

future cool stuff. Maybe we should just

31:28

just ring in the podcast to the cool

31:30

stuff podcast. I would like it that actually. That's

31:32

pretty cool. That's cool stuff. I

31:34

could do that. Alright. I think that's it for

31:36

today. Thanks everybody for tuning

31:39

in. We will catch you on Wednesday.

31:44

Peace. Head on over

31:46

to syntax dot f m for a

31:48

full archive of all of our shows.

31:50

And don't forget to subscribe in your

31:52

podcast player or drop a

31:54

review if you like this show.