HomeVideos

I responded to the drama

Now Playing

I responded to the drama

Transcript

435 segments

0:01

So, I just got back from holiday. I was

0:03

in vacation in Cairns, which is in the

0:07

north of Australia.

0:09

I was enjoying myself.

0:11

Um going snorkeling, seeing the coral

0:14

reef.

0:15

Uh

0:15

I saw some turtles and other wildlife.

0:20

I went on I went on a helicopter ride.

0:23

And a bunch of other cool stuff. So,

0:27

I couldn't get back to everyone, but I'm

0:30

here now and uh

0:32

And also,

0:35

there were so many comments that it was

0:37

kind of overwhelming. And so, I'm trying

0:39

to respond.

0:41

There have been 1 million views on my

0:45

last video

0:48

titled I was laid off by Atlassian,

0:52

where I went into

0:53

a little bit of detail about what I

0:56

built.

0:57

And basically did a recap.

0:59

And drew up some pretty basic diagrams

1:02

to explain things as I went along.

1:06

And then I went into a few of the more

1:10

interpersonal

1:12

sorts of lessons that I

1:14

that I learned. Really just the ones

1:16

that came to mind.

1:20

A million views is a lot.

1:23

And I obviously wasn't expecting that

1:26

kind of

1:27

exposure.

1:29

You can see that my previous videos,

1:31

they had less than 100 each.

1:34

And so, this response has been

1:38

interesting,

1:40

to say the least.

1:42

This video is going to try to address

1:45

the majority of the feedback and the

1:47

comments.

1:49

But I wanted to say one thing first,

1:52

just to make sure it's very, very clear.

1:56

I worked at Atlassian for 8 years

1:59

and I did that because I enjoyed working

2:03

there.

2:04

I was sad to be laid off,

2:07

but I am not angry at Atlassian for

2:10

laying me off. They made a business

2:12

decision.

2:14

I don't know the criteria behind that

2:16

business decision.

2:19

And it doesn't It's none of my business

2:22

what they do. I don't have

2:25

an entitlement to continue working there

2:28

for as long as I

2:30

want. You know, it's their money at the

2:32

end of the day.

2:35

And Atlassian didn't throw me out into

2:37

the cold to fend for myself.

2:40

They gave me

2:42

a substantial payout along with everyone

2:45

else who was laid off,

2:47

which gave those people time to

2:51

think about what they want to do next

2:53

and and gave them a lot of breathing

2:55

room to do so,

2:57

including me.

2:58

And you'll notice that

3:01

I made this video 2 months after I was

3:04

laid off.

3:05

I haven't been working this whole time

3:07

and I don't have to work

3:10

for

3:12

many more months if I don't want to.

3:16

So, I hope that that's clear that there

3:18

is

3:20

no anger

3:22

or vengeance

3:24

or anything else like that

3:26

uh

3:27

in the video that I made.

3:29

I don't have any kind of negative

3:30

feelings towards Atlassian.

3:33

I'm still keeping in touch with my

3:35

teammates.

3:37

I I really have nothing bad to say about

3:39

Atlassian.

3:43

Anyhow,

3:45

moving on, let's talk about

3:48

the comments on that video.

3:51

I tried to sort of group things into

3:54

categories,

3:57

but they may not be as granular as

4:00

people may like.

4:02

So, I'm probably going to try to just

4:05

pick out the very specific comments and

4:08

respond to them directly.

4:11

Um I may potentially make uh short-form

4:15

content to respond to some of them if I

4:18

think that the answer is interesting to

4:21

many people.

4:24

But, let's sort of start from the top

4:27

in a in a way.

4:29

>> [snorts]

4:30

>> For some people, it was unclear what my

4:33

level of education

4:35

and seniority was, what title I had, and

4:39

how much I was getting paid, and all

4:40

this kind of stuff.

4:42

Uh I have never been to university. In

4:44

fact, I didn't really finish high

4:46

school. I stopped after the 10th grade,

4:50

>> [snorts]

4:50

>> and I started working.

4:52

I started my tech career in help desk,

4:56

and I at some point taught myself how to

5:00

program in

5:01

PowerShell. Uh actually, I started with

5:03

Windows and PowerShell.

5:06

I then moved on to Python.

5:08

During the time that I was building up

5:10

the skills in my tech career, I had no

5:13

mentor myself. I had no one was teaching

5:15

me.

5:16

Uh I used books and videos

5:20

uh of other talks

5:23

uh as well as exercises and courses and

5:27

sites, wherever I could,

5:29

to learn what was relevant to me at the

5:32

time, and just to increase my skill in

5:34

general.

5:35

When I joined Atlassian, I was uh

5:37

systems engineer,

5:39

and after I delivered the

5:42

edge load balancing

5:44

project that I spoke about,

5:46

I was promoted to a senior systems

5:49

engineer.

5:50

So, I did not start as a junior or a

5:53

graduate. So, hopefully that answers um

5:56

a little bit about my title, my

5:58

experience,

6:00

the fact that I I've not been to uni. I

6:02

