HomeVideos

Worst Graph in the world | TheStandup

Now Playing

Worst Graph in the world | TheStandup

Transcript

1348 segments

0:00

Welcome to the standup. Today we have

0:01

two very special topics. And as always,

0:04

we have Tee DV, we have Casey Miratory,

0:08

and we have Trash Dev. All of them

0:10

legendary developers from the legendary

0:13

Twitter community here to talk about the

0:15

hottest and greatest parts that are

0:17

happening right now in tech today.

0:25

Uh anyways, sorry. The actual first

0:27

topic is going to have to be TJ Trash

0:32

and Casey guesses. What does LinkedIn

0:35

have to say? Now, I'm going to say a

0:37

phrase.

0:38

>> I had to fire Teach. Now, before I show

0:41

it to you, what is the LinkedIn

0:44

translation of I had to fire Teach?

0:46

>> What does this mean? LinkedIn

0:48

translation. Yes. Automatic LinkedIn

0:51

translator that takes my phrase

0:53

>> identifier

0:54

>> and transforms it into LinkedIn.

0:56

>> I've got

0:57

>> into like a five paragraph post.

0:58

>> Yeah, it's going to be really long. Like

1:00

um this is one of the hardest decisions

1:03

that we've had to make. Uh but the you

1:05

know the company is strong and this only

1:08

puts us in a stronger position. Uh Tee

1:10

was a very valuable employee and did a

1:12

lot of great things and we're really

1:14

looking forward to what he does next.

1:16

>> That's great. Trash. I was I was

1:18

thinking more of like something happens

1:19

in real life. So it's like I went to the

1:20

bagel store, but the bagel person ended

1:22

up burning my bagel, which somehow

1:24

reminded me of Tee burning down the code

1:27

at work, which made me realize and

1:28

reflect upon his recent performance. And

1:31

now I had to hash lay him off something

1:34

something.

1:35

>> That's crazy.

1:36

>> I I was going I was going more with TJ's

1:39

been my best friend since we founded

1:41

this company. We've been through hard

1:43

times. We've been through good times.

1:45

We've worked together. He came to my

1:48

wedding. I went to his. He's the

1:50

godfather of my child. Unfortunately for

1:53

him, it's time to grind even harder. #

1:56

grind #h hard.

2:01

And and so to do that in the age of AI,

2:04

I have an agent that says you are teach

2:07

and you are good enough to do exactly

2:09

what he did for me. So I laid off my

2:10

technical co-founder and we're shipping

2:12

10,000 lines of code today. buy my

2:13

course below to also ship like this.

2:18

Wow. All right. To tell you the truth,

2:20

it was in fact Casey who did the good

2:22

job. Today, I'm sharing one of the

2:24

hardest decisions I've ever had to make

2:27

as a leader.

2:29

>> I've had to part ways with my co-founder

2:32

Tee. Growth isn't always a straight

2:33

line. And sometimes the hardest part of

2:35

the journey is realizing when paths need

2:37

to diverge to protect long-term vision

2:38

of the company. It's about radical

2:40

canoandor making tough calls and staying

2:43

true to the mission. I'm incredibly

2:45

grateful for the lessons during this

2:46

chapter onward and upward. # leadership

2:49

#founderlife #growthmindset TJ that's a

2:52

TJ point and I

2:54

>> see I don't read LinkedIn so I didn't

2:56

know they were hashtag obsessed that I

2:58

totally miss that I totally miss that

2:59

>> love hashtags they love

3:01

>> Here we see the elusive programmer a

3:03

simple creature that spends most of its

3:05

time working alone often in darkness but

3:08

what's this someone being wrong on the

3:10

internet our coder springs into action

3:11

reaching top speeds of 120 words per

3:14

minute before flash a light mode website

3:16

the natural enemy of these code lovers

3:18

stuns our friend. The chase is called

3:20

off. We'll have to get them next time.

3:24

When not on their computers, they can

3:25

spend hours drawing crude symbols on

3:27

something they call whiteboards.

3:29

Researchers have discovered thousands of

3:30

dialects, often with more than a dozen

3:32

used in a single office. However, no

3:35

linguist has yet deciphered what their

3:37

purpose is.

3:40

Vein creatures, their bodies have

3:42

evolved over a millennia to be able to

3:44

sit in unusual postures while looking at

3:45

themselves online. This will often last

3:48

for many hours using the excuse they're

3:50

waiting for code review, depressed to

3:52

why they're so inactive.

3:54

And finally, after a long day of

3:56

accomplishing very little, our keyboard

3:58

warriors ready for bed. Quick read and

4:00

it's lights out.

4:03

Good night, little coder.

4:07

So, how do I sleep so well at night?

4:09

Well, I have sentry to help me crush

4:11

those bugs. And I'm not I'm not talking

4:13

about like little teen tiny South Dakota

4:14

bugs that die in the winter. I'm talking

4:16

about big mean jungle bugs and I'm not

4:20

scared of any of them by the way just

4:23

but I can squash those bugs with seer by

4:25

century. All right. Well, this was

4:27

inspired due to this post which was

4:30

unironically put on here which is

4:32

Michael and I are separating

4:33

romantically. We're not breaking up as

4:34

co-founders and we're not stepping away.

4:36

Dot dot dot. I never got THE ACTUAL FULL

4:37

THING.

4:38

>> NO, THIS ACTUALLY HAPPENED.

4:41

>> NO, THAT'S NOT REAL.

4:43

>> That is real.

4:45

>> Quick question. Did that guy happen to

4:47

make an app about tracking when your

4:48

wife leaves the dishes in the sink?

4:53

Yes.

4:55

>> Oh my gosh.

4:58

>> I love the idea of of like instead of

5:00

instead of saying I broke up or we're

5:02

getting divorced, it's like uh we're

5:04

announcing a change in our chief bedroom

5:06

officer,

5:11

>> the CBO. We we ARE WE ARE CURRENTLY

5:14

GOING INTO A PHASE where we're going to

5:16

search for our new uh chief bedroom

5:19

officer. We have a lot of promising

5:21

candidates. We want to make sure we find

5:24

the right match.

5:25

>> I plan on interview sound a lot more

5:27

professional

5:27

>> in the next six months.

5:28

>> Yeah. Yeah,

5:29

>> dude. That's the new Tinder pickup line.

5:31

Looking for a CBO.

5:32

>> Yeah, looking for a CBO.

5:35

>> All right. Someone else like I like

5:36

that. I like that.

5:37

>> I'm I'm I'm serving as interim CBO right

5:40

now.

5:43

But it's not it's not long-term,

5:46

>> man. That interview process is crazy.

5:51

>> I am avoiding saying anything. I

5:55

>> smart. Next topic. Quick. Quick.

5:57

>> All right. So, we're going to actually

5:58

get to the real first topic of the

5:59

standup. I saw somebody on the internet

6:02

post this right here. It's the

