I don't think that the data centers as we know them are going to go extinct.
I think they will be around.
Welcome to Screaming in the Cloud.
I'm Corey Quinn.
Once upon a time, I was a grumpy Unix systems administrator because
it's not like there's a second kind of Unix systems administrator.
Then I decided it was time to get better at the networking piece.
So I got a CCNA one year.
Did this make me a competent network engineer?
Absolutely not, but it made me a slightly better systems person.
My guest today is coming from the other side of the world,
specifically someone who is in fact good at the networking things.
Serena, or SheNetworks, as you might know her
from TikTok, or NotSheNetworks from the Twitters.
Thank you for joining me.
I appreciate your time.
Yeah.
Thanks for inviting me on.
This episode is sponsored in part by my day job, the Duck Bill Group.
Do you have a horrifying AWS bill?
That can mean a lot of things.
Predicting what it's going to be, determining what it should be.
Negotiating your next long term contract with AWS, or
just figuring out why it increasingly resembles a phone
number, but nobody seems to quite know why that is.
To learn more, visit duckbillgroup.
com.
Remember, you can't duck the duck bill bill.
And my CEO informs me that is absolutely not our slogan.
So at a very high level, you are a network engineer and you specialize in
data center, compute and virtualization, which is fun because I remember
doing a lot of that once upon a time before I went basically all in
on cloud consulting and then sort of forgot that data centers existed.
That's still a thing?
That's, that's still going well and there are computers out there that
don't belong to one of the three biggest tech companies in the world?
Yeah, shockingly, there's still a ton of data centers
out there, still a lot of private hosting, and a lot
of the environments that we see are mixed environment.
They will have some cloud, some on prem,
but yes, data centers are still relevant.
On some level, it feels like once you get into the world of
cloud, you don't have to really think about networking anymore.
You know, until there's a big outage and suddenly everyone has to
think about the networks, but it also feels like it is abstractions
piled upon abstractions in the cloud infrastructure space.
How much of what happens in data centers these days maps
to what happens in these hyperscaler provider environments?
So I have two CCNAs.
I'm very familiar with networking.
I'm very familiar with virtualization.
And I went and got my AWS certification because, as
we're talking about, a lot of cloud things happening now.
It's, it's big.
It's good to know about it.
And underlying infrastructure under the cloud is all of the data centers
that I work with, all of the network working things that I work with.
So it maps very well to me.
I thought I had like a really easy time studying for my AWS
certification because a lot of the concepts just had like a
different fancy name for AWS versus just what you would know
as like NAT or, you know, DNS, different things like that.
Of course, NAT used to be a thing that was, everyone would yell at you.
It's not security, even though there are, I would
argue there are security elements tied into it.
But honestly, that feels like one of the best ways to pick
fights with people who are way better at this than I am.
Nowadays, of course, I just view NAT through a lens of, yeah, I
totally want to pay an extra four and a half cents per gigabyte passing
through a managed NAT gateway, which remains, of course, my nemesis.
The intersection of security, networking, and billing
leads to basically just being very angry all the time.
Yeah, you come into the field like so ready to go and
then sometimes you do get beat down, but it's worth it.
I think I, I really like what I do.
And what you do is something of an anomaly because most people who
focus on this world of data center networking and the security aspects
thereof and the virtualization stuff are all, How do I put it politely?
Old, grumpy, and unpleasant.
I mean, I guess I'm not going to put it politely because I'm
just going to be honest with it because I'm one of those people.
Let's be clear here.
Instead, you are creating a whole bunch of content on this on Twitter and
on TikTok, where I've got to say that the union set in the Venn diagram
between TikTok and deep dive networking and cybersecurity is basically you.
How did you get there?
To your first point, the, you know, old grumpy kind of stereotype, those
are honestly some of my favorite people, truly, because I don't know
what it is, but I just vibe with them in a work environment so well.
And it's funny, you know, when I got my first job out of
college, I was definitely the youngest person on my team by far.
And, um, I just, We would all go out to lunch.
I would mess with all of them.
We'd all play pranks on each other.
Just integrating into the teams was always super easy for me, which
I'm really lucky that not everybody has that experience, especially
in their first job, things are a little rough, but it's always great.
Like I love the diversity in tech.
And to your second point, how did I end up here?
Right.
With this kind of intersection from this networking, to Tik Tok.
People are always confused.
Like, how did that happen?
How are you finding followers on Tik Tok that are interested in networking?
And I'm just as shocked.
Honestly, I started making this content this time last year and You
know, at first I was like, nobody wants to learn about DNS on TikTok.
This is where people dance and play pranks and all this stuff.
And if you're dancing, when it comes to DNS, at some
point, something has gone either hilarious or terrifyingly.
Then again, I use it as a database, so who am I to talk?
Yeah, but It's been fun.
I am shocked, but there is such a wide variety of
people now using TikTok and it's growing so quickly.
Early on in my TikTok career, I had messages and emails from people who
were vice presidents at major fortune 100 companies asking me, you know,
if I'd be interested in working there or, you know, something like that.
And I was just like, I was so shocked because there was a company
that was a fortune 100 and one of their VPs joined one of my lives
and was asking me questions just about like my background career.
And then they sent me a follow up email to be like, Hey, so
I was like, did I just get interviewed on my live on TikTok?
And that, that always like cracked me up.
And at that point I knew I was like, okay, this is a good time.
This is something different.
Like, this is interesting because, you know, at the end of the day, you see the
views and the numbers and the followers, but you don't have really faces to put
to them or names and you don't really know where a lot of these people are from.
So you don't know who's seeing it.
And a lot of times I think I made the assumption that they're,
they're younger kids, which is true, but there are also a lot of
very seasoned professionals that have been in this field for a very
long time that also follow me and comment on my videos and add.
Great input and things like that.
There's a giant misunderstanding, I think, across the industry, that
the executives at the big, serious companies, you know, the ones
whose mottos may as well be, that's not funny, have no personality
themselves as people and that they live their entire lives, In this
corporate bubble where they, they talk to their kids primarily via,
I don't know, Microsoft Teams or Webex or something else equally sad.
And in practice, it just doesn't work that way.
They're human beings, too.
And granted, you have to present in certain ways in certain rooms.
But the idea that, oh, you're only going to reach developers with
attitude problems by having a personality and being on modern platforms.
I mean, it's an easy mistake to make.
I know this because I spent years making it myself with the nonsense
that I do until suddenly people are reaching out and it's, Huh, you
sure did use a lot of high level strategic terms for a developer.
And you start digging into it and it's like, Oh, you're,
you're a chief operating officer at a giant company.
I bet your code is terrible.
It's like, yeah, it turns out maybe I'm
not looking at that through the right lens.
Meeting people where they are with engaging content is important
and I think that a lot of folks completely miss that bus.
Yeah, I agree.
And this is a small field, right?
So it gets kind of nerve wracking sometimes because sometimes
you say things and It's so easy to be like, this is how I
joke with my friends, but I'm still somewhat in a professional
capacity because of me associating with my career, right?
And then when my videos reach a million, half a million views,
when we think about how many people are actually in this field that
would be interested in viewing that content, you realize, Oh wow.
Like this is a huge mixed bag of people, which does include
very high level executives all the way to people that are
in high school that are just interested in learning more.
So it's definitely been interesting to figure that out along the way.
But yeah, they all have regular personalities.
They all like TikTok too.
If they don't, they're lying.
I used to be very down on the whole TikTok thing, but I
started experimenting with it, and yeah, it turns out I have
a face for radio and, you know, the social graces for Twitter.
So it's not really my cup of tea, but I enjoy watching it.
I found that I'm not really a video person, but something about
the TikTok format means I'm just going to start scrolling.
And oh dear, it's been six hours, and my phone
battery died, thank God, or I'd still be there.
There's something very captivating about it, and I really like the format.
The problem I always had with looking at a lot of the deeply
technical content out there is so many companies are out
there producing this and selling this, and that's fine.
Fine.
Money is not the end all be all of this.
I'm about to spend weeks of my life on something.
The fact that it cost me 30 or 50 bucks or whatnot is really
not economic thing I should be concerning myself with.
But it all feels like it's classroom stuff.
It's, if you give people an option, are you going to go to
a college lecture or are you going to go to a comedy show?
There's the idea of, I want to be entertained.
If you can teach me something while entertaining
me, that feels like the winning combination.
And you've absolutely nailed that.
I think.
A lot of these companies that are producing content hold themselves back a lot.
And that is why they're not successful, right?
Because there's so many stipulations and there's teams of
people and boardrooms of approvals and all of these things.
And me, all I'm doing, I record all my TikToks
on my iPhone and I just use in app editing.
I spend a lot of time kind of researching, right?
Maybe you I will experiment with different formats,
but the best format that's worked for me is just being
authentic, kind of not having that corporate vibe, right?
And also not really expecting anything in return.
So a lot of times corporations are putting out content because they obviously
want to drive traffic to their websites and different things like that.
But the companies that do the best are the ones that are just putting out
content for free and really not necessarily expecting anything in return.
And they also give themselves so much more leeway into
the type of content that they create because they're
not thinking about the numbers at the end of it, right?
You just got to put stuff out there and people will see it.
For me, I just put stuff out there.
I don't need to wait for someone to approve my TikTok
for me to push it out and have this content there.
So that, that is a big difference.
And I've learned that through working with sponsors, where they'll
send you a giant list of talking points they want you to say.
And, and I'm like, you know, you guys know this is a 60 second video, right?
It needs to be really small.
You need to like really learn how to get the really important stuff
out there because the rest of the smaller stuff doesn't matter as much.
Like sell them on one big thing.
And that really makes a difference.
Oh, very much so.
I see that sometimes with this show where people will reach out and ask
about sponsoring and they'll want to have a URL that I read into the
microphone and it's with UTM tracking parameters and the rest and it's
like, I, I appreciate where you're coming from and your intention here.
However, that is not generally how this format works.
So let's talk about this and the outcome.
And again, it's, it's a brave new world out there.
Yeah.
If you're You're used to buying display ads in
various places, that is exactly what you do.
For some reason, there's this corporate mentality toward, we're going
to spend 25 million on a billboard saturation campaign, and not really
give any thought about what we're actually going to say now that we
have all of that visual real estate to get people's attention with.
It's, there's not enough focus on the message itself.
And I think that that is a giant lost opportunity.
Enterprise marketing doesn't have to be boring, it can be a lot of fun.
I agree.
And I think podcasting was the last.
Probably big area that people budgeted for marketing, right?
So you have your traditional TV commercials and there was YouTube
and that, you know, TV commercials, billboards, newspapers, then
there's YouTube and then podcasts, I would say probably came a
little bit later as far as these companies look at for marketing.
And now TikTok is so new and a lot of these marketing companies have
no idea how to be successful on it because it's just so different.
It's Gen Z.
The humor is different.
It's kind of like the wild west on social media where things are just
like crazy and you have to fight the algorithm because on TikTok it's.
If you don't like it, you just scroll within three seconds.
The attention span's so short, so you really have to capture
people's attention within those first three seconds versus a podcast.
You have the whole, let's say, first 20 minutes to get people kind
of interested before you can be like, oh, hey, and here's my sponsor.
So it is, it's very different versus TikTok.
They'll just be like, oh, scroll.
So you have to get creative and, and think differently.
Many moons ago, when I was getting my CCNA, I worked at a
company where we wound up getting a core switch for the data
center, which was, at the time, something like 65 grand.
Great.
And then we rented, because we had configured it in our office, and then
a couple of us had to rent a Commercial van, which I think ran something
like 30, 000 itself, to transport this thing 20 miles to the data center.
And I'm sitting there going like, wow, the switch is
worth way more than the van that's sitting within.
Also, we're really shitty movers, and that
doesn't seem like the best idea for anything.
But I distinctly remember that, and it left an impression on me.
What I like about cloud with what I do is I can take a credit card
And then spend less than 10 on AWS, or theoretically Azure, or Google
Cloud, or you know, 2 million on IBM, because oops a doozy, but fine.
And I wind up coming out the other side of that
with having done some interesting disaster stuff.
You are teaching people about how this stuff works, but in a data
center world, it seems to me that the startup cost of, Oh, I'm going
to buy this random router or switch to wind up doing some demonstration
stuff for, it feels like the startup cost of getting hands on
that equipment Would be out of reach for an awful lot of people.
Am I just completely out of touch with how that world works?
No, you're right.
You're 100 percent right.
It is difficult.
So in college, my undergraduate degree is computer
information systems, and they had a Cisco networking academy.
And so we had old switches, old layer three
switches, and then we had some routers.
And this is all stuff that was EOL donated equipment, right?
It breaks down, you're bidding against very far
away places with no budget on eBay for replacements.
Oh, yes.
Yeah, exactly.
And it was a lot of iOS stuff, right?
And so when I was in college, I had no idea.
that NXOS existed, which is the data center or Nexus
version operating system for their switches and things.
And so when I got to my first job and saw
NXOS, I was like, oh crap, like, what is this?
Right?
Because I honestly didn't even know.
I didn't, I graduated and did not know that existed.
And I didn't know a lot of the stuff that
I was working on at my first shop existed.
And I really had to rely on kind of the fundamentals.
And they are transferable, right?
That's why it's good to kind of get into,
like, I know what these routing protocols are.
I know Layer 2.
I know this cabling.
So let me just learn these command differences and things like that.
And once you get into a production environment in general, out of a lab.
It hits the fan, like everything you feel like you've learned is
gone almost because There's so many layers, and now all of a sudden
you have these firewalls, when before you were just trying to
get, like, your neighbor, your routing neighborships to establish,
and you weren't worried about rules on a firewall somewhere.
Oh, and by the way, in this environment,
that link that you're working on goes down.
Every minute it's down.
Here is the number of commas in the amount of
money that we're losing, and yes, that's a plural.
It's Okay, so I guess I'm going to double check everything I run first.
Yeah, it's that caution that gives people a bit of credence there.
It's, you have to do these things in a more or less cowboy
style in these environments, at least not for very long.
Because you can break individual servers, that's fine.
But if you break the network, suddenly you may as well not have the computers.
Yeah, it can be paralyzing, truly.
It can be very overwhelming, your first networking job.
Especially for me, I was just dealing with outages constantly
because I work for a vendor, and I was like, I was just scared,
you know, because I would get these cases, and it would be
a hospital outage, and I'm like, I just graduated college.
What do you want from me?
You know, and back to your original point, it is difficult
in a data center space because the equipment's so expensive.
So a lot of people ask, do you have a home lab?
And one, there's a couple of reasons.
I don't really have a significant home lab when I move so much.
Oh, and the spare room basically is always 90
degrees and sounds like a jet engine taking off.
Yeah.
It's one of those, I should probably find a different
place where I don't live to have that equipment.
Yeah.
And I have access like remotely to all the lab equipment that I really need.
So I don't personally have one, but a lot of things that
I do work with are so expensive that I'm like, I can't
afford to put this data center equipment in my house.
That doesn't make any sense.
And there is luckily now a lot of virtual labs that you can do.
There's some sandboxes by Cisco there and other vendors where
you can kind of get a little bit of hands on experience.
A lot of it relates to their certifications.
You can rent racks, but that gets pretty pricey too.
So it is difficult and sometimes That's why a lot of these jobs, I
think, I have a lot of people who are looking for entry level work.
And it's hard to get into a specifically a data center space.
And aside from racking, stacking, working in a data center, maybe a NOC,
if you want to get into the actual, I'm configuring Nexus switches, I'm
configuring, you know, Palo Alto firewalls, it can be difficult because.
It's hard to get to that point.
There's not a clear path.
What is the entry path these days?
I entered tech by working on a help desk, and those aren't
really the jobs that they once were in a lot of different ways.
So I've stopped talking to entry level folks with the position
of, oh, yeah, this is what you should do because it's what I did.
It turns into, like, okay, Boomer, great job.
Tell me a little bit more, though, about what the Great War was like first.
No.
We aren't going to go down that path.
It's just, I don't know what the entry level point is for
someone who's legitimately interested in these things these days.
Nobody does.
It's crazy.
And you're right.
The OK Boomer thing.
See, networking was one of those.
Things that just got pushed on to people in just a general IT department, right?
So that's when everything was like, okay, we need to get on the internet.
So, you know, hey, you, you handle some of the computer stuff.
It's your job now.
Good luck, figure it out.
And so, you know, People started doing that and they kind of just got pushed
into it and then as the internet grew, as our capabilities grew, then the
job became like a little bit more specialized and now we have, you know,
dedicated network engineers, we have people running data centers, but that's not
necessarily a viable path now for people just because there's so much to it now.
There's cloud, there's security risks, there's data center, wireless,
phone, I mean you can be an engineer just for phones, right?
So, It's a little bit difficult for especially the
younger people coming in and the people that I talk to
and figuring out, well, how do I get to what you're doing?
And the way that I did is I went and got a four year
degree and then joined a new college graduate program
at a Fortune 100 company, which, uh, is a great path.
I highly recommend it to anybody that can do it,
but it's also not available for everybody, right?
Because not everybody has the means to get a four year
education, nor do you necessarily need one to do what I do.
So, everybody's kind of has this different path, and it's very confusing for
people who are aspire network engineers or aspiring cloud engineers even.
Here at the Duck Bill Group, one of the things we do with,
you know, my day job is we help negotiate AWS contracts.
We just recently crossed 5 billion of contract value negotiated.
It solves for fun problems, such as how do you know that your
contract that you have with AWS is the best deal you can get?
How do you know you're not leaving money on the table?
How do you know that you're not doing what I do on this podcast
and on Twitter constantly and sticking your foot in your mouth?
To learn more, come chat at duckbillgroup.
com.
Optionally, I will also do podcast voice when we talk about it.
Again, that's duck bill group.com.
The narrative the cloud companies have been pushing for a while, like,
and I'm in that space deeply enough that I haven't really thought to go
super deep into questioning this is that, well, the future is all cloud.
The data center is basically this legacy thing that
the tide is slowly eroding in the fullness of time.
'cause everything will one day be cloud.
Do you think that's accurate?
I don't.
I really don't think that's accurate.
Don't get me wrong.
I think that the cloud is here to stay and
a lot of people are going to be using it.
And it's going to be, and it currently is a huge part of our lives.
Like as we've seen recently with a few of the AWS outages, when it goes
down, it goes down hard because everything's so centralized and people
like to think like, Oh, you know, we have all this redundancy, yada, yada.
That has not protected us so far, like, from these major outages, right?
And a lot of places that I see, especially when you're looking at a public
sector, is a hybrid where you do have data center on prem and you have cloud.
And I think that personally is the best way to go unless
you're, you know, maybe you're a fast growing startup
in AWS or Azure makes a lot of sense to And it does.
There's great use cases for that, right?
But they're not only Aside from the whole cloud shift, there's
another shift of, you know, making our data centers eco friendly, too.
And workload optimization, so maybe the price point that you're looking for,
what's going to save your business the most money, is doing that hybrid.
So I'm going to store a lot of my private documents on site.
I'm going to have this as a backup disaster recovery,
but we're also going to operate in the cloud.
I don't think that the data centers, as we know them, are going to go extinct.
I think they will be around.
Well, AWS finally made their outposts, the smaller ones, read as servers that
run AWS services in your facility, available a year after announcing them.
And I looked at it, it's like, oh wow, these things are 600
bucks a month, which is not nothing, but certainly something
I could afford to wind up exploring and doing some content in.
But okay, first, it's a three year commitment, so that's 20 grand or so.
Okay, not ideal, but fine, that would effectively almost double my AWS bill.
But that's not the hardest part because, oh, and to
get one of these, you have to have enterprise support.
And when I pointed this out to some Amazonian friends,
their response was, well, what's the problem on this?
Yeah, enterprise support starts at 15, 000 a month minimum.
And that means that people aren't going to
pick these up to do proof of concept work.
They're going to do it when they already
have a significant infrastructure out there.
And I think that's leaving an awful lot of money on the table
by making people jump through sales hoops and getting proof
of concept credits and doing all the other stuff for this.
Ship me a box for a few weeks and let me kick the tires on
it in my environment and see if it works or doesn't work.
Worst case, I'll ship it back to you.
Worst, worst case, I lose the thing and then
you charge me whatever it costs to replace this.
But it still feels like they are really doing the whole, oh,
it's only big legacy companies that have on premises stuff.
I don't like that narrative.
I don't either, and I honestly think it's a bad idea, right?
Because if you do put all of your eggs in the AWS basket and they have
all the power, that's not going to give us a lot of bargaining, right?
That's not going to give people a lot of, because they'll know,
they know how hard it is to to get off of AWS at that point.
They know it's costly.
It takes manpower.
It takes knowledge, right?
And I think that it is in people's best
interest to kind of have that mixed environment.
Just for a long term, I'm just very wary of centralizing everything in one area.
I think it's a bad idea.
I think that we need to be prepared for ourselves.
And that's it.
That means also relying a little bit on ourselves.
We can't just, in my opinion, put everything in the AWS basket.
Not for very long, anyway.
It just doesn't seem to work.
Right.
And it's a great product.
Oh, it absolutely is.
There's so many positive things about using cloud, because
I, I'm not the type of person that likes to use cloud.
Kind of talk crap about any vendor.
I think everybody has their pros, cons, flaws, whatever.
It's really about what works best for your environment.
And that's part of being a network engineer or a network architect is evaluating
your environment and figuring out what is going to be the best for you.
Right.
There's no one size fits all, unfortunately.
Yeah.
And AWS is uniformly excellent.
Let this be very clear.
Okay.
Not, maybe not uniformly.
Some services are.
Significantly better than others, but I had an opinion piece in the
information, paywalled unfortunately, but I'm working on it, that has
the general thesis that AWS has gotten too big to fail in that when
it's not like they're first, they are going to have better uptime
than you or I will running our own data centers across the board.
They are very good at keeping things up, but when they do go down,
it's not just your company or my company anymore having an outage.
It is a significant portion of, you know, the global economy.
And that is an awful lot of systemic concentrated risk.
I'm not suggesting they did anything wrong, as far as how they
sold these things, though some people will want to argue with that.
But it's the, it's the, what does this mean?
Are we ready to reckon with that as a society?
That whenever U.
S.
East 1 has a bad day, so does the stock market?
Is that something we're really prepared to accept or wrangle with?
Or worse than that, There are life critical services now.
Does that mean that there are, we're going to accept there's some
number of people who will die when there's an outage of a data center?
And that's new territory for me.
I have not worked in environments where it was
life or death consequential, at least not directly.
Yeah, I have.
So I have definitely worked in those environments, right?
And it's very scary, and especially when it's outside of your control.
So, if you are relying or just waiting on AWS to get back
up, you don't have the control to get in there and start
fixing things yourself, which is my instinct, right?
Like I immediately want to get hands on.
I put my troubleshooting hat on, like, let's figure this out.
Let me look through logs.
Let me do this.
And you don't have that option with AWS when it's a
significant outage that's impacting multiple people.
It's not some configuration internally to you, right?
And That's scary.
It's a scary place to be.
And I think that we need to really consider the cascading effects that will
happen, which a lot of these outages are kind of starting to show us, right?
And luckily there hasn't been anything major catastrophic, but we, we
do need to really consider life when we're talking about, you know,
hospitals, 911 systems, all of these critical infrastructures that are.
Going to be cloud managed and out of our control and centralized.
So, you know, you lose one 9 1 1 system.
Okay, well, you can do a backup, right?
You might be able to route all your calls to the city
over because their 9 1 1 systems are up and running.
Well, what if theirs are out now too?
Because you're both hosted on AWS.
Or you're, ah, we're gonna diversify and we're gonna
have this other one on a different cloud provider.
That's great, but there's a critical third party dependency that's
right back to the thing you're trying to avoid, and there you go again.
Yep, and that's dependency hell, right?
Oh yeah, and I don't know how we get away from that.
Like, we don't want everyone writing all their own stuff from scratch,
like starting with assembly, move up the stack, but here we are.
Right, and it's funny because These AWS outages
specifically affect or cloud outages, right?
I feel like I'm picking on them.
I'm not trying to.
Sorry, AWS, but don't come for me.
But, you know, explaining to my mom why her ring doorbell is not
working and her Roomba stopped working when that outage happened, right?
She's like, why is this not?
I won't connect.
Like, I don't understand.
She's like, what's AWS?
And then to tell my mom that the, The company that she buys her socks
from, like, that she goes online and, like, buys on Amazon is the company
that also is hosting her Roomba, you know, services, her Ring services.
It's so interesting to have those conversations.
And a lot of people who aren't in our field don't understand that.
They don't understand cloud.
They don't understand on prem versus, you know, hosted by a third party.
So it's interesting to watch that kind of unfold now because it's very new.
It's very new territory.
I have one last question before we wind up calling it an episode.
It is remarkably clear in talking to you that
you are in no way, shape, or form, junior.
You are not a beginner.
You know exactly how this stuff works in significant depth.
Your content that you put out is aimed at beginners.
I do something very similar, so to be very clear, this is not a criticism in
the slightest, but I am curious as to why that's the direction you went in.
I think there's a few reasons.
While I might have this knowledge right, I still consider
myself very junior in my career, very early in my career.
There's so many things that I don't know, and I recognize that.
I think when you're first starting out,
you might have this kind of inflated sense.
of knowledge where you're like, like me, I was like, oh yeah, I know all about
OSPF and running on iOS and the command line until I figured out there was NXOS.
And I'm like, oh crap, what else do I not know about, right?
By the way, that never goes away.
I feel exactly the same way 20 years into my career now.
I still have absolutely no idea what I'm doing.
So smile, nod, and get used to it is the only
insight I've got there, but please go on.
And even on Twitter, sometimes I'm reading people's stuff and I'm like,
how did you get into these obscure protocols and all these things?
And, you know, I just kind of dive deeper into there.
But I think the big reason that I create a lot of my content
for beginners is because I remember so well how it was
at the beginning, learning about subnetting and that iOS.
I'm learning about subnetting and all of
the different models that we have, right?
And I was overwhelmed, and I was stressed out, and it
just seemed so Just like a giant mountain to climb.
It seems so daunting in the beginning.
For me, it did because there's so much, right?
And it felt like everybody was so far ahead of me.
And I don't want other people to really feel like that.
Like, I don't want people to be turned off from
networking because they feel like the bar's too high.
That we're not We're not letting enough new people enter because we're
discouraging them from the beginning by saying, Oh, well, you're going
to have to know all this and let me throw this certification book at you.
And they're, they're big, like.
My certification books, these are massive, and this is for one half of the CCNA.
For those who aren't, like, on the video call, it's not being recorded.
Video wise, she's holding a book that you could use to
kill a mid sized dog by accident if it falls off a table.
It looks like a phone book with a hard cover on it.
Yeah, it's huge, right?
And there's thousands of pages and we just give this to somebody
and say, like, here you go, make sure you remember all this.
And this is all new information.
And does it still cover things like EIGRP, like Cisco's proprietary
routing protocols that I've never once seen in the wild?
Yeah.
So sometimes you will have to learn that and they, they've
changed it recently to, they update their certification exam.
So you will learn about some legacy protocols
because sometimes you do run into them.
Oh, yes.
That's when I have the good sense to pay
professionals who know what they're doing.
Exactly.
So yeah, you do run into those sometimes, but it feels
so daunting for new people, and I totally recognize that.
And by nature of TikTok, I, especially when I first started making
content, I assumed that most of the people on there are going
to be people who are younger, who are interested in this career.
And as you know, in tech in general, especially networking,
security, cloud, there's a massive shortage of people.
And How are we solving that?
Right?
And my contribution to helping solve that is by getting people interested.
And now I have people that DM me and say, I passed my network plus, or
I just took the CCNA, or this has been helping me with my class so much.
And that is like, okay, this is great.
Like, that's exactly what I want.
I want to help the pipeline.
I want to get more people interested and help a diverse.
group of people get interested in tech and say, Hey,
like this is, you know, where I came from and I did it.
You can do it.
Let's do it together type situation.
I really want to thank you for being so generous with your time.
If people want to learn more as they absolutely should, where can they find you?
I am on TikTok as SheNetworks.
I am on Twitter as NotSheNetworks.
Because
that is very confusing.
Well, my initial thing was like, I didn't really use Twitter that much.
And I would just like, It kind of used it
as like a back channel to my TikTok, right?
Where I would just like, Hey, I'm going to go live or do this.
And then my Twitter kind of got a little out of control and out of my hands.
It does that sometimes.
Yeah.
I had no idea there would be so much interest and it surprises me every day.
So it's exciting though.
I've, I really love all the people that I've met and I feel like I fit in.
And I've met.
So many good friends that it's been great.
But yeah, so not SheNetworks on Twitter, because
somebody had SheNetworks and it was a joke.
And so if you want to find me there, you could also find me there.
And we will, of course, put links to that in the show notes.
Thank you so much for taking the time to speak with me today.
I really do appreciate it.
Thank you for having me.
This has been great.
Serena, also known as SheNetworks, so much for being here.
Networking content creator to the stars.
I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud.
If you've enjoyed this podcast, please leave a five
star review on your podcast platform of choice.
Whereas if you've hated this podcast, please leave a five star review
on your podcast platform of choice and then a long, angry, rambling
comment about how the network isn't that important that you're then
not going to be able to submit because the network isn't working.