had very little schooling.

6:05

And I I mostly taught myself. So,

6:07

hopefully that's clear.

6:08

If you got any other questions about

6:10

that, just let me know.

6:12

The second thing is

6:15

I've noticed

6:17

uh people asking if I violated an NDA, a

6:20

non-disclosure agreement,

6:22

or if I am at risk of being sued, or

6:25

anything like that. I've noticed it on

6:28

social media broadly, but and and also

6:30

in the comments.

6:32

The detail

6:35

and the content that I shared is

6:37

something that

6:39

a typical

6:42

speaker would share at any tech

6:44

conference.

6:46

There's actually blogs posted

6:49

on the Atlassian website that have more

6:51

detail than what I shared in my video.

6:55

And in fact, me and my colleague who

6:58

wrote such blogs and published them.

7:03

Planned to talk about the stack in even

7:09

more detail than what I shared at the

7:12

Envoy conference that was just recently

7:14

in Japan, which we both unfortunately

7:17

did not get to go to

7:19

because we didn't really have the time

7:22

to write up a talk,

7:24

especially since uh my employment ended.

7:28

So, for people that are more

7:30

experienced, it's very clear that I

7:32

haven't broken any kind of

7:35

NDA and that I haven't shared real

7:37

confidential information because there's

7:40

There's not enough detail in what I

7:42

described for it to reveal anything

7:45

confidential.

7:47

So, hopefully that is clear.

7:49

Uh some people gave me

7:52

tips about my microphone placement.

7:55

Uh as you can see, I have changed the

7:58

direction of my mic so that the top of

8:00

the microphone is now facing me.

8:03

Hopefully, this is delivering a nicer

8:05

clarity to you.

8:08

So, thanks for the tip.

8:10

A decent number of comments said that

8:12

the video that I

8:14

made

8:15

gave

8:18

educational content that was perhaps

8:20

better than university courses or

8:23

paid boot camps or something like that.

8:26

I don't know. I've never been on any of

8:29

those courses, so I don't know exactly

8:31

how valuable

8:32

the educational material is in those.

8:36

I'm not sure if I would

8:40

be able to take my last video and

8:44

meaningfully

8:46

apply it to a real business problem.

8:49

It was really just a recap in my view,

8:52

but I could be wrong.

8:55

Uh either way, I'm glad that it was

8:59

interesting and valuable. This is

9:00

actually really surprising to me

9:03

and very validating because I thought

9:06

maybe most people would find it quite

9:10

boring

9:11

unless they were specifically in

9:14

I guess the niche that I thought I was

9:17

in.

9:18

A lot of you said that you appreciated

9:21

the

9:23

breakdown of um Envoy and Sovereign into

9:27

the diagrams that I shared. I'm super

9:30

glad that uh that you liked that and

9:34

that just encourages me to make more.

9:37

Um so I'm going to think and plan about

9:40

exactly what kind of educational content

9:42

I'm going to create

9:45

in future.

9:46

Some of you said you were interested in

9:48

seeing me build something from scratch.

9:50

I'm definitely going to do that.

9:54

Uh, the plan that I have for that

9:55

actually is that I'm going to build a

9:56

control plane from scratch.

9:59

Mainly so you can see how easy it

10:01

actually is. So, I'm going to build a

10:03

control plane in three ways.

10:06

First, in Python.

10:09

Uh,

10:11

in a very basic way

10:12

that just is going to do a uh fetch

10:16

and a response.

10:19

Then I'm going to use uh some other

10:22

languages and stacks to show you how

10:26

advanced it can get if you're

10:29

you know, operating at a higher scale

10:32

where certain efficiency

10:34

is more meaningful.

10:36

Uh, a lot of people that are more on the

10:38

junior or student side appreciated the

10:42

video and they said that I would make a

10:46

good mentor and I really appreciate

10:49

that.

10:50

Um, I'm going to try to

10:53

sort of asynchronously mentor

10:57

all of you

10:58

uh

10:59

with future content if I can.

11:01

There was some very, very valid

11:03

critiques

11:05

on the complexity

11:07

of the solution that I described.

11:09

Some of you questioned whether

11:12

microservices are a good choice.

11:16

Some of you questioned whether you need

11:18

to have

11:21

uh you know, a a broker and a control

11:23

plane and ASGs and EC2 servers and why

11:28

not just use Kubernetes and why not do

11:31

this?

11:32

Yeah, completely valid.

11:35

I would say this in response.

11:38

The stuff that I recapped was close to a

11:41

decade ago. If I had to build it today,

11:44

I would build it differently.

11:47

Maybe it would be on Kubernetes. I'm not

11:49

sure. I would have to do experiments to

11:52

figure out what is the best approach

11:55

given that it would have to integrate

11:58

with a whole bunch of other things that

11:59

are

12:00

pre-existing.

12:03

When we're talking about building stuff

12:04

from scratch, if you if you could just

12:06

build your company from scratch and give

12:08

it the best architecture ever,

12:11

then maybe

12:13

maybe it would be super easy just spin

12:15