6:04

complexity visualizer. Now, this was

6:06

posted by STEM explorer. I presumably a

6:10

Twitter account about exploring STEM

6:12

>> and they

6:12

>> like the like the thing in the flowers.

6:15

>> Yes. Uh kind of

6:17

>> TJ reached deep for that pun cuz it was

6:19

it was okay.

6:22

>> Uh and so they gave us a complexity

6:24

visualizer big O notation race in which

6:28

they have O of one O of N O N log N^ squ

6:33

and then of course 2 to the N kind of

6:34

like your classic situation. Now, this

6:36

reminded me immediately of when Casey

6:39

had an absolute meltdown on the internet

6:41

over the ball diagram.

6:42

>> We had several videos. We had

6:44

>> This is actually worse.

6:46

>> This is actually worse.

6:48

>> I didn't know it could get worse than

6:50

the balls.

6:51

>> Well, it's kind of There's two different

6:52

things. So, the meltdown over the ball

6:54

video. I mean, obviously, like I always

6:56

criticize ball videos.

6:59

>> Classic known ball criticizer.

7:01

>> Yeah. uh when developers feel the need

7:03

to show their balls off to the entire

7:05

world like that and I'm just I'm just

7:07

sitting there going like

7:08

>> that's a job for the CBO. Am I right,

7:10

boys?

7:10

>> Yeah, exactly.

7:12

Um, chief ball officer.

7:15

>> Uh, well, internet chief ball officer

7:17

Ben Dickin, who at this point is now

7:19

infamous for these ball diagrams and

7:21

loves it, by the way. like he as far as

7:23

I can tell he is he is leaning into the

7:25

balls

7:27

>> uh and and uh cuz you know he posts them

7:30

to get to get engagement like that's he

7:33

you know he's trying to do uh he's he's

7:35

trying to

7:36

>> get a

7:37

>> to get people to interact with his uh

7:39

social media and so like you know people

7:42

people saying these are awful is just as

7:44

good as people saying they're bad I

7:45

assume I don't really know but anyway

7:48

the problem with those ball diagrams

7:51

Are you fundamentally opposed to men

7:53

leaning into ball diagrams?

7:55

>> No, what I'm saying is that he was

7:58

leaning into it. I'm not making a value

7:59

judgment. If a man wants to lean into

8:01

their balls uh or or anyone's balls uh

8:05

at on social media, that's entirely up

8:08

to them in my opinion. I don't think

8:10

that we should be telling them what to

8:12

do or not to do. That's my opinion.

8:14

That's just my opinion. Um and I'm

8:16

sticking to it. So anyway, my problem

8:18

with the balls was that they're a bad

8:20

way to visualize data. A but the reason

8:24

but that happens a lot. So that there's

8:26

a lot of people who post their balls on

8:27

the internet and it's just like okay

8:30

this maybe the thing that they were

8:31

posting was actually fine. They happen

8:33

to want to show you their balls instead

8:36

of just putting the data in a better

8:37

format. And I'm just like, could you not

8:39

do that? Because it's a really it's I

8:42

understand it's eye-catching and that's

8:43

why you're doing it, but it's a very bad

8:45

way to visualize data. And like there's

8:47

even like you can literally go find

8:49

studies people have done where they've

8:51

looked at how people like react to

8:54

different ways of pres presenting data.

8:56

And motion is like one of the worst

8:58

things to use to try and get people to

9:00

conceptualize the differences between

9:02

things. Like humans are horrible at

9:05

comparing like the rate of movement of

9:07

things as compared to just the sizes of

9:10

them, right? So

9:12

>> that makes sense.

9:13

>> Yeah. So it's just a bad idea for a

9:15

chart. It's only good when you're trying

9:17

to bait social media engagement, which

9:19

to be fair, like I said, I think Ben

9:21

Dicken knows. So he's kind of off the

9:22

hook in a sense for that part of it. So

9:25

really, because that's what he was

9:26

trying to do, and that's fine. The

9:29

reason I was so grumpy about those is

9:30

because the data was wrong. like the

9:33

thing that they were Ben Dickens data is

9:35

usually also wrong, right? So he makes a

9:38

repository, he invites people to

9:40

contribute to the repository, the

9:42

contributions are terrible, generally

9:44

speaking, they're just all over the map

9:46

and then he graphs them as if they

9:47

compare like language performance, but

9:49

they don't at all, right? Um, and so

9:52

it's just not like it's it's bad. It's

9:55

misleading. And that's why I get upset

9:57

about that. the balls are kind of, you

10:00

know, uh, insult to injury, if you will,

10:03

like, oh, now I got to look at balls

10:04

while I see this bad data. It's like,

10:06

you know, just makes things worse. So, I

10:09

wanted to clear that up first. This is

10:12

something completely different. This is

10:15

like they posted a graph that literally

10:18

doesn't show the thing at all.

10:23

>> It is very, very true. I've been

10:25

struggling trying to figure out the

10:26

meaning behind it for a long time.

10:27

>> Prime was so tilted when he was like

10:29

we're saw the first one and I was just

10:31

like I stopped looking. Like constant

10:32

time is just a wave like this. I'm like

10:34

what? It should just be like a line,

10:35

right? Like what? I don't understand at

10:37

all.

10:38

>> I have no idea what it's even graphing.

10:40

Like I have literally no idea.

10:42

>> None. I don't know how they I don't know

10:44

how they came up with

10:46

>> complexity visualized. Casey says right

10:49

on the ground.

10:50

>> It says right there, Casey. It's pretty

10:51

obvious. read.

10:53

>> Well, I mean, you know, if I can't see

10:55

because of course, you know, this is

10:57

Riverside and so being able to see the

10:58

thing,

10:59

>> I can't read I can't read any of that.

11:02

>> Yep.

11:02

>> Uh but like what's the top one? O1 is

11:06

supposed to be right.

11:07

>> And what's Okay, so so 01's

11:10

>> it goes really

11:12

>> what's the next one?

11:14

>> Uh log N

11:16

>> log N. And the next one is N log N maybe

11:18

or

11:19

>> No, it's just N.

11:20

>> This is linear.

11:20

>> Oh, okay. Okay, we skipped n login. All

11:22

right,

11:22

>> then n login. No, then n login cuz it's

11:24

slower, right? Theoretically, it's

11:26

slower.

11:26

>> Then n squ and then 2 to the n. So each

11:29

one is like progressively worse by an

11:31

order of complexity.

11:33

>> Understood. Okay.

11:34

>> With a couple complexities skipped.

11:36

>> So the more squiggles, the worse.

11:39

>> Yeah. The more so how long it takes to

11:42

move from one side to the other. But the

11:44

squiggles are useless.

11:46

>> Yes, correct. The squiggles.

11:49

>> What I was trying to do is count them.

11:50

I'm like, do the do the squiggles even

11:52

go in a pattern that has to do with like

