📺 Develpreneur YouTube Episode

Video + transcript

When Coffee Hits the Fan: Developer Disaster Recovery

2024-08-01 •Youtube

Detailed Notes

Welcome back to our podcast as we continue our season on the developer journey. Today, we’re diving into a topic that resonates with many: navigating challenging work environments, or as we put it, “when the coffee hits the fan.” Specifically, we’ll discuss developer disaster recovery and how to manage such situations effectively.

Read More... https://develpreneur.com/when-coffee-hits-the-fan-developer-disaster-recovery

Stay Connected: Join the Developreneur Community

We invite you to join our community and share your coding journey with us. Whether you’re a seasoned developer or just starting, there’s always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let’s continue exploring the exciting world of software development.

Additional Resources

* System Backups – Prepare for the Worst (https://develpreneur.com/system-backups-prepare-for-the-worst/)

* Using Dropbox To Provide A File Store and Reliable Backup (https://develpreneur.com/using-dropbox-to-provide-a-file-store-and-reliable-backup/)

* Testing Your Backups – Disaster Recovery Requires Verification (https://develpreneur.com/testing-your-backups-disaster-recovery-requires-verification/)

* Virtual Systems On A Budget – Realistic Cloud Pricing (https://develpreneur.com/virtual-systems-on-a-budget-realistic-cloud-pricing/)

Transcript Text
[Music]
oh hey there we hit record and we are
back back on track so yet another
episode uh last time around we talked
about stepping away taking a break uh
this episode we are gonna talk about
something different uh let's see what
are some good things to talk
about now in this week I'm wondering if
there's something we should take on
because this week we had the uh the
crowd strike Fiasco that like cause all
kinds of
issues
and you know this is this is actually a
good one I I think this is something
we'll talk about is um personal Disaster
Recovery basically uh because we have
had I've got some I've got a few stories
in my past of situations where we've
been in work environments where we had
to make do and it's like yeah you could
just say okay you know the world's on
fire so we're just not going to get work
done for a a while but sometimes that
doesn't help because that means when the
world is not on fire anymore now you got
to catch up twice as much and we there's
some interesting things that we've done
in the past that I've been involved with
just uh particularly in the
last 15 20 years as technology has
advanced and we've gotten beyond the
ability you know where we weren't like
wired in on a network and all these
kinds of stuff and actually I guess it's
gone sort of because used to be nobody
cared if the networ work down because
there wasn't a network and then
everything was networked and now
everything's Wireless but now you still
have to you know you almost always have
to be connected particularly as a
developer so I think sort of a personal
Disaster Recovery plan which is also a
little bit of a a road warrior kinds of
things we've talked about that some
about having a go bag and things like
that but I think we can we can revisit
that with
the what happens when things go wrong in
your normal place of work
yeah that Mak sense I like that as you
started I was thinking funding the
environment because I've been doing that
a lot lately as the corporation starts
to lock us down more and more so like
today I got a critical email oh you need
to reboot your machine because we're
putting Nanny Weare on your machine to
lock out all the basically they're
controlling everything well then we
found out we couldn't hit like stack
Overflow we couldn't hit red hat and
then they immediately had a production
issue and they couldn't support
it so yeah I I definitely think uh good
topic yeah there's a yeah it's a little
bit of a white hat black hat hacker type
of thing almost as well so hello and
welcome back we are continuing our
season when we're talking about the
developer journey and today we're going
to talk about uh when the uh the coffee
hits the fan basically when you're in an
environment and it is not a very kind
environment that's conducive to getting
work done recently there was a company
that we're not going to talk about but
you may have heard about it on the news
depending on how far back this is that
you're you know in the future you're
listening to this they had some issues
and it caused a lot of updates to not
update properly and a lot of machines
and a lot of systems to be unfunctional
for a while I'll even say nonfunctional
because unfunctional is not really a
word before we get into this one though
want to introduce myself my name is Rob
Broadhead I am one of the founders of
develop andur building better developers
also a founder of RB Consulting where we
tackle technology fatigue and sprawl and
we find ways through simplification
Automation and integration to take your
big nasty ugly things of technology and
streamline them and get it down to
something that works well Works solid
and is easy to maintain upgrate scale
all that good stuff somebody that else
that is H pretty much One of a Kind so
he's not going to scale very well and
you're not going to get too many
upgrades at least not until they go into
the million dollar man all that kind of
stuff Michael on the other side go ahead
and introduce yourself hey everyone my
name is Michael Mage I'm one of the
co-founders of developer Nur and a
founder of Envision QA where we help
small and midsize companies look at
their software stack see what
technologies they have and help them
either integrate better systems or build
something that suits more to their
needs so let's talk about I think we've
talked before about being like a a road
warrior kind of thing as a developer and
like some of the things where you have
it's useful to have like a lot of
different plugs and a lot of different
you know ways to integrate your system
to whatever it is you're on to make sure
that your phone can plug in to make sure
that your laptop can plug
in but these days most people have a
laptop so that allows you to be you
don't have to actually be plugged into
Power I mean you do at some point but
you know you can go for a while without
power and sometimes you can go without
you know it's most people need the
internet but the bonus is and one of the
things to prepare yourself sort of your
own little Disaster Recovery is have
like
a uh an external drive where you've got
some of your you know your primary
source code that you're working on right
now if that's feasible or or make sure
that you've brought it local even if
you're doing if you're using like GitHub
or one of of those or get or some
distributed Version Control System like
that as long as you've brought stuff
local you can continue to make branches
you can commit you can do all that stuff
and then eventually you can sync back
and get all of that stuff to like you
know line back up so you don't have you
can fake it you can also bring you know
through things we've talked about like
you know Docker and kubernetes and stuff
like that you can have an entire system
spun up you know virtual servers and all
this kind of stuff and it it can take
time it can take an investment to make
sure that you have that environment
available but when everything goes wrong
it is useful I will before I pass it on
to Michael and get your feedback and
thoughts I will share one little story
that I have that just sort of like as we
were thinking about and discussing the
topic for this is this is many years ago
it's probably now shoot I don't even
know I guess it's probably 15 years ago
it's been a while been a day or two as
they would say and we were we were
working this is back when everybody
basically you know nobody worked remote
everybody worked in an office and we had
a nice big office and we're in a big
office building and we had deadlines and
we were cranking through stuff and the
power went out whole building power went
out lost all the internet now we had
laptops and they were MacBooks a little
Apple ad there basically for you so they
even then had serious battery power so
you could you could code and be a
developer for hours on those suckers
before they ran out of power the problem
was we had to connect to the internet
this is where it's useful to have a a
device usually now it's your phone that
is a
hotspot and we literally are because our
manager was a big iPhone guy and this is
when iPhones had just come out they just
gotten to the point where you could
actually I think it was the first
version where it was ability to have a
Hotpot your iPhone could be its own
Hotpot and he walked out of his office
said his phone on top of a of a shelf
there and then said everybody this is
the wireless here's the password and
there's like I don't know five 10 of us
that we're working on using his phone to
connect out to the internet it was like
you know 0 g or whatever I don't
remember what it was not 4G or 5G I
can't remember what it was it was not
terribly fast but it got the job done
for as far as like you know having to
deal with emails and do a you know you
you're not going to download you know
gigabytes and gigabytes of data but you
probably don't need that and if you do
you should plan a little bit better so
you don't have to in those kinds of
situations is think through like how
self-sufficient is your system if you
get in a situation where you really need
to get something done but you don't have
your normal work environment if you're a
consultant if you're a side Hustler this
is the kind of thing that can come up
fairly often and does for me where
you're out you're not anywhere near your
office you're living life and somebody
calls with a critical issue and you've
got to find a way to you know help them
out I mean you could you could always
drive back home but it may take eight
hours and they're may be down all that
time particularly you know if you're
working 247 support things like that
there's all kinds of things that come up
so you know look at like your phone you
may be able to do a lot from that these
days because there's you know especially
if it's a smartphone you may have a
tablet you know like a an iPad or
something like that you may have like a
Chromebook or your regular laptop that
you can just you know throw in a
backpack that you create with you which
yes I'm a geek I do that way too often
people know me as a guy that's like I'll
sit down at the piano bar and crack out
the laptop every so often be like all
right I got work to do those are some of
the things to think about and it's as
always you want to think about those
before the disaster happens as opposed
to when it happens and on that no no
relation to disasters happening I will
pass it over to you and get your
thoughts on it
Michael thanks Rob uh yeah so it's funny
your story and how you're talking about
the disaster recovery and especially we
don't want to name names but you know
the uh the screen of death kind of thing
but as developers we run into other
situations it's not even just the
internet goes down or power goes down we
run into similar issues as to what
happened in the news we could take an
update to our IDE oops our IDE is now
broken we could take an update to the
operating system the operating system
shot
so building a model or setting up your
environment in a way that makes you as
basically environment agnostic as
possible is key at at least to me uh
over the years and why say that is over
the years I've gone through different
environments be it Windows Linux Unix
Mac
whatever all of them have the same
problems a system update gets pushed
down things get shot as400 a wrong patch
gets installed you're bricked you now
have to restore everything and you're
down for
hours as developers we are suceptible to
little things like that we could go from
say Java uh 2 to Java 8 and now the code
suddenly doesn't work you we have lots
of little things that can break our
environment so we have to be very
careful and very mindful of what it is
that we do to our machines that could
impact our work and not just the work
but also our customers because when we
push that software out we want to make
sure that the customer is not impacted
by something that we did
wrong so the story I'm going to tell is
is back at a company uh we were at but
before you came on uh when I first came
on board we had these very ancient uh
archaic machines that barely had 4 gigs
of RAM and we were trying to write code
on
this very minimal uh system
requirements we kept running out dis
space so this was
before Docker and really before VMS to
and extent uh VMware had just started
out and our Network guy had been using
Citrix so he started spinning up some
playing around with VM and started
spinning up some VM environments and
what I essentially did was I created a
base environment
image and that was the only image that
was allowed to go out to any of the
developers so all we had to do was we
basically just dropped their image
reload the image and it pointed to a
virtual drive that had all their files
in a separate location so they never
lost their files we would always once a
quarter review any system update
security patches whatever we did it in
one Silo made sure it worked and then we
pushed it out to everyone we never went
down prior to that we had hard drives
going out uh we had monitors going out
we had more hardware issues than you
could throw a skunk app I it was crazy
now in today's world we have do we have
containers we have things that we can
set up and now all you need is a virtual
disc space or a virtual environment you
can do it online you could do it on your
computers you can essentially do it
anywhere and then you essentially again
treat your environment as a silo and if
you need to change something test it
there if you break it there you're not
impacting your development so that's
just one approach I would take to saving
yourself the headaches of potential
disaster from update
first off I have to start with the
visual image of throwing a skunk at your
problems I was just like got to watch
out pepul Pew may get a little bad when
you do that that is actually a perfect
example of of the kind of Disaster
Recovery environments that we would love
to have this is something that now it's
much more feasible to do in the in the
world of cloud development and all that
kind of stuff it is very easy to set up
and I have done this I actually did this
for one of the seasons I can't remember
how far back we did where I went through
the entire thing I did an entire project
and I used Amazon's Cloud9 I think it
was even it may been before Amazon
bought Cloud9 but it was basically
working on a a completely virtual IDE so
I just logged in didn't matter where I
was what machine I was on I logged in it
logged me into my machine that was out
there yes I needed to have internet
connectivity but other than that all my
code was there all of the everything I
done it was everything I needed my
entire environment was there and it was
very similar to what Michael just
described um although the one he
described was a bit more powerful
because of you know citric and it was
closer and some things like that
but the nice thing about that was is
like when I came in I use that
environment all the time and I almost
never had to touch my actual laptop
didn't care what was on it didn't care
anything about it as long as I could get
to a like the the browser for at the
Citrix window I could go open up the
session and yes we did have problems as
we grew a little bit because people
would step on each other's sessions we
had to have the right s you had about
six or seven you know development
environments we had set up but then you
knew where to go if I'm focused on this
I'm going to go to this machine if I'm
focused on that I'm going to go to that
machine if I need to go fix the database
I got to go to this one you know it's
those kinds of things allow you to be
completely free now you don't have to
worry about oh crap I left that on my
machine CH so utilize the cloud for that
kind of stuff don't be afraid to use
things like definitely uh GitHub and
places like that for your version
control so you can access your source
code from anywhere also I make heavy use
of Dropbox and have for a long time and
there are other tools like that that are
commercially available if you want to do
your own personal cloud there are plenty
of options for that where you basically
go get a you know multi-terabyte drive
and then you can access it from anywhere
as long as you want to take care of this
you know security and things like
that these things will be they are more
than worth their weight in gold when you
need them and if you get yourself using
them all the time you will find more and
more for example that you don't need a
high-end laptop when you go upgrade your
development laptop or your development
machine you just need a way to get to
that environment maybe you just need a
browser so now suddenly you know maybe
it is like a little Chromebook works
fine for because you really don't it
that thing doesn't matter all that
matters you have a decent display a
decent keyboard and you can browse to
wherever your Cloud environment is and
this is becoming more and more common
particularly if you're in the world of
like Salesforce and net suite and
HubSpot and all these things that are
you basically you can live your
professional life on this site or in
this you know software as a service
solution and you don't have to worry
about it being on your machine and
sharing stuff out and all the things
that can be involved in
that uh closing
thoughts yeah in addition to what we've
talked about up to this point the other
thing that this type of approach is good
for is if you are looking at taking on
new customers or you have a customer
that needs some software written and
you're not sure if either your software
is going to work with theirs this is
where you can build those virtual
environments locally test them and make
sure they work before you actually
impact the production environment if you
need more RAM you know ahead of time go
buy the ram put it in the cost don't
just push your software out and then
have 1,000 users turn around and say hey
only 10 people can get in because we
don't have enough
switches these are things that you can
test you should be testing and the
beauty of it is it is not that expensive
to build your own own virtual uh
virtualization
environment at home or on the
web it is also not that expensive to
give us some feedback to get something
in there throw some comments out there
give us give us a little love you know a
little like Hey we're spending some time
here we're coming into your I know it is
a little bit intrusive coming into your
your ear holes as we are whether your
audio or your eyeh holes if you're
watching through
YouTube but we love that feedback we'd
love to hear from you we' love to hear
where would you like us to go next as
we're talking through our developer
journey and yes we are not done we are
only about roughly halfway maybe through
the season and we've got plenty of
topics ahead even we don't know what
those topics are yet though because
we're sort of like we're journeying as
we go through some of these things and
that's worked out pretty good we think
so far hopefully you agree but obviously
your feedback will help and we can
either use your name or we can keep you
Anonymous if you want to you know if you
don't want to have anything to do with
us we get
that however come on back hang out with
us for a little bit and see where we go
with this feedback is always welcome and
as always go out there and have yourself
a great day a great week and we will
talk to you next
time bonus
material I will say
particularly I have lost
days in in the past particularly with if
react development node development uh
Python and Java particularly like Maven
environments and stuff where you've got
a lot of libraries I think I haven't
done I haven't run into it as much in
the net world but I haven't done as much
in recent years when they've gotten into
their whole you know nuggets and all
that I forget what they call them but if
you're in that kind of an environment
one turn off automatic updates like save
yourself the headache because it's
amazing how often as Michael alluded to
an automatic update blows your whole
world up and you can lose days the other
thing is is if you can if you can get
yourself comfortable on a regular basis
working in a virtual environment then it
will help you immensely when those
things happen because you're just you're
always in that
environment you're used to it and so if
something happens and you accidentally
take an update or what you say okay I'm
going to go back my last backup you know
things like that and particularly that's
the other thing back up regularly make
sure that you you know at the end of the
day that you're not just you've not just
moved your problems into a virtual
environment that also you are doing
backups and things like that depending
on how you've got stuff set up there are
a lot of tools out there you can use
like Apple's time machine and then
there's all those things out there where
you can you can find a lot of ways to
back up even huge amounts of data uh you
know like a big if you've got a 50 gig
100 Gig 200 gig virtual environment
you can have that thing just syn
somewhere and just you know update every
night while you go to sleep or something
like that there's there are a lot of
ways to do it just make sure that when
you do it you keep that environment
pristine and as Michael said is like
don't be afraid to like back it up if
you've got to do updates or you've got
to like you know do an upgrade or
something like that back up the one and
then come back and then you can go ahead
and pull all that stuff down verify it
and then you can you know you can say
okay I can stamp this as good and move
forward okay I remembered I remember
okay all right
so we've talked about the virtualization
we've talked about the environments and
everything something that hit me
today is power so yes our laptops have
you know pretty decent battery power our
phones have pretty decent battery power
but you sometimes run into situations
where you did not bring the right cable
or you did not plan ahead with you know
Char charging before you got went on
that road trip or you lost power in the
middle of you know what you're trying to
get out for production having battery
backups having UBS backups uh generators
things of that nature you know in this
day and age it is also prudent to think
about some other type of power backups
to just ensure that you are still
working be it's solar or whatever just
to make sure that you do have that extra
redundancy because you never know you
know we get storms out here from time to
time a tree may take out a power line
might not you never know um so just kind
of a side thought on that think about
what you have for your existing
environment outside of you know your
typical utilities what can you do to
keep the power on so you can keep
working that makes sense and it that is
something that I guess I had really
thought about but it I have at times the
idea of having like either little and
they are incredibly like decently priced
if you want to have like a a there are
solar generators and and ways to capture
energy and stuff like that particularly
if you go look in the uh the Camping
World and things like that there are a
lot of ways to get that extra power we
worked with a developer years ago that
was at a place
where um they they were on a you know
basically at midnight everything shut
down all electricity everything went
went dark at midnight and so when that
hit he would go out in the back and he
had like two hours worth of power cuz
he' go crank up a gas power generator
and he'd be able to use that for a while
I mean there's things like that that you
can do so uh you know that power is is
pretty you know pretty important to get
through um that being said I think
that's good enough for now we got to
wrap it up we got to get going and uh
get back to our work and and all of our
stuff so continue as always give us
feedback info@ developer.com leave us
comments however smoke signals whatever
it is face Facebook X developer.com on
the the forums you can submit stuff
we're happy to hear from you and uh look
for you know new suggestions and things
like that from you guys that being said
go out there and have yourselves a good
one and we will be back next time
around bushy eyed and brigh eyed and
bushy tailed as always and we won't
throw skunks at you have a good one
[Music]
Transcript Segments
1.35

[Music]

27.199

oh hey there we hit record and we are

29.72

back back on track so yet another

33.68

episode uh last time around we talked

37.44

about stepping away taking a break uh

41.399

this episode we are gonna talk about

44.48

something different uh let's see what

47.52

are some good things to talk

50.48

about now in this week I'm wondering if

52.879

there's something we should take on

54.68

because this week we had the uh the

57.52

crowd strike Fiasco that like cause all

60.92

kinds of

62.28

issues

64.479

and you know this is this is actually a

67.32

good one I I think this is something

68.84

we'll talk about is um personal Disaster

72.119

Recovery basically uh because we have

75.28

had I've got some I've got a few stories

77.68

in my past of situations where we've

79.52

been in work environments where we had

82.32

to make do and it's like yeah you could

85.36

just say okay you know the world's on

88

fire so we're just not going to get work

89.52

done for a a while but sometimes that

92.439

doesn't help because that means when the

93.88

world is not on fire anymore now you got

95.92

to catch up twice as much and we there's

100.04

some interesting things that we've done

101.399

in the past that I've been involved with

103.32

just uh particularly in the

105.88

last 15 20 years as technology has

109

advanced and we've gotten beyond the

111.159

ability you know where we weren't like

112.6

wired in on a network and all these

114.799

kinds of stuff and actually I guess it's

116.68

gone sort of because used to be nobody

118.32

cared if the networ work down because

119.6

there wasn't a network and then

122.119

everything was networked and now

123.96

everything's Wireless but now you still

125.64

have to you know you almost always have

127.6

to be connected particularly as a

129.36

developer so I think sort of a personal

133.239

Disaster Recovery plan which is also a

135.16

little bit of a a road warrior kinds of

138.68

things we've talked about that some

140.08

about having a go bag and things like

141.68

that but I think we can we can revisit

144.04

that with

145.72

the what happens when things go wrong in

148.519

your normal place of work

150.879

yeah that Mak sense I like that as you

153.48

started I was thinking funding the

155.16

environment because I've been doing that

156.56

a lot lately as the corporation starts

160.239

to lock us down more and more so like

163.28

today I got a critical email oh you need

166.28

to reboot your machine because we're

167.8

putting Nanny Weare on your machine to

170.239

lock out all the basically they're

172.239

controlling everything well then we

173.92

found out we couldn't hit like stack

175.4

Overflow we couldn't hit red hat and

177.48

then they immediately had a production

179.08

issue and they couldn't support

183.08

it so yeah I I definitely think uh good

187.48

topic yeah there's a yeah it's a little

189.76

bit of a white hat black hat hacker type

192.12

of thing almost as well so hello and

194.599

welcome back we are continuing our

196.76

season when we're talking about the

198.4

developer journey and today we're going

200.959

to talk about uh when the uh the coffee

205.44

hits the fan basically when you're in an

207.2

environment and it is not a very kind

209.799

environment that's conducive to getting

211.319

work done recently there was a company

214.28

that we're not going to talk about but

216.239

you may have heard about it on the news

217.76

depending on how far back this is that

219.4

you're you know in the future you're

220.4

listening to this they had some issues

223.319

and it caused a lot of updates to not

226.04

update properly and a lot of machines

227.72

and a lot of systems to be unfunctional

230.239

for a while I'll even say nonfunctional

232.64

because unfunctional is not really a

234.36

word before we get into this one though

237.48

want to introduce myself my name is Rob

239.04

Broadhead I am one of the founders of

240.68

develop andur building better developers

242.959

also a founder of RB Consulting where we

245.92

tackle technology fatigue and sprawl and

250.159

we find ways through simplification

252.319

Automation and integration to take your

254.64

big nasty ugly things of technology and

258.6

streamline them and get it down to

260.44

something that works well Works solid

263

and is easy to maintain upgrate scale

265.919

all that good stuff somebody that else

268.36

that is H pretty much One of a Kind so

270.44

he's not going to scale very well and

272.199

you're not going to get too many

273.28

upgrades at least not until they go into

276

the million dollar man all that kind of

277.52

stuff Michael on the other side go ahead

279.84

and introduce yourself hey everyone my

282.28

name is Michael Mage I'm one of the

284

co-founders of developer Nur and a

285.88

founder of Envision QA where we help

288.36

small and midsize companies look at

290.88

their software stack see what

292.96

technologies they have and help them

295.479

either integrate better systems or build

298.12

something that suits more to their

301.88

needs so let's talk about I think we've

306.52

talked before about being like a a road

308.28

warrior kind of thing as a developer and

309.88

like some of the things where you have

312.24

it's useful to have like a lot of

313.68

different plugs and a lot of different

315.68

you know ways to integrate your system

317.52

to whatever it is you're on to make sure

319.08

that your phone can plug in to make sure

320.919

that your laptop can plug

323

in but these days most people have a

326.319

laptop so that allows you to be you

329.12

don't have to actually be plugged into

330.6

Power I mean you do at some point but

332.479

you know you can go for a while without

334.52

power and sometimes you can go without

337.52

you know it's most people need the

339.639

internet but the bonus is and one of the

342.08

things to prepare yourself sort of your

343.52

own little Disaster Recovery is have

346.4

like

347.24

a uh an external drive where you've got

350.44

some of your you know your primary

351.68

source code that you're working on right

353.24

now if that's feasible or or make sure

355.28

that you've brought it local even if

357.16

you're doing if you're using like GitHub

359.28

or one of of those or get or some

361.68

distributed Version Control System like

363.639

that as long as you've brought stuff

365.36

local you can continue to make branches

367.16

you can commit you can do all that stuff

368.8

and then eventually you can sync back

370.639

and get all of that stuff to like you

372.599

know line back up so you don't have you

375.639

can fake it you can also bring you know

378.479

through things we've talked about like

379.919

you know Docker and kubernetes and stuff

381.72

like that you can have an entire system

383.24

spun up you know virtual servers and all

386.16

this kind of stuff and it it can take

389

time it can take an investment to make

392.199

sure that you have that environment

393.84

available but when everything goes wrong

397.68

it is useful I will before I pass it on

400.16

to Michael and get your feedback and

401.72

thoughts I will share one little story

403.319

that I have that just sort of like as we

405.56

were thinking about and discussing the

407.16

topic for this is this is many years ago

410.599

it's probably now shoot I don't even

412.36

know I guess it's probably 15 years ago

414.4

it's been a while been a day or two as

417.039

they would say and we were we were

419.56

working this is back when everybody

421.12

basically you know nobody worked remote

423

everybody worked in an office and we had

424.319

a nice big office and we're in a big

425.72

office building and we had deadlines and

427.96

we were cranking through stuff and the

430.08

power went out whole building power went

433

out lost all the internet now we had

436.199

laptops and they were MacBooks a little

438.599

Apple ad there basically for you so they

441.24

even then had serious battery power so

444.08

you could you could code and be a

446.4

developer for hours on those suckers

448.599

before they ran out of power the problem

451.12

was we had to connect to the internet

453.639

this is where it's useful to have a a

457.08

device usually now it's your phone that

459.639

is a

460.919

hotspot and we literally are because our

464.479

manager was a big iPhone guy and this is

466.56

when iPhones had just come out they just

468.639

gotten to the point where you could

470.12

actually I think it was the first

471.28

version where it was ability to have a

473.919

Hotpot your iPhone could be its own

475.879

Hotpot and he walked out of his office

479.039

said his phone on top of a of a shelf

483.12

there and then said everybody this is

485.639

the wireless here's the password and

488.039

there's like I don't know five 10 of us

490.199

that we're working on using his phone to

493

connect out to the internet it was like

495.919

you know 0 g or whatever I don't

497.919

remember what it was not 4G or 5G I

500.039

can't remember what it was it was not

501.96

terribly fast but it got the job done

504.84

for as far as like you know having to

507.24

deal with emails and do a you know you

509.879

you're not going to download you know

512.8

gigabytes and gigabytes of data but you

516.08

probably don't need that and if you do

518.959

you should plan a little bit better so

520.56

you don't have to in those kinds of

522.279

situations is think through like how

525.839

self-sufficient is your system if you

528.36

get in a situation where you really need

530.2

to get something done but you don't have

532.839

your normal work environment if you're a

534.959

consultant if you're a side Hustler this

536.64

is the kind of thing that can come up

538.04

fairly often and does for me where

541.399

you're out you're not anywhere near your

544

office you're living life and somebody

545.76

calls with a critical issue and you've

547.8

got to find a way to you know help them

549.88

out I mean you could you could always

551.12

drive back home but it may take eight

553.399

hours and they're may be down all that

555.2

time particularly you know if you're

556.44

working 247 support things like that

559.76

there's all kinds of things that come up

561.6

so you know look at like your phone you

564.72

may be able to do a lot from that these

566.519

days because there's you know especially

567.88

if it's a smartphone you may have a

569.72

tablet you know like a an iPad or

572.04

something like that you may have like a

573.32

Chromebook or your regular laptop that

575.72

you can just you know throw in a

577.04

backpack that you create with you which

578.519

yes I'm a geek I do that way too often

581.16

people know me as a guy that's like I'll

582.839

sit down at the piano bar and crack out

584.519

the laptop every so often be like all

586.24

right I got work to do those are some of

588.76

the things to think about and it's as

590.76

always you want to think about those

592.36

before the disaster happens as opposed

594.68

to when it happens and on that no no

599.64

relation to disasters happening I will

601.68

pass it over to you and get your

602.959

thoughts on it

604.519

Michael thanks Rob uh yeah so it's funny

609.079

your story and how you're talking about

611.72

the disaster recovery and especially we

614.32

don't want to name names but you know

616.16

the uh the screen of death kind of thing

620.36

but as developers we run into other

624.44

situations it's not even just the

626.56

internet goes down or power goes down we

629.36

run into similar issues as to what

631.56

happened in the news we could take an

634.92

update to our IDE oops our IDE is now

637.88

broken we could take an update to the

639.6

operating system the operating system

641.44

shot

643.04

so building a model or setting up your

647.2

environment in a way that makes you as

650.839

basically environment agnostic as

653.399

possible is key at at least to me uh

657.72

over the years and why say that is over

660.48

the years I've gone through different

663

environments be it Windows Linux Unix

665.68

Mac

667.2

whatever all of them have the same

669.56

problems a system update gets pushed

671.92

down things get shot as400 a wrong patch

675.639

gets installed you're bricked you now

677.32

have to restore everything and you're

678.76

down for

680

hours as developers we are suceptible to

684.2

little things like that we could go from

686.2

say Java uh 2 to Java 8 and now the code

690.279

suddenly doesn't work you we have lots

693.6

of little things that can break our

695.959

environment so we have to be very

697.639

careful and very mindful of what it is

700.6

that we do to our machines that could

703.959

impact our work and not just the work

706.279

but also our customers because when we

707.839

push that software out we want to make

710.079

sure that the customer is not impacted

712.8

by something that we did

715.76

wrong so the story I'm going to tell is

719.32

is back at a company uh we were at but

722.88

before you came on uh when I first came

725.92

on board we had these very ancient uh

730

archaic machines that barely had 4 gigs

732.36

of RAM and we were trying to write code

734.959

on

736.12

this very minimal uh system

740.399

requirements we kept running out dis

742.639

space so this was

745.399

before Docker and really before VMS to

748.92

and extent uh VMware had just started

751.519

out and our Network guy had been using

754.44

Citrix so he started spinning up some

756.639

playing around with VM and started

758.48

spinning up some VM environments and

760.72

what I essentially did was I created a

763.24

base environment

765.639

image and that was the only image that

768.32

was allowed to go out to any of the

770.04

developers so all we had to do was we

772.639

basically just dropped their image

774.199

reload the image and it pointed to a

776.56

virtual drive that had all their files

779.279

in a separate location so they never

780.8

lost their files we would always once a

784.32

quarter review any system update

787.6

security patches whatever we did it in

789.68

one Silo made sure it worked and then we

792.36

pushed it out to everyone we never went

794.839

down prior to that we had hard drives

797.839

going out uh we had monitors going out

800.12

we had more hardware issues than you

802.199

could throw a skunk app I it was crazy

806.24

now in today's world we have do we have

809.76

containers we have things that we can

811.519

set up and now all you need is a virtual

815.079

disc space or a virtual environment you

817.36

can do it online you could do it on your

819.16

computers you can essentially do it

821.24

anywhere and then you essentially again

823.76

treat your environment as a silo and if

826.6

you need to change something test it

828.199

there if you break it there you're not

830.399

impacting your development so that's

832.839

just one approach I would take to saving

835.92

yourself the headaches of potential

838.079

disaster from update

841

first off I have to start with the

843.32

visual image of throwing a skunk at your

845.32

problems I was just like got to watch

847.56

out pepul Pew may get a little bad when

849.92

you do that that is actually a perfect

854

example of of the kind of Disaster

857.639

Recovery environments that we would love

859.759

to have this is something that now it's

862.04

much more feasible to do in the in the

864.24

world of cloud development and all that

865.639

kind of stuff it is very easy to set up

868.32

and I have done this I actually did this

870.839

for one of the seasons I can't remember

872.6

how far back we did where I went through

874.56

the entire thing I did an entire project

876.199

and I used Amazon's Cloud9 I think it

878.68

was even it may been before Amazon

881.199

bought Cloud9 but it was basically

882.839

working on a a completely virtual IDE so

886.56

I just logged in didn't matter where I

888.6

was what machine I was on I logged in it

891.72

logged me into my machine that was out

893.6

there yes I needed to have internet

895.199

connectivity but other than that all my

897.759

code was there all of the everything I

899.72

done it was everything I needed my

902.32

entire environment was there and it was

903.959

very similar to what Michael just

905.88

described um although the one he

908.399

described was a bit more powerful

909.88

because of you know citric and it was

911.759

closer and some things like that

914.16

but the nice thing about that was is

916.68

like when I came in I use that

918.199

environment all the time and I almost

920.199

never had to touch my actual laptop

922.759

didn't care what was on it didn't care

924.6

anything about it as long as I could get

926.759

to a like the the browser for at the

929.279

Citrix window I could go open up the

931.56

session and yes we did have problems as

933.72

we grew a little bit because people

934.92

would step on each other's sessions we

936.519

had to have the right s you had about

938.12

six or seven you know development

939.72

environments we had set up but then you

941.48

knew where to go if I'm focused on this

944.399

I'm going to go to this machine if I'm

945.88

focused on that I'm going to go to that

947.319

machine if I need to go fix the database

949.6

I got to go to this one you know it's

951.839

those kinds of things allow you to be

954.959

completely free now you don't have to

956.519

worry about oh crap I left that on my

958.639

machine CH so utilize the cloud for that

962.519

kind of stuff don't be afraid to use

964.199

things like definitely uh GitHub and

968.12

places like that for your version

969.36

control so you can access your source

970.959

code from anywhere also I make heavy use

974.079

of Dropbox and have for a long time and

976.16

there are other tools like that that are

978.399

commercially available if you want to do

980.319

your own personal cloud there are plenty

982.079

of options for that where you basically

983.92

go get a you know multi-terabyte drive

987

and then you can access it from anywhere

989

as long as you want to take care of this

990.279

you know security and things like

992.16

that these things will be they are more

995.759

than worth their weight in gold when you

997.88

need them and if you get yourself using

1000.319

them all the time you will find more and

1002.079

more for example that you don't need a

1005.16

high-end laptop when you go upgrade your

1007.16

development laptop or your development

1008.72

machine you just need a way to get to

1011.839

that environment maybe you just need a

1013.36

browser so now suddenly you know maybe

1016.36

it is like a little Chromebook works

1018.36

fine for because you really don't it

1020.56

that thing doesn't matter all that

1023.36

matters you have a decent display a

1025.079

decent keyboard and you can browse to

1027.839

wherever your Cloud environment is and

1030

this is becoming more and more common

1032

particularly if you're in the world of

1033.36

like Salesforce and net suite and

1036.6

HubSpot and all these things that are

1038.88

you basically you can live your

1040.76

professional life on this site or in

1042.88

this you know software as a service

1045.039

solution and you don't have to worry

1046.959

about it being on your machine and

1048.88

sharing stuff out and all the things

1051.44

that can be involved in

1053.44

that uh closing

1055.679

thoughts yeah in addition to what we've

1058.2

talked about up to this point the other

1060.48

thing that this type of approach is good

1062.84

for is if you are looking at taking on

1066.559

new customers or you have a customer

1069.559

that needs some software written and

1071.559

you're not sure if either your software

1073.919

is going to work with theirs this is

1075.64

where you can build those virtual

1077

environments locally test them and make

1080.76

sure they work before you actually

1082.24

impact the production environment if you

1084.159

need more RAM you know ahead of time go

1086.36

buy the ram put it in the cost don't

1089.32

just push your software out and then

1091.96

have 1,000 users turn around and say hey

1094.919

only 10 people can get in because we

1097.679

don't have enough

1099.039

switches these are things that you can

1101.4

test you should be testing and the

1103.919

beauty of it is it is not that expensive

1107.44

to build your own own virtual uh

1110.919

virtualization

1112.44

environment at home or on the

1116.159

web it is also not that expensive to

1119.72

give us some feedback to get something

1121.559

in there throw some comments out there

1123.2

give us give us a little love you know a

1125.679

little like Hey we're spending some time

1127.4

here we're coming into your I know it is

1129.24

a little bit intrusive coming into your

1131.28

your ear holes as we are whether your

1133.12

audio or your eyeh holes if you're

1134.679

watching through

1136.919

YouTube but we love that feedback we'd

1139.88

love to hear from you we' love to hear

1141.32

where would you like us to go next as

1143.039

we're talking through our developer

1145.08

journey and yes we are not done we are

1147.2

only about roughly halfway maybe through

1149.6

the season and we've got plenty of

1152.24

topics ahead even we don't know what

1154.96

those topics are yet though because

1157.12

we're sort of like we're journeying as

1158.96

we go through some of these things and

1161.36

that's worked out pretty good we think

1162.76

so far hopefully you agree but obviously

1165.48

your feedback will help and we can

1167

either use your name or we can keep you

1169.2

Anonymous if you want to you know if you

1170.919

don't want to have anything to do with

1172.4

us we get

1174.44

that however come on back hang out with

1178.039

us for a little bit and see where we go

1179.36

with this feedback is always welcome and

1182.28

as always go out there and have yourself

1184

a great day a great week and we will

1186.28

talk to you next

1188.799

time bonus

1193.159

material I will say

1196.36

particularly I have lost

1199.679

days in in the past particularly with if

1203.88

react development node development uh

1207.12

Python and Java particularly like Maven

1209.52

environments and stuff where you've got

1210.64

a lot of libraries I think I haven't

1213.52

done I haven't run into it as much in

1215.28

the net world but I haven't done as much

1217

in recent years when they've gotten into

1218.799

their whole you know nuggets and all

1220.6

that I forget what they call them but if

1222.679

you're in that kind of an environment

1224.52

one turn off automatic updates like save

1228.28

yourself the headache because it's

1230

amazing how often as Michael alluded to

1232

an automatic update blows your whole

1233.679

world up and you can lose days the other

1236.28

thing is is if you can if you can get

1238.52

yourself comfortable on a regular basis

1241.08

working in a virtual environment then it

1243.6

will help you immensely when those

1246.24

things happen because you're just you're

1247.84

always in that

1249.08

environment you're used to it and so if

1252.36

something happens and you accidentally

1254.799

take an update or what you say okay I'm

1256.4

going to go back my last backup you know

1258.159

things like that and particularly that's

1259.48

the other thing back up regularly make

1261.08

sure that you you know at the end of the

1262.799

day that you're not just you've not just

1264.799

moved your problems into a virtual

1266.96

environment that also you are doing

1268.679

backups and things like that depending

1270.799

on how you've got stuff set up there are

1272.559

a lot of tools out there you can use

1274.279

like Apple's time machine and then

1275.919

there's all those things out there where

1277.4

you can you can find a lot of ways to

1279.799

back up even huge amounts of data uh you

1282.679

know like a big if you've got a 50 gig

1285.919

100 Gig 200 gig virtual environment

1289.24

you can have that thing just syn

1290.6

somewhere and just you know update every

1292.279

night while you go to sleep or something

1293.6

like that there's there are a lot of

1295.2

ways to do it just make sure that when

1297.159

you do it you keep that environment

1298.96

pristine and as Michael said is like

1300.52

don't be afraid to like back it up if

1304.2

you've got to do updates or you've got

1305.679

to like you know do an upgrade or

1306.96

something like that back up the one and

1308.52

then come back and then you can go ahead

1309.88

and pull all that stuff down verify it

1312.4

and then you can you know you can say

1313.919

okay I can stamp this as good and move

1317.36

forward okay I remembered I remember

1320.44

okay all right

1322.799

so we've talked about the virtualization

1325.12

we've talked about the environments and

1326.88

everything something that hit me

1329.559

today is power so yes our laptops have

1334.72

you know pretty decent battery power our

1336.799

phones have pretty decent battery power

1338.72

but you sometimes run into situations

1341.4

where you did not bring the right cable

1344.32

or you did not plan ahead with you know

1347.24

Char charging before you got went on

1348.88

that road trip or you lost power in the

1350.76

middle of you know what you're trying to

1353.2

get out for production having battery

1355.559

backups having UBS backups uh generators

1358.88

things of that nature you know in this

1361.12

day and age it is also prudent to think

1364.159

about some other type of power backups

1366.96

to just ensure that you are still

1368.36

working be it's solar or whatever just

1370.52

to make sure that you do have that extra

1372.799

redundancy because you never know you

1375.4

know we get storms out here from time to

1377.24

time a tree may take out a power line

1379.12

might not you never know um so just kind

1383.08

of a side thought on that think about

1385.039

what you have for your existing

1388.039

environment outside of you know your

1390.08

typical utilities what can you do to

1391.84

keep the power on so you can keep

1394.6

working that makes sense and it that is

1397.4

something that I guess I had really

1398.76

thought about but it I have at times the

1400.679

idea of having like either little and

1402.88

they are incredibly like decently priced

1406.96

if you want to have like a a there are

1409.2

solar generators and and ways to capture

1412.2

energy and stuff like that particularly

1413.799

if you go look in the uh the Camping

1416.159

World and things like that there are a

1418.72

lot of ways to get that extra power we

1421.44

worked with a developer years ago that

1423.6

was at a place

1425.96

where um they they were on a you know

1430.24

basically at midnight everything shut

1432.2

down all electricity everything went

1434.64

went dark at midnight and so when that

1437.64

hit he would go out in the back and he

1439

had like two hours worth of power cuz

1440.32

he' go crank up a gas power generator

1441.919

and he'd be able to use that for a while

1443.2

I mean there's things like that that you

1444.44

can do so uh you know that power is is

1448.279

pretty you know pretty important to get

1451

through um that being said I think

1454.159

that's good enough for now we got to

1455.52

wrap it up we got to get going and uh

1457.679

get back to our work and and all of our

1459.88

stuff so continue as always give us

1462.64

feedback info@ developer.com leave us

1465.36

comments however smoke signals whatever

1467.799

it is face Facebook X developer.com on

1471.559

the the forums you can submit stuff

1473.279

we're happy to hear from you and uh look

1475.679

for you know new suggestions and things

1477.559

like that from you guys that being said

1479.76

go out there and have yourselves a good

1481.08

one and we will be back next time

1483.72

around bushy eyed and brigh eyed and

1486.32

bushy tailed as always and we won't

1488.36

throw skunks at you have a good one

1493.15

[Music]