up Claude

12:17

and 58 it

12:19

10 billion agents and

12:21

just build the most

12:24

perfect architecture ever. I actually

12:26

don't think there is a perfect

12:27

architecture. I think at all times you

12:30

are making trade-offs, whether you're

12:31

aware of them or not. I think it's

12:33

better if you are aware of the

12:35

trade-offs you are making cuz otherwise

12:38

you have no idea what's going on and in

12:40

future you will run into problems that

12:42

you did not anticipate.

12:45

I can talk about how I would build it

12:47

today.

12:48

It would be different. It would be very

12:50

different. I can talk you I can talk

12:52

about some of the things

12:54

that were painful which I didn't include

12:57

in that video.

12:59

And there was pain and struggle and

13:01

problems.

13:04

And

13:05

uh

13:05

those were a direct consequence of the

13:09

architecture that we chose. So, I can

13:11

talk about those things.

13:15

And I may do that in future.

13:18

But yeah, I just wanted to say that the

13:20

criticisms

13:22

that

13:23

ended up in the comments, a lot of them

13:25

very fair, very valid.

13:27

Absolutely no problem with that.

13:30

Some of you said that I reversed the

13:32

interview process by basically putting

13:34

out

13:36

you know,

13:37

pre-answering interview questions in a

13:40

video.

13:41

Yeah, this was all calculated, guys.

13:44

Like I I planned for it to go viral so

13:47

that everyone knows exactly what I've

13:49

built

13:51

8 years ago so that they can hire me.

13:53

Exactly. It's just I'm playing 4D chess

13:56

over here.

13:59

Some of you shared that watching the

14:02

video made you feel

14:05

deep impostor syndrome and that you

14:07

weren't at my level.

14:09

Um

14:11

To that, I would say

14:13

you're at a different stage of the

14:16

journey. There are people that I look at

14:18

who are younger than me that I think are

14:21

just

14:23

so much more intelligent, more

14:26

conscientious.

14:29

And so I feel the same way.

14:32

Uh I don't know. I don't think there's

14:34

really

14:35

I don't think there's a point to really

14:36

getting

14:38

uh

14:39

to feeling negative

14:42

as a result of comparing yourself to

14:43

someone else because

14:46

there's so much work to be done

14:49

that we

14:51

we need people. And if you're halfway

14:54

com- competent

14:56

then

14:57

I I don't see why you wouldn't be

14:59

welcome.

15:00

Like as long as you aren't making things

15:02

worse

15:04

than they were before. If you're making

15:06

things better, then I don't see why you

15:09

should care the about the delta between

15:11

you and someone else that you perceive

15:14

as being way smarter than you.

15:15

I I think it could just be that they

15:19

they've spent more time.

15:21

Um I don't think it's impossible for you

15:23

to learn the same things as them. So,

15:26

just try to stay positive and maybe look

15:29

at the

15:31

what you can do in order to get closer

15:33

and use them as inspiration, not as a

15:36

way of feeling defeated. A lot of you

15:38

commented on

15:42

my

15:44

prints that I framed. Thank you for

15:46

those comments.

15:47

It brings me joy.

15:50

Uh,

15:51

I like to joke that when I show up

15:53

on the uh

15:55

severity one incident call and they see

15:59

the picture in the back that every

16:01

everyone calms down because, you know,

16:03

this is fine.

16:05

But, uh yeah. Sorry, that was lame.

16:10

Um, also in terms of just YouTube in

16:13

general,

16:14

uh

16:15

uh some of you said you wanted to do

16:17

like super chats or whatever it was, uh

16:19

super donations. I'm not sure exactly

16:21

how that stuff works.

16:23

Uh, because I've only been posting on

16:25

YouTube for maybe a month.

16:27

Um, so

16:28

because of the views that came in

16:32

and subscribes and everything,

16:34

um I I have become eligible to be a

16:37

YouTube partner. So, I've applied for

16:39

that now and apparently it's in review

16:42

and it's going to take some weeks, maybe

16:44

a month or whatever.

16:46

So, um

16:47

that's where that's at. I think you

16:49

won't be able to

16:51

become a member or do any donation type

16:53

things until that point.

16:56

So, yeah.

16:57

So, anyway, that I think that covers a

16:59

lot of the feedback that I got in the

17:01

video. Um, if there's anything else

17:03

that's unclear,

17:05

uh I will be going through every single

17:08

comment on the last video and responding

17:11

wherever possible, unless it's something

17:13

generic, then I I might just like it and

17:16

move on.

17:18

And then I'm going to get to work on the

17:21

follow-up videos. I've got a few videos

17:23

planned,

17:25

but I have to

17:26

go do the work and create them. So,

17:29

thanks for your patience while I get

17:32

those up and running.

17:34

See you next time.

Interactive Summary

The speaker addresses the massive response to their previous video about being laid off from Atlassian, clarifies their professional background, responds to common questions regarding NDAs and their expertise, and discusses future content plans, including building a control plane from scratch and offering mentorship.

Suggested questions

4 ready-made prompts