11:55

what the N was? And it doesn't even look

11:57

like that. Like I could

11:58

>> very difficult because they erase the

12:00

squiggly. So if you were supposed to

12:01

deduce the squiggle density, it's being

12:04

erased actively.

12:05

>> Actively because like the top one, so if

12:07

that's 01, then the constant would have

12:10

to be like three, right? Because there's

12:12

three squiggles. So and we know that N

12:15

is one. So you know the constant would

12:18

have to be three. If the next one is log

12:20

n, right? We assume the constant is

12:23

still three pro. I mean, I guess there's

12:26

no reason to think that the constant

12:28

would still be three, I suppose. But I'm

12:29

just I'm just trying to figure out is

12:30

there any way to make this line up? I

12:32

suppose you could say, well, the

12:33

constant changes at each time, and

12:35

that's where the squiggles I I don't

12:36

know. I I literally don't know. I can't

12:39

figure it There's no way any thought

12:40

went into.

12:40

>> So the thing that really just grinds my

12:42

gears is that constant time

12:45

theoretically it does not matter upon

12:47

the input,

12:48

>> right? It's just about whatever the

12:50

coefficient is next to the constant

12:51

time. That really dictates

12:52

>> constant part and constant time.

12:54

>> That's the constant part and constant.

12:55

And so the fact that it takes about half

12:58

the speed as log n really bothers me

13:01

because constant is a fixed kind of like

13:04

operating time whereas login depends on

13:06

how much input there is.

13:07

>> Yeah. Yeah.

13:07

>> And so you can't actually make any sort

13:09

of relational guess between constant and

13:12

log. But in this one they're saying it

13:15

it's about 60%.

13:19

>> That kills me on the inside.

13:20

>> Right.

13:22

>> On average constant time is about or

13:24

login time is about 60% as fast as

13:27

constant time on average.

13:27

>> 50% of the time every time.

13:29

>> Yeah. Like on average.

13:30

>> It really hurts me so so much. And then

13:32

the the then the other part that really

13:34

gets me is that at the very end when

13:37

they're kind of finishing everything up,

13:38

uh, two to the end, exponential time and

13:42

quadratic time, exponential times like

13:44

20 or 15% through and quadratic time is

13:48

like 95% way through.

13:50

>> Yep.

13:50

>> And so it's just like that is not true

13:52

even in the slightest, right? It's like

13:54

at at n of 10,

13:56

>> exponential time is 10 times larger. At

13:58

n of 11, exponential times 100 times

14:01

larger than n squ. At 12, it's a

14:03

thousand times larger. Like none of this

14:06

makes any sense. Just driving me just

14:07

completely insane.

14:09

>> This has to be AI generated. There's no

14:11

way.

14:11

>> I assume it is.

14:12

>> Well, they wrote code to generate the

14:15

>> Oh, did they?

14:16

>> This is not AI generated in the sense

14:18

that someone came up with this idea and

14:20

told AI to generate it. I am so positive

14:23

that if you told AI like, "Hey, generate

14:25

the differences between these times,"

14:26

>> it would have done a standard graph.

14:28

>> It would have been more accurate. It

14:29

would have been this

14:30

>> right here. Exactly.

14:32

>> Yeah.

14:33

>> Exactly.

14:34

>> Yeah.

14:35

>> Which this I I'm looking at that I'm

14:38

looking at it

14:39

>> and I'm like, "But which one takes

14:40

longer?"

14:41

>> I can't even tell because where's the

14:43

ball moving across the screen?

14:45

>> I can't even tell.

14:48

>> Oh my gosh. Sorry. I was I was just so

14:50

>> but that's kind of the point te right

14:53

like so one of the important things

14:56

about complexity is that it doesn't tell

14:58

you how long something takes you can

15:00

have an 01 algorithm that takes a lot

15:03

longer than an algorithm for some n

15:07

>> this is true classic array versus uh set

15:09

lookup when you're doing stuff

15:11

>> this is just how it is and so the that's

15:13

the point of understanding like if you

15:17

try to convey to somebody that O is

15:20

faster than O N log N or something like

15:23

that, you're conveying incorrect

15:25

information because it's not faster or

15:26

slower. It scales worse, right? There's

15:29

a difference between those things. And

15:31

so you need like even showing anything

15:34

that implies that there's a speed

15:36

difference between them is wrong just

15:38

right out of the gate because complexity

15:40

is not about telling you how fast

15:42

something ran. And that's critical to

15:45

understand. It's so critical that

15:47

actually in in shipping code in

15:50

deployment sometimes you will use

15:52

algorithms that have worse scaling

15:55

complexity when you know what the n is

15:57

because the scaling complexity doesn't

15:59

matter because the n is low and the

16:01

constant's too high on the scaling

16:03

version right on the on the lower

16:06

complexity. So you can have times people

16:08

deploy an n squed algorithm instead of

16:09

an n login algorithm. You can have

16:10

people deploy an n login algorithm

16:12

instead of an no algorithm and so on and

16:14

so forth. That will absolutely happen

16:16

not because the person didn't know what

16:17

they're doing but because that was

16:18

actually the right choice for the scale

16:20

of problem they were working on. A quick

16:22

classic example, quicksort. Often for

16:24

the last few elements, we'll switch to

16:26

insertion sort because it's actually

16:28

faster to not quick sort on a bunch of

16:30

small items due to the stack invocation

16:32

and recursion cost comparatively to the

16:35

n squared algorithm worst or standard

16:37

case average case of insertion sort.

16:41

>> I didn't even know that. Uh well quick

16:42

sort quick sort's n squed

16:44

>> uh quick sort worst case is n squed

16:46

quicksort average case is and login and

16:48

so often inside of those also with merge

16:51

sort you'll break into an insertion sort

16:53

at the very bottom because it is just

16:54

better

16:55

>> and so there's a classic example where

16:56

scaling actually doesn't

16:58

>> you know is is traded off in the middle

17:00

just because of size.

17:01

>> Wow. I was thinking too prime of like uh

17:04

when we talked to Tiger Beetle a while

17:06

ago of how they like all of their like

17:10

so many places in the code they have

17:11

like some assert about the size of how

17:14

big something can be because they're

17:15

also like loading all of it ahead of

17:17

time and others but so it's like you

17:19

just say hey I think that this thing

17:20

should never get over 200 elements or a

17:22

thousand elements like it's cool because

17:25

then you can pick something that works

17:26

really good where n is less than a

17:28

thousand and it's like it's really fast

17:30

at that thing and then later if that

17:32

invariant breaks, you find out cuz you

17:34

have a debug failure or like some

17:36

warning or something that happens in

17:38

your system that can then you're like,

17:39

"Okay, cool." So now apparently we have

17:42

big enough customers that a thousand

17:43

isn't always the case. Sometimes it's

17:44

like 10 million for some reason or

17:46

something. We have some pathological

17:47

customer that does this. So then we got

17:49

to go fix that separately, which I

17:51

thought was really cool.

17:52

>> This actually John Carmarmac does.

17:55

>> John Carmarmac, if you don't know, does

17:56

the exact same thing in Doom and a bunch

17:58

of other places. he would assert like

17:59

the world can't have more than tw,000

18:02

items. That's just a that's just a

18:04

reality of life. We make all of our

18:05

decisions based off this one thing.

18:08

>> There's also cases where you know that

18:10

there's a limiting factor on the other

18:11

end.

18:12

>> Like for example, if you're like, look,

18:14

this thing is designed for 10 gigabit,

18:16

you know, Ethernet uplinks. So there you

18:19

go. like I know I know how much data is

18:21

flowing through this thing and it can't

18:23

ever be more than that because we don't

18:24

have you know and we're we will we will

18:26

fundamentally redesign this part of the

18:28

code if we switch to you know a higher

18:30

bandwidth connection or something like

18:31

that right or this screen like we know

18:34

that we're shipping on this console that

18:35

only supports 1080p so that's how many

18:37

pixels are on the screen like we know

18:39

that a particular region of the screen

18:41

can only have this many pixels so we're

18:43

making decisions based on that like so

18:44

you can definitely have situations too

18:46

where you even just know you're just

18:47

like look for the deployment scenario IO

18:50

we actually guarantee there is no

18:52

physical way that it can have a

18:53

different thing and at that point you're

18:55

free to make all kinds of decisions

18:57

based on n because you know what it is

18:59

but okay so then how do I know which

19:01

one's no I'm just kidding

19:02

>> so which one is faster

19:05

>> a lot of people like uh complexity is

19:08

one of those things where it's like the

19:10

um it's kind of a I guess since we were

19:13

talking about diagrams of and balls and

19:16

all that uh complexity theory is

19:18

definitely one of those things that I

19:19

feel is a just the tip kind of uh thing

19:22

in computer science where it's like do

19:25

you need to know complexity theory? A

19:27

lot of people ask this question, right?

19:28

Like do I need to know complexity theory

19:30

to like be a programmer? You absolutely

19:33

don't need to know complexity theory

19:34

because complexity theory is like forget

19:37

like okay you how do you prove something

19:39

is NP hard or something like like

19:41

actually knowing complexity theory I

19:43

don't know complexity theory. I don't

19:45

I'm not going to give you a dissertation

19:46

on pace or some like forget it right

19:49

it's not gonna happen.

19:50

>> Uh you do you do need to know yeah you

19:53

do need to know just the tip you need to

19:55

know like your basic like okay how do

19:58

algorithms scale with n roughly in terms

20:01

of how much memory they use and how much

20:03

like uh how how many concrete operations

20:07

whatever that operation is will they

20:09

have to do. That's something everyone

20:10

should know just for the basics like the

20:13

ones that were on this diagram probably

20:15

not exponential because almost nobody

20:18

uses exponential except in situations

20:20

where so this this may be getting ahead

20:23

of my out of my over my skis a little

20:25

bit but I would say that in general if

20:29

you're in the realm of exponential time

20:31

so you're thinking of things that are

20:32

like two to the n complexity or worse at

20:35

that point you may start wanting to know

20:38

more complexity like At that point,

20:40

you're in the in the realm of hardcore

20:42

algorithm design where you probably want

20:45

to know more than just the basics

20:47

because you're in you're going to start

20:49

needing to know things about heristics,

20:51

heristic based algorithms, randomized

20:53

algorithms, things that are like not

20:55

commonly thought about very much in you

20:57

know in work a day programming circles.

20:59

So once you are doing something that's

21:02

beyond n^ squ or n cubed and you're you

21:04

know out of polomial time at that point

21:06

you you may want to know more but

21:08

everything below that I'd say is a just

21:10

a tip situation.

21:11

>> Casey what happen if you have a a

21:12

salesman okay and he wants to start in

21:14

rapid city south Dakota. Okay, I'm

21:17

listening.

21:18

>> That's exactly what I That's exactly

21:19

what I was thinking of in my head when I

21:20

said that cuz like those kinds of

21:22

problems require a a deeper

21:24

understanding of of algorithm design and

21:26

the ways that we attack problems that

21:28

are sort of technically infeasible like

21:31

like theoretically you can't really

21:33

solve this problem efficiently. that

21:36

we've come up with lots of ways to, you

21:39

know, maybe not get the best answer, but

21:41

get a good enough answer that can be

21:43

used for humanity to do it whatever it

21:46

was trying to do. Can we prove uh that

21:49

we will we will get the best answer

21:51

every time? No. But we can get like

21:53

close, right? And that's you have to

21:54

kind of start to know uh that sort of

21:56

thing, right? Uh re by the way just I

21:59

know we're we're getting weird slightly

22:01

off but uh FedEx and uh UPS and USPS

22:05

they all have an actual uh NP problem

22:08

which of course is bin packing because

22:09

if you have x amount of boxes and you

22:12

have y amount of containers and you need

22:13

to be able to most efficiently pack

22:15

these boxes especially along a route now

22:17

you also have like multipplexing dystras

22:19

along with with bin packing. Very very

22:22

crazy. I mean they actually have a

22:23

really hard and interesting algorithm to

22:25

solve. I mean, even just basic things

22:28

like your your uh school. What is going

22:32

on, Prime? Oh my god,

22:35

>> that will literally break my teeth off

22:36

my mouth if I

22:40

crust on that Prime.

22:41

>> It was good. It was good. I just want to

22:43

taste it. You know,

22:44

>> now the heat's gone. If you just think

22:47

about like your local school district,

22:50

what the bus routes are and which order

22:52

they go in, that already is like there

22:54

are companies who specialize in solving

22:56

that problem because it it you need

22:57

heristic salt. Like you can't if you

23:00

even just the number of students in your

23:02

district being 500 or whatever it is is

23:05

enough to start to make it be like we

23:08

can't we can't guarantee you a perfect

23:09

solution. Like sorry like that's just

23:11

out of out of the bounds. So, we have to

23:14

do like things that, you know, take into

23:16

account that we have uh, you know, that

23:19

we don't have to get it perfect in order

23:20

for it to be good enough and and all

23:22

these other sorts of things. So,

23:23

>> at my high school, Casey, they they

23:24

wrote that down on the whiteboard. They

23:26

leave it overnight. See if anybody can

23:27

figure it out. Any janitors walking by?

23:29

>> Any janitors walking by?

23:31

>> Wait a minute. I've seen this.

23:36

>> Yeah. So, so we, you know, we always

23:38

look and I don't know. Last time I

23:39

looked at that sort of stuff, it was

23:41

kind of generally uh expected that look,

23:44

a lot of these kind of problems, you can

23:47

get very close to optimal solutions. You

23:49

you just there's certain like they have

23:52

these regions of their of their sort of

23:54

solution space that are just

23:56

extraordinarily hard. And so if the

23:58

input data happens to fall in those

24:00

areas, you are kind of screwed. If it

24:03

falls outside of those areas, then it's

24:05

okay. and you'll get, you know, you'll

24:07

typically get the solution you were

24:08

looking for, right? So anyway, my point

24:10

in all of that was just to say if that's

24:12

the kind of thing you're doing, you

24:14

should know, you should know more than

24:15

me about complexity at that point and

24:18

you should know more about than me about

24:19

like how you go about solving those kind

24:22

of problems with, you know, heristic

24:23

approaches, randomized approaches,

24:25

things like that because there's entire

24:26

theory of randomized algorithms. It's

24:28

very interesting actually, but it's like

24:30

I don't know it and a lot of programmers

24:32

don't know it uh because it doesn't come

24:34

up that often. Are you ready for Are you

24:36

ready for part two? So, can we say

24:37

goodbye to our squiggles? Our heart

24:39

heartbeat di We can all at least agree.

24:41

Heartbeat diagram terrible for

24:43

complexity visualization.

24:46

>> Yeah. I mean, I think what this really

24:48

is is an open challenge to Ben Dicken.

24:50

It was like

24:52

>> true.

24:53

>> We can like STEM Explorer has bested you

24:56

at every possible access. Not only is

24:59

the diagram even worse than the bouncing

25:02

balls, but it also is literally not

25:06

graphing anything even related to the

25:08

subject. Right? So I think that's why I

25:11

just reposted this and I think I said

25:13

something like your move Ben Dicken

25:15

because I feel like I feel like at this

25:17

point he has been so thoroughly

25:19

dethroned

25:21

>> that like he needs to come he needs to

25:23

come back and hit hard here because

25:26

>> I standard ball diagram is not going to

25:28

do it. Like he has been shown up

25:31

>> like significantly and it's gonna it's

25:34

going to be sad if he comes out with

25:36

something and it's not good enough to

25:37

get on the pod, Ben. Okay. So Ben, if

25:39

you're out there listening, we need

25:41

something big from you. All right, the

25:42

squad here, we're looking Q1 that's

25:46

going to be you have to deliver by the

25:48

end of Q2, but we need it in Q1 at the

25:50

very, you know, that's kind of what I'm

25:51

targeting. The world is Dickens.

25:55

>> They want to see your response to this

25:57

cuz STEM Explorer came out of the gate

25:59

here first time and just absolutely

26:02

crushed it.

26:04

>> I'm having a Dax moment over here.

26:05

>> You are. The one thing I will say about

26:07

the ball diagram, whether you hate it or

26:09

not, if the data was accurate, at least

26:11

there was some level of like meaning you

26:14

could kind of gather from it and go,

26:16

"Oh, yeah. I can see this one's slower

26:18

and that one's faster by how much and

26:20

all that." You couldn't really gather

26:21

this one. I can't gather any there.

26:23

There's actually no information here.

26:25

>> Why Why are the squiggles erasing on

26:28

>> I was I was I was going to try to spend

26:30

a moment to say that. I It really

26:32

bothers me that they end.

26:33

>> They're getting vacuumed up. Yeah,

26:35

there's no budget. There's no budget for

26:37

uh to keep them going.

26:38

>> I just really hate that they break at

26:40

the end like that,

26:42

>> right? Like I mean there's because it

26:43

does it with each one of them. As they

26:44

get to the end, it like wigs out.

26:47

>> Oh no, we've

26:49

>> Oh no, that's the I'm done merc. That's

26:51

like I finished.

26:54

You know, on the standup, we like to

26:56

come together and discuss some things

26:58

that very important people say that make

27:02

everybody else super upset. And this is

27:05

just one of those moments where what

27:06

I've just read somehow is the most

27:10

infuriating complic I've ever received.

27:13

And I'm sure many people have ever

27:14

received in their lifetime. And of

27:16

course, I'm talking about Mr. Sammy

27:17

Jippity Alman right here saying, "I have

27:20

so much gratitude to people who wrote

27:23

extremely complex software character by

27:25

character. It already feels difficult to

27:27

remember how much effort it really took.

27:30

Thank you for getting us to this point."

27:36

But okay, so

27:38

>> for the boys,

27:40

>> pack it up. We are done. Uh but I do I

27:44

really do love this idea that there is

27:46

no more complex software because it

27:47

hidden in this statement is that there

27:50

like software complexity is now

27:51

officially over.

27:52

>> Solved.

27:54

>> It's actually solved.

27:56

>> That's why cloud code doesn't flicker

27:57

anymore, right?

27:59

>> This is why GTA 6 supposedly will

28:01

release this year. Like there is rumors

28:04

that it's that it's coming out

28:06

>> way. Yeah.

28:08

I mean I I don't it's it's like almost

28:13

this is this is similar. These two

28:15

topics are feel very related to me,

28:17

right? Because the previous one was like

28:19

let's have a competition to see who can

28:21

post the worst graph, right? Was like

28:23

kind of what that was, right? And this

28:26

it's like it seems like that AI people

28:28

are doing like let's have a competition

28:30

to see who like people will dislike the

28:33

most, right? like like how do I become

28:35

some someone that literally no one likes

28:38

at all? And it's worth noting that it's

28:42

like including your customers like a

28:45

like they don't even want to be liked by

28:48

the people who are using their software

28:49

or they don't know that like I mean

28:52

unless they're really this unaware that

28:53

they don't see how insulting that is to

28:55

even people who are actively using their

28:57

software currently. Um I just it's crazy

29:01

it boggle like I don't even know if I

29:02

have a comment on that. I don't know

29:03

what to say about this. It's like it's

29:05

shocking.

29:06

>> I've got a hypothesis, Casey, which is

29:08

that, you know, they sort of feel like

29:10

they already won. And you know how when

29:12

you beat a video game, you can play it

29:13

back on like expert mode or like we've

29:16

I've been playing Slay Spire 2, climbing

29:18

my ascension ras, right? And each time

29:20

it adds like more difficulty, right?

29:21

Like start with a curse, you don't heal

29:23

all the way, etc. Um I feel like this is

29:26

kind of like, okay, well, we already

29:28

made like a trillion dollars. Can we do

29:30

it now if nobody likes us? Right. So

29:32

that's like

29:32

>> Right. Right.

29:33

>> So they're they're heaping those things

29:34

on. They're like, I'm going to win

29:36

biggest company in the world on

29:38

Ascension 20 Open AI Edition. I think

29:41

that that's probably

29:43

>> So you think at the beginning like like

29:45

Sam Alman, you know, for this round of

29:47

starting a company, it like it popped up

29:49

those little like pick which card you

29:51

want,

29:53

right? And one of them was get a lot of

29:56

money from people, but nobody likes you.

29:58

And and he picked like that was the that

30:00

was the modifier that he chose to play

30:02

the whole thing on.

30:03

>> Exactly. Fair enough.

30:04

>> Right. And then like round one was like

30:07

it had three options. It was like start

30:09

a nonprofit to save the world with AI.

30:12

Then like later it was like okay here's

30:14

a few forks in the road. One was like

30:16

continue the nonprofit. Everyone likes

30:18

you trying to make something for the

30:19

benefit of humanity. Option two was make

30:22

A TON OF MONEY.

30:24

>> YEAH. YEAH,

30:25

>> DUDE. When I read this tweet, I had like

30:27

a visualization in my head as like as I

30:30

was reading it as him like saying this,

30:31

but he was escorting like some old

30:33

person off the stage like kind of just

30:35

giving him this backhand comment and

30:36

then just kicking him off the stage and

30:37

then it was like let's here's the real

30:39

show kind of thing. Like cuz this is

30:41

stuff I tweeted this too, but this is

30:43

like the exact well at least my

30:44

emotional response was this is a message

30:47

of like when you lay somebody off like

30:48

thank you for all your hard work at the

30:50

company.

30:50

>> He LinkedIn posted it, bro.

30:52

>> Dude, like legit. And I was just like,

30:53

man, like when you're typing these

30:56

things, if he is the one typing these

30:58

things, like does he just hit send? Like

31:00

that's a good tweet. Like I don't I

31:02

don't

31:03

they're going to love that one. Like how

31:05

like what what is that scene look like?

31:07

I would love to just see like

31:08

surveillance of him posting this

31:10

>> and what he think is that he's I think

31:14

he and like Zuckerberg and a few of

31:15

these people fall into what is known as

31:17

the lizard category. And so I I

31:19

genuinely believe that he was just like,

31:22

"You know what? There was a lot of

31:24

people who I've taken all of their work

31:26

from and then making the biggest company

31:28

in the universe ever. I need to thank

31:30

those people. I'm going to thank them

31:32

right now. Here we go, boys." And like

31:34

got his team together like, "Okay, hold

31:36

on." Oh man, it was so complex. Step by

31:38

step. Oh my gosh. Hand coded

31:40

>> character.

31:41

>> But dude, it's like honestly it's hard

31:43

to even remember how hard that was. Does

31:47

he even know how hard it like does he

31:49

has he ever shipped anything that was

31:51

like a piece of

31:52

>> looped?

31:53

>> What is loop?

31:54

>> I don't know what that is.

31:55

>> Oh, okay. Pause.

31:57

>> I'll do I'll do a brown bag lunch on

32:00

this in a little bit. Okay. So, I'll

32:01

bring

32:02

>> You did brown bag world coin. So, I do

32:04

feel like you have to brown bag world uh

32:06

>> I'll brown bag looped for you later,

32:07

Casey. We'll we'll we'll bring you up to

32:10

speed on that. Make sure everyone brings

32:11

their own lunch, etc. Lunch will not be

32:13

provided. Just want to make that clear.

32:15

Uh but I will be providing a

32:16

presentation for that. Yeah.

32:18

>> All right. All right.

32:20

>> Yeah. I don't know. I This is just

32:22

really bizarre to me and it doesn't

32:27

So I I think I actually talked about

32:30

Dimmitri. I talked to Demetri about

32:31

something like this at one point. Um he

32:34

was obviously on the podcast last week

32:36

uh talking about AI stuff and

32:39

the way he said it, I don't want to

32:41

misrepresent him here, but he I asked

32:43

him this question. I was like given that

32:45

AI companies will face like a bunch of

32:48

lawsuits, regulatory hurdles, things

32:50

like this like societ they will run into

32:53

the bureaucratic elements of society and

32:56

they will have to navigate those right

32:58

um and and I'll point out they also will

33:02

have to navigate things that are worse

33:03

than that. So, uh, you know, I I don't

33:06

want to say anything that will get us

33:08

marked badly on YouTube, but let's just

33:10

say that like a data center is a pretty

33:13

easy target for civil unrest. I'll put

33:15

it that way, right?

33:16

>> True.

33:17

>> So, there's a lot of things that you

33:18

want if if you were really serious about

33:20

this. You're like, I want to make a

33:22

company that does this AI stuff and I

33:23

want to make sure that it succeeds and

33:25

does well. There's a lot of things you

33:27

would care about with respect to public

33:29

opinion and you would never say any of

33:31

the things that Sam Alman says ever,

33:32

right? If you were Sam Alman and you had

33:35

any self-awareness, you would not appear

33:37

in public. You would have somebody else

33:39

who was your person who appears in

33:41

public and it would never be you. That's

33:43

what you would do, right? Because nobody

33:45

likes him and when he opens his mouth,

33:47

he says things that make people very

33:48

angry. The in terms of the general

33:50

public, right? Not talking about

33:51

programmers or whatever. We're talking

33:53

about like the general public when they

33:54

hear from Sam Alman, they really don't

33:56

like it. He was recently just had

33:58

another one where he talked about how uh

34:00

if you compare the the cost of training

34:01

an AI to how much a human consumes, the

34:04

AI is actually better. Like no one

34:06

should ever say like if you care about

34:08

this as actually getting this thing

34:10

adopted, you would never say anything

34:12

like that, right? Yes. Because because

34:15

you should you should have someone out

34:17

there who understands how hum how actual

34:21

humans perceive things, right? Which is

34:23

not Sam Alman. That's that lizard thing

34:25

I was telling you about.

34:26

>> It's the lizard thing. You're right

34:27

about same Zuckerberg. They just they

34:29

have fundamentally no idea what a human

34:31

is like. Um even though they've seen

34:34

them before, they just aren't sure what

34:36

they do, right? They're like, "Huh?" And

34:39

so, uh, and so to me, I was like, why is

34:43

that? Like how does and how does no one

34:45

else step in and go like cuz I mean you

34:47

know when you're looking at a company

34:49

like OpenAI with these investors putting

34:51

billions of dollars in it. Someone would

34:54

in theory come along and be like uh Sam

34:56

thanks for all your hard work. You're

34:58

not going to be the they're going to

34:59

they'd palmer lucky him like they did at

35:01

Facebook right they're like you don't

35:03

get to talk to the public anymore. We're

35:05

you know we're replacing like that kind

35:07

of thing happens all the time for

35:09

reasons that are strictly about

35:10

appearances or public you know

35:11

perception.

35:12

>> What is that reference? I sorry I don't

35:13

know the Palmer Lucky thing at

35:15

>> Palmer Lucky uh well you know again

35:18

trying not to get into politics too much

35:19

Palmer Lucky was on the politically

35:22

wrong side of an issue early on when his

35:25

company Oculus was acquired by Facebook

35:28

now Meta uh they weren't obviously Meta

35:30

at the time because they were just

35:31

acquiring Oculus uh and he was basically

35:34

forced out of a leadership position

35:36

there and he ended up leaving the

35:38

company and that was purely

35:41

>> and he was the like to be

35:43

Wonder kid front of magazines super like

35:46

>> he was on the cover of Time magazine

35:48

>> everywhere like I do remember him being

35:50

>> the father of VR like everything he was

35:53

it wasn't just like oh like some random

35:55

guy got fired like he's he was the

35:57

wonder kid for them.

35:58

>> Yeah. He was like Jimmy Neutron is like

35:59

my ex expectation of him. He was

36:02

actually like a a very talented

36:03

individual that was like

36:06

>> way out there when it comes to talent

36:07

and building stuff.

36:08

>> Yeah.

36:09

>> Well, whatever you think about him, he

36:11

got forced out. Yeah, right. Like no one

36:14

disagrees with that. I don't think

36:15

that's not a controversial thing to say.

36:16

Like he did not voluntarily decide to

36:19

leave Facebook and their VR division

36:22

because he just wasn't feeling it that

36:24

day. He got for like he was forced to

36:26

leave uh the division that he was, you

36:29

know, that he had

36:31

>> that was his entire thing he wanted to

36:33

do. Like this was a thing that he

36:34

started in his bedroom doing, right? He

36:36

wanted to see if you could use phone

36:38

displays and stuff like that to produce

36:39

a real VR headset. Now, was the

36:40

technology ready? Right. And here he was

36:43

getting the opportunity to do that and

36:44

he got forced out for political reasons.

36:47

>> So something as simple as that, you can

36:49

force someone out.

36:50

>> They're not forcing Sam Alman out,

36:52

>> right? Nobody's telling Daario just to

36:55

keep his mouth closed, right? Like

36:56

that's not happening.

36:58

>> And so

37:00

are pretty funny these days.

37:01

>> My question was why? This is what I was

37:04

asking. I asked me I was like why? Like

37:06

what's going on there? because surely

37:08

the investors realize that it's better

37:11

uh for this, right? And what he said was

37:16

possibly somewhat convincing actually.

37:18

What he said was they have two choices

37:21

is what he said to me. One is they

37:25

garner public support or the other is

37:28

they garner investor support and they

37:30

went with investor support. And what he

37:32

meant by that was

37:34

>> if you tell a story about how AI is just

37:37

going to be beneficial for everybody and

37:39

that people won't be losing their jobs

37:40

and that it will just be like oh it'll

37:42

be easier to get your work done or

37:44

whatever it is whatever the publicly

37:46

we're just empowering artists were not

37:48

taking their jobs that can't raise the

37:51

level of investment that you can from

37:54

private investors if you tell them

37:56

you're putting everyone out of work. So

37:57

he said they had two choices. One was to

38:00

go and say that we're putting everyone

38:02

out of work and we're basically going to

38:04

be a pariah because everyone's going to

38:05

pay us and no one's going to pay anyone

38:06

else and raise their trillion dollars.

38:09

Or they could actually say something

38:10

positive, but they wouldn't be able to

38:12

raise that kind of money because it

38:13

doesn't sound like you're replacing the

38:14

entire industry with one computer and

38:16

they chose the one that gets them the

38:18

investment. And I was like, okay, that's

38:22

that's a pretty reasonable that's a

38:24

pretty reasonable way to say that that

38:26

could very well be the case. That makes

38:28

a lot of sense.

38:30

>> So you don't think about it that way at

38:32

all.

38:33

>> So you Well, this is why it's great to

38:35

talk to Demetri, right? It's why it's

38:36

why I'm doing that podcast is because he

38:38

has a lot of really interesting things

38:39

to say and he knows these people.

38:41

>> Yeah.

38:43

>> I'm just kidding.

38:43

>> He knows those people like he he's

38:45

interacted with a lot of these people

38:47

personally. He knows a lot of them in in

38:49

that field and so he has like some

38:51

perspective on why they do what they do.

38:53

It's like, yeah, so they could replace

38:54

Sam Alman with somebody who was much

38:57

more appealing to the public. And maybe

38:59

they will after they secure, right,

39:01

>> enough trillions of dollars. Then you're

39:03

like, okay, thanks. Thanks, Sam. Right.

39:06

>> Now, let's put a nice face on this thing

39:08

to try.

39:08

>> Then they hire Matthew McConna.

39:10

>> Exactly.

39:12

>> That's who I would hire.

39:13

>> Well, well, yeah.

39:14

>> I like DJ. All right.

39:16

>> Matthew McConna. That's the solution to

39:17

this thing.

39:18

>> I'm telling you, you guys seen him in

39:20

the Lincoln commercials? I mean, he

39:21

seems like a guy who you would trust,

39:24

>> you know? It's like that makes sense to

39:25

me.

39:26

>> I like Billy Bob Thorne. I trust him.

39:29

>> He could be like, he could be like, "I

39:30

don't stress." The mask behind could be

39:32

like, "I don't stress about it. I just

39:33

ask Chad GPT."

39:34

>> That's what I'm saying. You'd be like,

39:36

"He's so right, bro. He's so right. He's

39:38

so right."

39:39

>> So, just ask Chad GPT.

39:42

>> I Matthew McConna gets hired by OpenAI.

39:46

You guys are gonna You guys are going to

39:47

eat your words right here. Trash. Okay.

39:49

I mean, I love Matthew Mccane, too, man.

39:52

>> It's Matthew McConna AI.

39:54

>> Yes. He's going to legally change his

39:56

name.

39:57

>> Like like uh like um Oh, uh Will I Am

40:01

did right to the dots.

40:03

>> Oh, no. Will I Am

40:05

>> great, Casey. Nice pull.

40:07

>> Deep pull, right?

40:08

>> Remember when he made a smartwatch? No

40:10

one does. I do.

40:12

>> Uh Shakira, these chips don't lie.

40:19

COME ON. THAT WOULD BE A CRAZY I CAN'T

40:21

THINK of anything campaign.

40:23

>> That would be a crazy ad campaign.

40:24

>> Sitting here right now, I'm actually

40:26

slightly shocked that Will I am hasn't

40:28

announced an AI company. Maybe he has

40:30

and it just couldn't make it up. But

40:31

that would be so something he would do,

40:33

right?

40:34

>> Black eyed peas, right?

40:36

>> Originally, yes. But then he had his a

40:38

solo

40:39

>> Yeah. Yeah.

40:40

>> career. I was trying to make sure I'm

40:42

thinking of the same person.

40:43

>> Yeah. I have no idea who that is to tell

40:45

you the truth. Okay, I was a great

40:48

>> Prime. There's an era that you probably

40:50

missed out on because, you know, maybe

40:53

you're not quite as old as I am, but

40:56

>> there was an era where companies,

40:59

especially internet companies, uh, but

41:02

not exclusively, like companies like

41:03

Intel, for example,

41:05

had sort of brand ambassador positions.

41:09

And these were people who were like

41:11

enthusiastic about technology but didn't

41:14

really have all that much to do with it.

41:17

Will I am was one. Shingi. Does anyone

41:21

remember Shingi?

41:22

>> That sounds

41:23

>> say Chingi.

41:24

>> Nope. Shingi. He was he was an

41:27

experimental artist who was like a brand

41:30

ambassador for I can't I can't even

41:32

remember which company but a major

41:34

company like Huelet Packard or I don't

41:36

remember who it was but like and they

41:38

would produce these videos that were

41:40

just like you know them talking about

41:42

how cool technology is but

41:44

non-specifically this was a whole thing

41:47

that happened and there's more I'm not

41:48

remembering the world there's several

41:50

other celebrities who were like in that

41:52

vein and you're just like what is going

41:53

on but that was just it was cool for a

41:55

style in like the early 2000s to have

41:58

like this pseudo like it's usually

42:01

belist like it's not you know uh I'm not

42:04

trying to think of who the A-listers

42:05

it's not Jennifer Lawrence who is or

42:07

right it's not A-list celebrity someone

42:09

who's like launching a major motion

42:10

picture just below like B tier somebody

42:13

that people have heard of but is like

42:15

you know

42:16

>> prime like prime

42:18

>> dude that'd be so good dude I'd

42:20

definitely do that dude healer Patrick

42:22

>> and be like look at this printer

42:26

I got all these inks.

42:28

>> I got all the inks, BABY.

42:29

>> I GOT ALL THESE INKS.

42:31

>> Speaking of NAME COLOR. NAME A COLOR

42:32

RIGHT NOW. I GOT IT.

42:35

>> PRIME. Can I tell the story about what

42:36

happened on the call for nothing but

42:38

net?

42:39

>> Sure. I don't even know what the story

42:41

is, but you could you could

42:43

>> What does remind me of you saying Help

42:45

Packard and like we I'll call it HP and

42:47

you like not knowing acronyms. So, we're

42:50

doing an event next week with Sentry uh

42:53

in at the Chase Center, which is where

42:55

Golden State Warriors play. We have to

42:57

go to a game afterwards. We're going to

42:58

do something very fun. It's going to be

43:00

a surprise. Actually, we can't tell you

43:01

what our actual thing is. I'll tell you,

43:03

Casey afterwards. Um and trash.

43:05

>> Secret details. Sorry, chat. You're not

43:07

going to get to know this. Only I get to

43:09

know.

43:10

>> Yes.

43:10

>> And me and me.

43:11

>> Yeah. Or they have to come in person.

43:12

>> Trash. You might get kicked out.

43:14

>> Yeah. Oh. Um,

43:16

>> snacks he's provided.

43:18

>> We're like 15 minutes into the call with

43:20

them and there's someone from Golden

43:22

State on the call. Sentry's on the call.

43:24

Me and Prime are on the call. They've

43:26

said things like, you know, the GSW

43:29

staff will do this or like me, you know,

43:32

go through GSW this blah blah. They've

43:34

said the the acronym GSW about 35 times

43:39

at least. And we're 15 minutes into the

43:41

call and finally Prime goes,

43:43

>> "So what is GSW?"

43:47

>> Cuz I'm like, "Get [ __ ] one." Like I

43:50

kept saying in my head, "Get [ __ ] one."

43:53

I had no idea.

43:54

>> Yeah. Is that like graphics software or

43:59

>> Golden State Warriors?

44:00

>> I had no idea you guys were doing it

44:02

there. That's crazy.

44:03

>> Oh my goodness. And we're on the call.

44:05

Like you we've been talking about the

44:07

Warriors. We've been talking. It's not

44:08

like we were surprised about what NBA

44:10

team is at the place.

44:11

>> Golden State. What is the Golden State?

44:12

New Jersey. What is the Golden State?

44:14

>> SAN

44:16

I DON'T KNOW THAT ACRONYM. What's Golden

44:18

State?

44:18

>> Golden State. That's It's the San

44:20

Francisco team.

44:21

>> Golden State. Steph Curry.

44:23

>> Okay.

44:24

>> Golden State.

44:25

>> That's even better.

44:26

>> I don't know basketball at all.

44:28

>> That's fine.

44:28

>> Oh, I miss Oh crap. I missed my chance

44:30

again. I was supposed to say something

44:32

like I don't follow hockey. That's

44:34

twice. I missed an obvious setup. Damn

44:36

it. I thought you were going to say

44:37

something like, "I never watch moving

44:39

balls on the screen. I hate that crap."

44:41

>> Yeah, exactly. All these balls bouncing

44:44

bouncing people cannot comprehend Spade.

44:47

>> Yeah.

44:48

>> Uh,

44:48

>> all right. So, Golden State Warriors is

44:50

the San Francisco basketball team.

44:52

>> Yeah,

44:53

>> I believe so.

44:54

>> Possibly the greatest player ever.

44:56

>> Yes,

44:57

>> possibly. Okay,

44:58

>> maybe.

44:58

>> All right. So, I I do want to Hey, I in

45:00

my own personal defense, I would like to

45:03

say that we're ending the podcast. It is

45:05

one of my strengths that I am willing to

45:08

ask any question.

45:09

>> That part was good. I was proud of you.

45:12

I was proud of you that you asked even

45:13

though it was like awkwardly late into

45:15

the call. It was just it the

45:18

>> I thought I could just pick it up. I

45:19

thought I could just pick it up.

45:20

Honestly, I was like, "Oh, they used it

45:21

once. I'll probably get it the second

45:22

time. They used the second time." I'm

45:23

like,

45:24

>> I really don't understand it from this

45:26

context. Here we go. I have

45:27

>> it just cracked me up because it was

45:29

like just it happened to be if it was

45:32

just Sentry and not someone from Golden

45:35

State Warriors, I wouldn't have even

45:36

laughed or thought it was that funny.

45:37

But it was just because we had someone

45:39

from the org there. Correct.

45:40

>> That's like a record scratch moment.

45:42

>> Hey guys, if you like this episode, you

45:44

can watch the rest of it on the Spotify.

45:46

And don't forget to LIKE AND SUBSCRIBE.

45:48

WOO! See you later. Mood up the day.

45:54

V coating errors on my screen.

45:58

Terminal coffee

46:01

and

46:03

living the dream.

Interactive Summary

This developer standup features Casey Muratori, Trash Dev, Tee DV, and The Primeagen discussing a range of tech culture and engineering topics. They begin by mocking corporate LinkedIn jargon and the habits of programmers before diving into a deep critique of Big O notation visualizations. The conversation shifts into serious technical territory, exploring why theoretical complexity doesn't always equal performance and how top-tier developers like John Carmack use data scale to choose algorithms. Finally, they discuss the public perception of AI leaders and share a humorous story about a misunderstanding involving the Golden State Warriors.

Suggested questions

5 ready-made prompts