📺 Develpreneur YouTube Episode

Video + transcript

Ending Your Developer Journey: How to Leave a Lasting Legacy

2024-10-10 •Youtube

Detailed Notes

In this episode of Building Better Developers, the host dives into a crucial topic—ending your developer journey. Whether you’re nearing the end of your career, transitioning to a new job, or closing down a side project, knowing how to wrap up your work properly is essential. The episode offers insights into how to leave things in good order, ensuring continuity for whoever comes after you.

Read more... https://develpreneur.com/ending-your-developer-journey-how-to-leave-a-lasting-legacy/

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

* Moving Forward – Releasing Past Mistakes ("https://develpreneur.com/moving-forward-releasing-past-mistakes") * Admitting Defeat – Moving Forward And Accepting The Loss ("https://develpreneur.com/admitting-defeat-moving-forward-and-accepting-the-loss/") * Pivoting: How to Embrace Change and Fuel Your Professional Growth ("https://develpreneur.com/pivoting-how-to-embrace-change-and-fuel-your-professional-growth/") * Planning For Growth – Give Your Changes Time To Take Hold ("https://develpreneur.com/planning-for-growth-give-your-changes-time-to-take-hold/")

Follow- us on:

* https://develpreneur.com/ * https://www.youtube.com/channel/UCZOuFN_LhczvGyT2KSItH_g/featured * https://facebook.com/Develpreneur * https://twitter.com/develpreneur * http://linkedin.com/develpreneur

Transcript Text
[Music]
hello and welcome back we are hanging
out here a little bit we've hit record
as far as you know anyway we' hit record
after a series of edits and things like
that and we're thinking about our our
this is going to be the last episode
other than a recap episode so you know
this is the penultimate episode as they
say I like using that word because it
makes it sound more impressive than it
is so I'm thinking for our topic is uh
let's do like a ride off into the sunset
kind of thing let's talk
about um it's sort of like succession
planning but it's basically like when do
you talk a little bit about like hanging
them up and saying okay I'm done with
this what does that look like and maybe
thinking about things like retirement
and things like that
and this will be an interesting because
I I'm not retired yet I'm pretty sure
you're not retired yet so this isn't
something necessar that we have
experienced as much but I think it's
some things that we can maybe throw some
thoughts out there as we are you know
starting to get sort of towards that but
also we know some people that have and
maybe see where we can throw some things
for people that are uh where they may
need to start thinking about it now even
though it's 10 or 15 or even 20 years in
the future how's that sound I like that
within that conversation though we have
we haven't necessarily hung up our hats
but we have done side hustles that
didn't work or weren't going anywhere
and we have looked at them and no one to
shut them down and to Pivot to something
else I think that works with this
conversation what do you think
I think yeah I think that's a good thing
to add as well is be because there are
going to be it's maybe it's a little bit
when to call it quits because there is
going to be something like that where
it's like okay well what happens if
you're done with that side hustle
whether you move on to another one or or
you're retiring or you're closing it or
whatever it happens to be um yeah I
think that actually I think we can talk
about that a little bit it's like what
happens when you're getting to the end
of your journey in a business as well as
your your journey as a developer
uh we can talk about both of those I
think a little bit sound
good well hello and welcome back we are
building better developers we are
developing numers this is the
penultimate episode of this season I
just like using that word a lot it just
like I said it sounds cool you always
see like horns in the background or
something like that or a little confetti
going off or whatever my name is Rob
Broadhead I am one of the founders of
develop preneur also a founder of RB
Consulting where we help you take your
technology sprawl and turn it into
something that is manageable and gonna
work better for you we use that we use
simplification we use automation we use
integration we look at what you've got
where you need to go and help you build
the better vehicle to get there the
better solution to get for where you are
to tomorrow and 6 months 6 years 60
years down the road okay 60 is a little
far because technology is going to
change too much but we try to make you
as future proof as possible in the world
of good things and bad
things let's see where do I want to go
oh good things let's start with my good
thing
is I'm I'm working from home this week
I've got like a a schedule that allows
me a little bit more freedom during the
day I haven't been in as many meetings
and stuff like that which I guess is
good in itself but a bonus was I got
like some rays of sunshine the other day
just yesterday I guess it was in the
middle of the day I wasn't in the middle
of the meeting and I was perfectly set
up to say you you know what I can go
knock out mowing the yard so I was able
to like take advantage which is one of
the values of working remotely is take
advantage of that and be able to get a
couple of chores done at like the the
perfect kind of weather and time to do
that uh so I guess that's my good thing
bad
thing bad thing bad thing but boy I've
had so much good lately bad bad bad bad
bad bad bad I may have to punt on the
back cash now I got I I came into this
trying to think a bad thing and I'm
really struggling with the bad thing
what have I done bad lately um oh bad
thing I'll give you a bad
thing this actually came out of a good
thing so sometimes you have a situation
where you've got a like I had you have a
customer sort of come out of the blue
and they're like hey we've got to do
some stuff cool you dive in let's do it
and it's not a uh let's get ready and
then they just disappear it's like
you're working with you're doing some
stuff and you think it's going to
continue and you're like sort of ramping
up and then it's like and it doesn't and
then suddenly they just sort of like oh
no wait we really don't need it and it's
not it's not like getting laid off it's
not like you know a project necessarily
being canceled or anything it's just
like you thought that this was going
somewhere else or you were moving it's
like you had all the momentum and then
suddenly it stops and it's you know it's
business it's what it is it's just like
oh okay well we're done it's like you're
working to the end of a project and it's
like bam okay we're done and it's like
it's jarring because you're like you're
moving forward really fast on this thing
and all a sudden you're done and it's
like whoa It's like you hit a brick wall
so that's my bad thing is I just had one
of these happen where I was like okay I
gotta get all this stuff done and I was
like oh wait no I don't it's done like
all right moving on also moving on in
this podcast we're gonna go talk to Mike
on the other side and allow you to
introduce
yourself hey everyone my name is Michael
balash one of the co-founders of
developer ner building better developers
I'm also the founder in QA where we help
small midsize companies
clinicians help them with their
technology stack their software and
actually help them with existing
development Cycles or Stacks as well we
can help you really ramp up your
development Cycles reduce bugs with
utilizing automation testing and
redefining or defining what it means to
test your software good and bad uh I'll
start with the bad CU you're good with
the fact that you were able to actually
get out and mow the lawn I have not been
able to I have had rainy days every
chance I get to try and get out and do
my tours in the yard and when you own a
large sck of land that can be very timec
consuming and doesn't work good side
however is the weather's starting to get
better we're starting to get into the
fall I won't have to do that very much
longer uh and I get a few months off
from that so good and bad nice those are
that's a good pair there this episode
because it is the penultimate
episode we're going to talk about ending
your developer journey to some extent we
this has been the developer Journey so
we are reaching the end now we want to
talk about this in two different ways
that you end your journey there is the
ending your journey that you riding off
in the sunset and you are no longer
caring about being a better developer
because you are wrapping up your career
we are not there yet so there's going to
be just sort of like some things that
we've lessons learned from other people
people and so take it with a big grain
of salt or a big whole salt shaker of
salt the other thing is when you're
ending uh it's not necessar it's not a
career but it's a path whether it's a
side hustle whether it is uh actually I
think we also want to talk about because
this is a very good one is ending a job
when you're moving from one job maybe
into of you know your side hustle
becomes full hustle or going from one
job to another wrapping things down and
this isn't I want to take this we're
going to look a little bit not just at
like a project level but things like
okay we're moving on to the next thing
and some of the key things I want to
like this almost feels like harping on
things because it's a lot of the stuff
that we've talked about throughout the
season one of the things you want to be
able to do when you are wrapping
something up whether it is actually a
project whether it is moving to a new
job or whether you are looking to uh you
know stop your developer career to close
the door on that is to
document is to make sure that you have
what you use on a daily basis for sure
it's not like you know how to code but
it is like what are some of the
processes there what are some of the the
key things like what are the servers
that you connect to maybe even usernames
and passwords and particularly one of
the things that becomes a problem a lot
is emails that are automated that go to
you and this is a thinking usually that
it's going to be handed off to somebody
else if you're just going to shut
everything down and you don't care if
anybody ever talks to you again and none
of your work is ever going to be carried
on then you don't have to worry about
this it's very simple you shut the
laptop off or your desktop you unplug it
right off in the sunset that almost
never happens there's almost always
needs to be some continuity of knowledge
and of
processes all the more so when you're
leaving a company now leaving a company
sometimes they're going to be very they
are going to be very much a part of what
you can or should do because sometimes
it's things like hey if you give notice
they're just like go away you can you
gave two weeks notice but you're not
going to show up here again because
security and stuff like that there could
be other reasons around it as well but
if that's not the case or if you know
it's coming just make sure that you are
putting things in place that your house
is in order so that you can hand the
keys over to somebody else and say here
you go along with this is going to be
like I said it's going to be things like
documenting things it's going to be
looking at who are the who are the
contacts that you deal with to make sure
that people have contact information for
those contacts emails that come in
making sure that the people that email
you know that you are going to be
handing that off a lot of times this
includes some sort of a a call or
something like there or a meeting or
something where you're like hey Rob is
leaving let me introduce you to Mike
you're his problem now you know so it's
you're GNA do it a little better than
that but something along those lines
that you can do a hand off and you can't
hand off by being like it's not a dump a
bunch of stuff on somebody's lap and go
here you go bye have fun it is actually
handing it to them so they can look at
it and making sure that they can be
successful picking up where you left off
those are the kinds of things you want
to do because you want to you put all
this work into this whether it's a
company whether it's a project whether
it's you know whatever it is whether
it's your entire career don't screw it
up or you know tarnish it by not
allowing it to be handed off properly
now when you're getting into these
things take a look at like also if you
know you're coming into like if you're
winding something down or you're uh
you've got a company that you want to
close make sure that you are signaling
to customers and things like that and
this is a good example is there's a
company that I I deal with just I'm on
one of their you know mailing list and I
just got something them that said hey by
the way we're going to close down at I
think it's the end of the year and they
sell products physical products so it is
them saying we're going to be closing
down we're not going to be making those
products anymore if you need those
products in the future they didn't say
you know here are links but they said
there are other people out there there
are other providers or other vendors so
go check them out we know they're out
there see what you like see what you
don't like so they they didn't even you
they didn't even have to recommend even
but they just said hey we're giving a
heads up this is what's happening so
that the customers don't feel like they
were hung out to dry like for example
actually I think Michael was there one
time we had or maybe think was we had a
lunch on a Friday at a restaurant and we
came back like Monday or Tuesday to have
lunch there again the business was
closed Friday nobody knew everybody was
like hey let's go fine great we come in
a couple days later we're like there's
nobody in there the doors are locked
what the heck they were should they
should be open and we we had to dig
around I think to figure out that it was
closed so don't do that to your
customers let them know and that
includes your boss I know there's always
politics and personality and all that
kind of stuff and I hate this job or
whatever it happens to be that could
come up try to take the high road and
try to do all the right things to make
sure that you're making the right
notification even if you say even if you
if you offer to say hey I'm going to
like I'll work on train I can cross
train the next person or something like
that even if the company doesn't really
offer you the opportunity to do that try
to take advantage where you can whether
it's you know if you if you can't go to
that person and spend a little time with
them even if it's like have a lunch or a
dinner or something to hand stuff off at
least put again documentation together
so that when they sit down you can say
here's a folder this is what you need to
know uh you also have been through more
than a few changes in your career so
what are some of your thoughts on
these yeah so let me start with the
developer Journey side of things
so throughout my Development Career like
you said there are times when you give
notice and you're just walked out the
door for security reasons I've worked
for a couple companies where you had to
have security clearance to even get into
the building and then you had to have
even more security clearance to get into
certain
areas if you're in one of those
situations and you're going to be
leaving you definitely want if you want
to make sure that you leave in good
standings which you almost always should
even if there's friction or tension
within a job you never know who's going
to go somewhere else that you're going
to go to in the future and find out your
black ball so always try to leave
think in terms of software always try to
leave things in a better place than
where when you start it so in those
situations TR like you said like Rob
said try to document what your pro what
your tasks are because your job role
from the day you started to today is
probably not the same job role and if
you're in a very small company or a
small team if they need to replace you
if they were to go out and just dig out
the old job requirements and try to go
hire someone they're probably not to get
what they need from the next candidate
to fill that position or to do that job
so maybe kind of write down your tasks
what it is that you do daily what is
required to do your job and sometimes
that may mean oh they have to go hire
more than one
person another time I was
transitioning L the company really
didn't want to leave but due to
financial stipulations with the company
there really was was no more upward
momentum there was really nowhere to go
and you just hit that ceiling and it's
really hard because they tried to find
something else for me to do to keep me
but they just financially much better
offers out in the
industry I had to leave however I did
give them 30 days notice because this
was one of those situations where I was
the lynchman I was the only person who
had been doing this task for seven years
no one else in the company knew what I
did or how I did it so in that situation
I literally had to document everything I
did I recorded videos I transcribed
everything I sat down with multiple team
members to walk them through the process
and I really do feel I left them in a
better place than when they started one
they had almost minimal automation of
their application Suite
by the time we left we went from maybe a
couple hundred test Suites to over
20,000 automated tests running against
her system but I built that entire
framework and that for that company so
really they had no none of this
information so I documented it all I put
it all together the best part was which
to me was kind of a mixed blessing was 6
months later I'm still friends with my
old manager and he was like you know we
had hire two people to take over for
your task but you left us in such a good
place they were able to just sit down
pick it up and roll with it and that's
really a good thing to hear if you're
handing off a project even if you're
within the company moving to a different
department if you really liked what you
did you don't want it to crash and burn
you really want it to succeed so those
are some of the good success stories bad
success or bad stories are when you do
give that notice and they literally walk
you out the door and in that kind of
position it's really sad because you
know and I've heard this more than one
times from people I've worked with
before they had no idea what it is that
you did they don't by walking you out
the door they literally shut down the
project
because they didn't take the time they
didn't think there was no conceptional
thought to why you know why you left or
what it is that you were doing do we
have everything that we need so from a
business perspective if you are going to
walk someone out the door or get rid of
someone make sure you know what they do
passwords emails things of that nature
like Rob mentioned now transition out of
our development Journey out of working
for a business to side hustles and
working in your business if you're doing
this
full-time from a side hustle
perspective at one
time and Rob I think we were working it
for recruiters or something else at that
time but there have been times in my
career where I've had multiple side
hustles going at once CU I wanted to try
different things and they didn't quite
fit into one one hat so I actually spun
up five different companies one time for
different things I helped my wife spin
up an online uh store selling uh knives
I did a kind of a fan based Doctor Who
website that it just finally shut down I
actually had it sitting around for three
years I was doing nothing with it
thinking boy why am I paying for this if
I'm not doing anything with this and you
get to that point where it's you forget
about it you probably need to shut it
down but before you do shut some things
down like that if you took the time to
write something or have some
intellectual property make sure you back
that up because you want to make sure
you have that CU if someone steals that
you want to make sure that you can say
hey no that's my property you can't take
that on the flip side of that because of
covid and because I've had some
customers that have aged out and some
have passed you will run into situations
where companies that you work for shut
down but they'll want you to help them
shut down because sometimes you can't
just turn the lights off and walk out
the door if you're a financial
institution a healthcare institution you
still have to hold on to patient records
or certain Financial documentation for
years after a company closes so if
you're in the process of helping them
shut down or shutting down yourself
these are some things you need to think
about and actually plan for before you
just turn the lights out and walk away
so you need to kind of have an exit
strategy for a business or helping a
business kind of shut
down so I wanted I'm sorry go ahead I
was just going to say your thoughts yep
uh a couple quick hits because there's a
there's a lot of places we can go with
this um one of them is that when you're
shutting something
down one is there's two things to
consider and this sort of goes to this
you know making sure that you have
backups and things like that is there is
your for your purposes and then also for
your customers purposes now a lot of us
do software and things of that nature so
you do need to consider things like do I
give a repository or source code over to
a customer do I uh do I give them the
keys to the kingdom for you know like my
GitHub account or something like that or
do I share it over do I make them an
administrator uh there are you know are
there servers that maybe you have that
you were they were leasing through you
or something like that you need to move
those servers somewhere else for them or
allow them to have full access while
you're doing that now you don't want to
be the jerk which a lot of people had
where you just shut it down and now
they've got to go figure out a way to do
all of that moving themselves you want
to allow them as much as possible access
so that they even though you don't have
to do it for them it's ideal if you give
them some way to transfer out if not at
least give them full access so they can
do so as much as makes sense for your
business now there can be you know
there's issues around all of that so
take each case on a case-by casee BAS
you also want to make sure like Michael
mentioned if you have any IP any
intellectual property if you're shutting
down a business if there's anything that
you put into that then make sure that
you have a way to access that again for
example when we shut down it for
recruiters we had numerous things that
we had put together there were uh
classes there were blog articles there's
a whole bunch of stuff we still have
somewhere not exactly sure where it is I
could find it if I really needed to it
um all of the BL all of that site we
have the database backed up we could go
respin that site up if we needed to I've
actually done it once or twice to find
like a couple of things we also have all
of our documentation is sitting out on a
an archived folder somewhere so we can
go back and get things and we actually
did in a couple of cases like I think it
was a couple years later we came back
and actually repurposed some of the
lessons that we had and helped another
company build out some of their lessons
based on that so you want to do that
when I shut down the blessing not
stressing podcast I still have same
thing I have the database for it I have
the site I could spin it back up if I
needed to I also made sure one that
because it was a podcast I actually left
the podcast side of it up for quite a
while so even though it had been dormant
for a long time it was still live in
apple podcast even though I think they
showed in a lot of the other podcast
places they showed that it was uh not
active because there hadn't been a u
there hadn't been an episode released in
a certain amount of time which is funny
because if you listen for example to
Hardcore History Dan Carlin sometimes
will go a year before he turns another
episode out it's still active but it
will show is not active because he
hasn't cranked one out
recently but I did take when I did that
I took also copied down the audio for
every single episode because I wanted to
make sure that I had backups of every
one of those if I ever for whatever
reason ever needed to go back to them
because you may want to repurpose stuff
this is particularly if you go from one
company to another now there can be uh
licensing and legality issues and stuff
like that that it may be that what you
built you didn't own and you're not
allowed to do that but for the stuff
that you did definitely want to do that
and a lot of times you need it just
again it's almost cya but it's also just
to go back if somebody a year later says
hey how did you do that or what did you
do or who did you email or something
like that it is useful to do that that
includes like if you're Outlook
extracting the little Outlook files your
little inbox or whatever I forget PST
files I think is what they're called uh
if you're whatever you know wherever you
can back up and store and archive that
information and it may be that you don't
hold on to it but put it somewhere there
to say hey by the way this is my you
know maybe it's your personal network
drive out there at the company to say
here's all of my stuff so somebody knows
where to go for it also be like I said
be be prepared to
uh hand some of that stuff off maybe
have a a meeting where you can say
here's all the code and by the way
here's how here's the build scripts
here's how you build it knock yourself
out something along those
lines that's quite a bit but you
probably did quite a bit potentially you
spent years working there so there could
be quite a bit going on and there are
people that I've talked to that have
that I've been involved with where I've
I've helped people shut down their
career sometimes in a couple cases where
it was basically their entire career was
spent in this company 20 30 years and
ramping things down and helping find the
next person to replace them uh so you
know it's I've watched this and a lot of
it does come down to unfortunately
enough a lot of it comes down to
documentation comes down to really
making yourself if you're that person
making yourself sit down probably on a
daily basis and get your thoughts to
paper about the things you do and it's
helpful if you've been there a long time
if you're looking at retiring or
shutting a business down take months
spend a quarter or more ramping things
down making sure that you're taking care
of this stuff your you know payments are
being dealt with so that you can shut
all that stuff down so if there's
licenses and stuff like that that those
are all being closed down and they're
not Auto renewing all of those kinds of
things that being said we are wrapping
up this pin ultimate episode of this
season I could say that at least one
more time and I want you still we're not
done this is not our last season we are
going to step into the next season we're
going to have lots of nuggets and
challenges and and key things to do each
episode a good action item for building
a better developer how do you and for
you whoever you are yeah you to that guy
in the back all of you people including
us what are things we can do to become
better developers and there will be
these shorter term and longer term
things a lot of it's going to be about
habits and things of that nature so
shoot us an email info develop and
or.com you can contact us out on
developer.com there's a contact form you
can check us out on XD developer develop
preneur d v l p r Nur R you can also
check us out we have a Facebook page we
have LinkedIn we have a lot of those
things you can leave comments out on
YouTube you can leave comments wherever
you get your podcast you can leave those
comments out on our our site if you want
to do it definitely give us your
thoughts what are some things maybe that
you would that you have if you have some
suggestions or some things that you
would like to say hey I struggle with X
and I would like not Twitter but like I
I struggle with this thing and I would
like to figure out how can I better do
that how can I become better at it and
we're going to have all kinds of
suggestions for that related to wherever
you are in your career and how you can
better yourself that being said why
don't you go out there and have yourself
great day a great week and we will talk
to you on the final the ultimate episode
for this season have yourself a good one
bonus
material so one thing I want to throw
out that I didn't touch on during the
podcast is if you are shutting a
business down or you're shutting a
project
down make sure that if you are keeping
your intellectual property or you're
keeping any of your media your emails
things of that nature one make sure that
when you store it somewhere you're
storing the
unsecured information there's been a
couple times where I've backed up my
email messages and it's tied to an
exchange server and even though I've
exported them I still can't get them so
make sure you export them to a
non-secured
folder secondly make sure you back up
your media to Media that's going to be
around
if you want to keep looking at it or
maintaining it I found floppy
discs that I had information on and I
had to go buy an external floppy drive
thank God to get something that was a
little outdated but was actually
something really cool I did back in
college that I wanted to pull out and
show my daughter Well that took about
three months to get that one little
files in some additional cost so make
sure you store it on media that is going
to be around if you need to
old-fashioned printer print stuff out
you know that lasts for quite a long
time you know unless you have a fire or
water damage CDs a little more fuzzy
since a lot of more computers these days
don't have CD or DVD drives or even
Blu-ray drives uh definitely hard drives
are pretty much de facto they've been
around for a long time and there's a lot
of adapters and that for using those you
have external drives things of that
nature be careful of cloud
backup Some Cloud backups that were
around 10 years ago are not around today
so be very cautious about that so if you
back anything up I recommend to do it to
something physical and something that is
maintainable or at least will be around
for at least 20 to 30 years uh because
depending upon where you're at within
your career you may need to transfer
that at some point to maintain that but
if you're retired that's probably about
all the time you need to really care
about it because your kids aren't going
to to pick it up and they're not going
to care about it the last thing I want
to touch on is if you have any type of
GitHub or repository where you have
source code that you have put a lot of
effort into but you're done with
it think about open sourcing it maybe
find another contributor put it out
basically put it out there hey it's like
hey this had a good run anyone that
wants to continue give it to the
community and let it Thrive you never
know it could turn out to the next big
Blockbuster or you might save someone a
headache down the road by them looking
at and say hey this is exactly what I
need let me go tweak this and hey you
just made someone stay so just some
ideas to kind of keep your legacy going
or at least keep a backup of it in case
you ever need to revisit it I'll keep it
short and follow it up with the Version
Control thing is uh well two things I
guess I will go back definitely keep an
idea an eye on your media devices I have
done this same thing I have done stuff I
just accidentally I don't know why I
raised my hand it was like I have my
hand i'm talking with my hands too much
I'm sorry I'm just going to sit on my
hands um I recently have gone back
through because I've been doing some
cleaning and I have I've had some stuff
I've got five and a quarter inch floppy
disc I have got the three and a half
inch hard Diss and I have got actually I
have what was called a zip Drive which
would be one of those things I have the
discs the drive piece of crap right now
I don't think I could find one anywhere
so I should have at some point pulled
off of those I also was burning CDs and
so I do have cd backups and I have
literally just for such an occasion and
because I occasionally like to run music
on my laptop or something like that when
I'm running around I do have a USB CD
drive so I can use that and now I've had
to it's USB and I think I'm now going to
have to change the plugs because I have
apple stuff and they keep upgrading
these things so you may have to do that
you may have to periodically check out
your backups if you need them if you're
you know if you're riding off into the
sunset you probably won't have to worry
about it if you're like thinking like
Michael like hey I might want to look at
this 20 years from now then you may have
to continue to move your stuff forward
in a similar sense don't try if you
whatever you used for your version
control back up a withdrawn a pull pull
it out and zip up or however you do it
compress The Source or ideally don't
even compress The Source put it
somewhere where you can store it that is
not within the Version Control System I
happened to actually back up a long time
ago my I had an RCS Version Control
piece actually I also had a uh Source
safe I think is what it was called the
old Microsoft I had Source safe stuff
that I just backed up the whole kit and
Kaboodle the whole server that or that
piece of it and then later when I wanted
to go digging it up I had to go find the
server piece of it to be able to connect
to it to be able to pull the stuff out
and extract it all and actually at that
point I actually took all that crap and
shoved it up into GitHub because I'm
like all right I'm going to put it into
a git repository and like get it out of
the way but you know be careful what you
use like Michael said be careful what
you use to store your stuff because if
it's a technology that technology might
disappear cloud is great but always you
should have physical copies somewhere as
well and as I say this I sort of panic
because I'm thinking about all the code
that I have out in GitHub and other
places that I don't actually currently
have a physical other than my you know
my devices I don't have other physical
copies so I may be spending a couple of
weekends in the near future pulling
stuff down and burning it to a disc or
something like that that being said time
to wrap this one up we will come back
next time for the ultimate episode of
this season the final one we have
finished our journey and we're going to
talk about that Journey again and maybe
do a little bit of a we'll do our you
know like a Sprint we're going to get to
the end we're going to do a little
retrospective and then we'll be into
season 23 so as always reach out however
you feel like reaching out to us even
smoke signals we'll figure it out we'll
get that information that'll help us
help you as we grow into this next
season as always go out there and have
yourself a great one and we will talk to
you next time
[Music]
Transcript Segments
1.35

[Music]

27.119

hello and welcome back we are hanging

29.279

out here a little bit we've hit record

31.359

as far as you know anyway we' hit record

34.28

after a series of edits and things like

36.96

that and we're thinking about our our

39.68

this is going to be the last episode

43.079

other than a recap episode so you know

46

this is the penultimate episode as they

48.079

say I like using that word because it

49.64

makes it sound more impressive than it

51.039

is so I'm thinking for our topic is uh

55

let's do like a ride off into the sunset

56.719

kind of thing let's talk

58.079

about um it's sort of like succession

60.559

planning but it's basically like when do

62.039

you talk a little bit about like hanging

64.08

them up and saying okay I'm done with

66.159

this what does that look like and maybe

68.64

thinking about things like retirement

70.6

and things like that

73.159

and this will be an interesting because

75.479

I I'm not retired yet I'm pretty sure

77.2

you're not retired yet so this isn't

79.159

something necessar that we have

80.24

experienced as much but I think it's

81.56

some things that we can maybe throw some

83.119

thoughts out there as we are you know

85.6

starting to get sort of towards that but

87.92

also we know some people that have and

89.92

maybe see where we can throw some things

91.24

for people that are uh where they may

93.68

need to start thinking about it now even

96.32

though it's 10 or 15 or even 20 years in

98.68

the future how's that sound I like that

102.56

within that conversation though we have

105.399

we haven't necessarily hung up our hats

107.56

but we have done side hustles that

109.24

didn't work or weren't going anywhere

111.28

and we have looked at them and no one to

113.6

shut them down and to Pivot to something

115.68

else I think that works with this

117.96

conversation what do you think

120.36

I think yeah I think that's a good thing

121.6

to add as well is be because there are

123.399

going to be it's maybe it's a little bit

125.88

when to call it quits because there is

127.719

going to be something like that where

128.759

it's like okay well what happens if

131.2

you're done with that side hustle

132.8

whether you move on to another one or or

134.76

you're retiring or you're closing it or

136.599

whatever it happens to be um yeah I

140.28

think that actually I think we can talk

141.519

about that a little bit it's like what

142.519

happens when you're getting to the end

144.12

of your journey in a business as well as

147.8

your your journey as a developer

150.4

uh we can talk about both of those I

151.959

think a little bit sound

155

good well hello and welcome back we are

158.76

building better developers we are

160.4

developing numers this is the

162.44

penultimate episode of this season I

164.68

just like using that word a lot it just

166.4

like I said it sounds cool you always

167.92

see like horns in the background or

169.28

something like that or a little confetti

170.48

going off or whatever my name is Rob

173.36

Broadhead I am one of the founders of

175.04

develop preneur also a founder of RB

178.84

Consulting where we help you take your

182.239

technology sprawl and turn it into

184.12

something that is manageable and gonna

187.56

work better for you we use that we use

189.599

simplification we use automation we use

191.599

integration we look at what you've got

193.68

where you need to go and help you build

195.84

the better vehicle to get there the

197.519

better solution to get for where you are

200.12

to tomorrow and 6 months 6 years 60

203.599

years down the road okay 60 is a little

205.84

far because technology is going to

206.959

change too much but we try to make you

208.64

as future proof as possible in the world

211.28

of good things and bad

212.959

things let's see where do I want to go

215.4

oh good things let's start with my good

217.879

thing

219

is I'm I'm working from home this week

221.84

I've got like a a schedule that allows

223.959

me a little bit more freedom during the

225.959

day I haven't been in as many meetings

227.4

and stuff like that which I guess is

229

good in itself but a bonus was I got

231.68

like some rays of sunshine the other day

234

just yesterday I guess it was in the

235.72

middle of the day I wasn't in the middle

237.72

of the meeting and I was perfectly set

239.239

up to say you you know what I can go

240.72

knock out mowing the yard so I was able

243.519

to like take advantage which is one of

245.36

the values of working remotely is take

248.12

advantage of that and be able to get a

249.319

couple of chores done at like the the

251.36

perfect kind of weather and time to do

254

that uh so I guess that's my good thing

257.16

bad

258.359

thing bad thing bad thing but boy I've

260.759

had so much good lately bad bad bad bad

264.8

bad bad bad I may have to punt on the

267.24

back cash now I got I I came into this

269.24

trying to think a bad thing and I'm

271.84

really struggling with the bad thing

274.84

what have I done bad lately um oh bad

278.479

thing I'll give you a bad

280.68

thing this actually came out of a good

282.919

thing so sometimes you have a situation

285.12

where you've got a like I had you have a

286.8

customer sort of come out of the blue

288.36

and they're like hey we've got to do

289.52

some stuff cool you dive in let's do it

294.16

and it's not a uh let's get ready and

297.6

then they just disappear it's like

298.96

you're working with you're doing some

300.44

stuff and you think it's going to

302.199

continue and you're like sort of ramping

305

up and then it's like and it doesn't and

307.52

then suddenly they just sort of like oh

308.84

no wait we really don't need it and it's

310.56

not it's not like getting laid off it's

313.36

not like you know a project necessarily

315.32

being canceled or anything it's just

316.72

like you thought that this was going

318.319

somewhere else or you were moving it's

320.36

like you had all the momentum and then

322.72

suddenly it stops and it's you know it's

326

business it's what it is it's just like

327.56

oh okay well we're done it's like you're

329.08

working to the end of a project and it's

330.639

like bam okay we're done and it's like

333.28

it's jarring because you're like you're

334.919

moving forward really fast on this thing

337

and all a sudden you're done and it's

338.08

like whoa It's like you hit a brick wall

339.88

so that's my bad thing is I just had one

341.4

of these happen where I was like okay I

342.96

gotta get all this stuff done and I was

344.039

like oh wait no I don't it's done like

346.199

all right moving on also moving on in

349.12

this podcast we're gonna go talk to Mike

350.759

on the other side and allow you to

352.199

introduce

353.24

yourself hey everyone my name is Michael

355.36

balash one of the co-founders of

356.639

developer ner building better developers

358.68

I'm also the founder in QA where we help

361.44

small midsize companies

363.96

clinicians help them with their

366.52

technology stack their software and

369.479

actually help them with existing

371.84

development Cycles or Stacks as well we

374.639

can help you really ramp up your

377.24

development Cycles reduce bugs with

379.36

utilizing automation testing and

382.199

redefining or defining what it means to

384.84

test your software good and bad uh I'll

387.8

start with the bad CU you're good with

389.759

the fact that you were able to actually

390.96

get out and mow the lawn I have not been

393.599

able to I have had rainy days every

396.08

chance I get to try and get out and do

398.319

my tours in the yard and when you own a

401.16

large sck of land that can be very timec

404

consuming and doesn't work good side

407.36

however is the weather's starting to get

409.68

better we're starting to get into the

410.84

fall I won't have to do that very much

412.919

longer uh and I get a few months off

415.52

from that so good and bad nice those are

419.199

that's a good pair there this episode

422.639

because it is the penultimate

425.12

episode we're going to talk about ending

428.319

your developer journey to some extent we

430.16

this has been the developer Journey so

431.479

we are reaching the end now we want to

433.4

talk about this in two different ways

435.28

that you end your journey there is the

437.44

ending your journey that you riding off

439

in the sunset and you are no longer

440.44

caring about being a better developer

442

because you are wrapping up your career

445.039

we are not there yet so there's going to

446.56

be just sort of like some things that

447.919

we've lessons learned from other people

449.52

people and so take it with a big grain

452.44

of salt or a big whole salt shaker of

455

salt the other thing is when you're

458.52

ending uh it's not necessar it's not a

461.56

career but it's a path whether it's a

463.24

side hustle whether it is uh actually I

465.759

think we also want to talk about because

467.039

this is a very good one is ending a job

468.919

when you're moving from one job maybe

470.599

into of you know your side hustle

472.319

becomes full hustle or going from one

474.36

job to another wrapping things down and

476.96

this isn't I want to take this we're

478.72

going to look a little bit not just at

480.4

like a project level but things like

482.4

okay we're moving on to the next thing

485.319

and some of the key things I want to

487.4

like this almost feels like harping on

489.12

things because it's a lot of the stuff

490.36

that we've talked about throughout the

492.8

season one of the things you want to be

495.039

able to do when you are wrapping

496.8

something up whether it is actually a

499.199

project whether it is moving to a new

501.039

job or whether you are looking to uh you

504.039

know stop your developer career to close

507.159

the door on that is to

510.12

document is to make sure that you have

513.8

what you use on a daily basis for sure

518.24

it's not like you know how to code but

520.12

it is like what are some of the

521.279

processes there what are some of the the

523.399

key things like what are the servers

525.24

that you connect to maybe even usernames

527.24

and passwords and particularly one of

529.36

the things that becomes a problem a lot

530.959

is emails that are automated that go to

533.24

you and this is a thinking usually that

535.68

it's going to be handed off to somebody

537.2

else if you're just going to shut

538.44

everything down and you don't care if

539.68

anybody ever talks to you again and none

541.44

of your work is ever going to be carried

542.839

on then you don't have to worry about

544.079

this it's very simple you shut the

545.399

laptop off or your desktop you unplug it

548.04

right off in the sunset that almost

549.88

never happens there's almost always

551.24

needs to be some continuity of knowledge

554.8

and of

556.44

processes all the more so when you're

558.56

leaving a company now leaving a company

560.839

sometimes they're going to be very they

563.399

are going to be very much a part of what

564.92

you can or should do because sometimes

567.44

it's things like hey if you give notice

569.079

they're just like go away you can you

570.72

gave two weeks notice but you're not

571.92

going to show up here again because

573.64

security and stuff like that there could

575.399

be other reasons around it as well but

578.48

if that's not the case or if you know

580.24

it's coming just make sure that you are

583.04

putting things in place that your house

584.959

is in order so that you can hand the

586.48

keys over to somebody else and say here

589.12

you go along with this is going to be

591.519

like I said it's going to be things like

592.88

documenting things it's going to be

594.36

looking at who are the who are the

595.8

contacts that you deal with to make sure

597.8

that people have contact information for

599.44

those contacts emails that come in

601.48

making sure that the people that email

603

you know that you are going to be

605.2

handing that off a lot of times this

606.88

includes some sort of a a call or

609.64

something like there or a meeting or

610.839

something where you're like hey Rob is

613.279

leaving let me introduce you to Mike

615.839

you're his problem now you know so it's

617.92

you're GNA do it a little better than

619.2

that but something along those lines

620.72

that you can do a hand off and you can't

623.959

hand off by being like it's not a dump a

626.36

bunch of stuff on somebody's lap and go

628

here you go bye have fun it is actually

630.519

handing it to them so they can look at

632.279

it and making sure that they can be

634.48

successful picking up where you left off

637.399

those are the kinds of things you want

638.44

to do because you want to you put all

639.92

this work into this whether it's a

642.16

company whether it's a project whether

644.76

it's you know whatever it is whether

646.279

it's your entire career don't screw it

649.079

up or you know tarnish it by not

651.92

allowing it to be handed off properly

654.92

now when you're getting into these

656.12

things take a look at like also if you

658.36

know you're coming into like if you're

659.72

winding something down or you're uh

662.16

you've got a company that you want to

663.72

close make sure that you are signaling

666.959

to customers and things like that and

669.56

this is a good example is there's a

671.04

company that I I deal with just I'm on

674.68

one of their you know mailing list and I

677.12

just got something them that said hey by

678.639

the way we're going to close down at I

680.839

think it's the end of the year and they

683.279

sell products physical products so it is

686.24

them saying we're going to be closing

688.079

down we're not going to be making those

689.6

products anymore if you need those

691.56

products in the future they didn't say

694.2

you know here are links but they said

695.8

there are other people out there there

697.12

are other providers or other vendors so

699.519

go check them out we know they're out

701.56

there see what you like see what you

702.959

don't like so they they didn't even you

704.6

they didn't even have to recommend even

706.56

but they just said hey we're giving a

708.6

heads up this is what's happening so

711.04

that the customers don't feel like they

713.44

were hung out to dry like for example

716.079

actually I think Michael was there one

717.36

time we had or maybe think was we had a

720.88

lunch on a Friday at a restaurant and we

724.079

came back like Monday or Tuesday to have

726.079

lunch there again the business was

728.279

closed Friday nobody knew everybody was

732.12

like hey let's go fine great we come in

734.56

a couple days later we're like there's

736.76

nobody in there the doors are locked

738.68

what the heck they were should they

740.12

should be open and we we had to dig

742.32

around I think to figure out that it was

743.839

closed so don't do that to your

745.88

customers let them know and that

748.199

includes your boss I know there's always

750.32

politics and personality and all that

751.68

kind of stuff and I hate this job or

752.88

whatever it happens to be that could

754.16

come up try to take the high road and

757.76

try to do all the right things to make

759.199

sure that you're making the right

760.72

notification even if you say even if you

764.36

if you offer to say hey I'm going to

765.88

like I'll work on train I can cross

768.04

train the next person or something like

769.48

that even if the company doesn't really

771.32

offer you the opportunity to do that try

773.72

to take advantage where you can whether

775.36

it's you know if you if you can't go to

776.959

that person and spend a little time with

778.72

them even if it's like have a lunch or a

780.16

dinner or something to hand stuff off at

782

least put again documentation together

784.24

so that when they sit down you can say

785.88

here's a folder this is what you need to

787.839

know uh you also have been through more

790.04

than a few changes in your career so

791.68

what are some of your thoughts on

793.72

these yeah so let me start with the

796.56

developer Journey side of things

798.959

so throughout my Development Career like

802.12

you said there are times when you give

804.16

notice and you're just walked out the

806.36

door for security reasons I've worked

807.92

for a couple companies where you had to

811.12

have security clearance to even get into

813.48

the building and then you had to have

814.639

even more security clearance to get into

816.48

certain

817.44

areas if you're in one of those

819.399

situations and you're going to be

822.04

leaving you definitely want if you want

824.56

to make sure that you leave in good

826.04

standings which you almost always should

828.399

even if there's friction or tension

830.199

within a job you never know who's going

833.279

to go somewhere else that you're going

834.6

to go to in the future and find out your

836.68

black ball so always try to leave

839.88

think in terms of software always try to

842.04

leave things in a better place than

844.04

where when you start it so in those

847.759

situations TR like you said like Rob

850.24

said try to document what your pro what

853.36

your tasks are because your job role

855.279

from the day you started to today is

857.759

probably not the same job role and if

859.56

you're in a very small company or a

861.6

small team if they need to replace you

864.399

if they were to go out and just dig out

865.92

the old job requirements and try to go

867.6

hire someone they're probably not to get

869.44

what they need from the next candidate

871.68

to fill that position or to do that job

874.519

so maybe kind of write down your tasks

878.399

what it is that you do daily what is

880.519

required to do your job and sometimes

883.6

that may mean oh they have to go hire

885.6

more than one

886.72

person another time I was

890.399

transitioning L the company really

892.839

didn't want to leave but due to

895.32

financial stipulations with the company

898.44

there really was was no more upward

900.199

momentum there was really nowhere to go

902.72

and you just hit that ceiling and it's

907.16

really hard because they tried to find

910.32

something else for me to do to keep me

913.079

but they just financially much better

915.92

offers out in the

917.44

industry I had to leave however I did

920.44

give them 30 days notice because this

922.44

was one of those situations where I was

924.399

the lynchman I was the only person who

926.8

had been doing this task for seven years

931

no one else in the company knew what I

933.839

did or how I did it so in that situation

937.04

I literally had to document everything I

940.199

did I recorded videos I transcribed

943.839

everything I sat down with multiple team

945.68

members to walk them through the process

949.079

and I really do feel I left them in a

951.399

better place than when they started one

954.199

they had almost minimal automation of

957.519

their application Suite

959.48

by the time we left we went from maybe a

961.6

couple hundred test Suites to over

963.839

20,000 automated tests running against

966.199

her system but I built that entire

969.399

framework and that for that company so

971.6

really they had no none of this

974.04

information so I documented it all I put

976.959

it all together the best part was which

980.12

to me was kind of a mixed blessing was 6

984.279

months later I'm still friends with my

986.399

old manager and he was like you know we

988.68

had hire two people to take over for

990.48

your task but you left us in such a good

992.279

place they were able to just sit down

994.199

pick it up and roll with it and that's

996.92

really a good thing to hear if you're

998.959

handing off a project even if you're

1000.92

within the company moving to a different

1002.72

department if you really liked what you

1005.079

did you don't want it to crash and burn

1007.16

you really want it to succeed so those

1009.56

are some of the good success stories bad

1012.36

success or bad stories are when you do

1015.44

give that notice and they literally walk

1017.24

you out the door and in that kind of

1019.639

position it's really sad because you

1022.519

know and I've heard this more than one

1025.079

times from people I've worked with

1026.76

before they had no idea what it is that

1029.199

you did they don't by walking you out

1032

the door they literally shut down the

1033.88

project

1035.48

because they didn't take the time they

1037.6

didn't think there was no conceptional

1040.679

thought to why you know why you left or

1044.76

what it is that you were doing do we

1046.439

have everything that we need so from a

1048.48

business perspective if you are going to

1050.559

walk someone out the door or get rid of

1052.64

someone make sure you know what they do

1055.039

passwords emails things of that nature

1056.72

like Rob mentioned now transition out of

1060.96

our development Journey out of working

1063.919

for a business to side hustles and

1066.36

working in your business if you're doing

1068.48

this

1069.64

full-time from a side hustle

1072.48

perspective at one

1074.799

time and Rob I think we were working it

1079.2

for recruiters or something else at that

1081

time but there have been times in my

1083.48

career where I've had multiple side

1086.24

hustles going at once CU I wanted to try

1089.96

different things and they didn't quite

1091.64

fit into one one hat so I actually spun

1095.159

up five different companies one time for

1098.36

different things I helped my wife spin

1100.76

up an online uh store selling uh knives

1104.72

I did a kind of a fan based Doctor Who

1107.76

website that it just finally shut down I

1110.919

actually had it sitting around for three

1112.96

years I was doing nothing with it

1114.44

thinking boy why am I paying for this if

1116.559

I'm not doing anything with this and you

1119.72

get to that point where it's you forget

1121.48

about it you probably need to shut it

1123.36

down but before you do shut some things

1126.24

down like that if you took the time to

1128.919

write something or have some

1130.799

intellectual property make sure you back

1133.28

that up because you want to make sure

1135.4

you have that CU if someone steals that

1137.44

you want to make sure that you can say

1139.44

hey no that's my property you can't take

1143.32

that on the flip side of that because of

1147.28

covid and because I've had some

1149.48

customers that have aged out and some

1152.799

have passed you will run into situations

1156.039

where companies that you work for shut

1159.08

down but they'll want you to help them

1162.76

shut down because sometimes you can't

1164.679

just turn the lights off and walk out

1166.6

the door if you're a financial

1168.72

institution a healthcare institution you

1170.6

still have to hold on to patient records

1172.72

or certain Financial documentation for

1175.64

years after a company closes so if

1179.32

you're in the process of helping them

1181

shut down or shutting down yourself

1182.799

these are some things you need to think

1184.32

about and actually plan for before you

1186.919

just turn the lights out and walk away

1189

so you need to kind of have an exit

1191.28

strategy for a business or helping a

1193.679

business kind of shut

1196.36

down so I wanted I'm sorry go ahead I

1200.52

was just going to say your thoughts yep

1202.919

uh a couple quick hits because there's a

1204.88

there's a lot of places we can go with

1206.44

this um one of them is that when you're

1208.88

shutting something

1210.4

down one is there's two things to

1212.88

consider and this sort of goes to this

1214.799

you know making sure that you have

1216.32

backups and things like that is there is

1219.08

your for your purposes and then also for

1222.159

your customers purposes now a lot of us

1224.88

do software and things of that nature so

1227.96

you do need to consider things like do I

1231.88

give a repository or source code over to

1234.96

a customer do I uh do I give them the

1238.84

keys to the kingdom for you know like my

1240.919

GitHub account or something like that or

1242.24

do I share it over do I make them an

1244

administrator uh there are you know are

1246.08

there servers that maybe you have that

1248.28

you were they were leasing through you

1250.72

or something like that you need to move

1253

those servers somewhere else for them or

1255.919

allow them to have full access while

1257.799

you're doing that now you don't want to

1260.4

be the jerk which a lot of people had

1262.88

where you just shut it down and now

1264.24

they've got to go figure out a way to do

1266.2

all of that moving themselves you want

1268.039

to allow them as much as possible access

1270.12

so that they even though you don't have

1271.72

to do it for them it's ideal if you give

1274.159

them some way to transfer out if not at

1276.88

least give them full access so they can

1279.48

do so as much as makes sense for your

1282.279

business now there can be you know

1284.12

there's issues around all of that so

1286.76

take each case on a case-by casee BAS

1290.08

you also want to make sure like Michael

1291.799

mentioned if you have any IP any

1294.4

intellectual property if you're shutting

1296.24

down a business if there's anything that

1297.559

you put into that then make sure that

1299.559

you have a way to access that again for

1302.279

example when we shut down it for

1304.4

recruiters we had numerous things that

1306.32

we had put together there were uh

1308.84

classes there were blog articles there's

1311

a whole bunch of stuff we still have

1313.32

somewhere not exactly sure where it is I

1315.32

could find it if I really needed to it

1317.919

um all of the BL all of that site we

1320.48

have the database backed up we could go

1322.48

respin that site up if we needed to I've

1325.2

actually done it once or twice to find

1326.76

like a couple of things we also have all

1329.36

of our documentation is sitting out on a

1331.919

an archived folder somewhere so we can

1334.84

go back and get things and we actually

1336.6

did in a couple of cases like I think it

1340.44

was a couple years later we came back

1343.039

and actually repurposed some of the

1345.32

lessons that we had and helped another

1347.32

company build out some of their lessons

1349.44

based on that so you want to do that

1351.919

when I shut down the blessing not

1354

stressing podcast I still have same

1356.2

thing I have the database for it I have

1358.32

the site I could spin it back up if I

1360.12

needed to I also made sure one that

1363.48

because it was a podcast I actually left

1365.32

the podcast side of it up for quite a

1368.919

while so even though it had been dormant

1370.84

for a long time it was still live in

1374.4

apple podcast even though I think they

1376.039

showed in a lot of the other podcast

1377.84

places they showed that it was uh not

1380.2

active because there hadn't been a u

1382.76

there hadn't been an episode released in

1384.159

a certain amount of time which is funny

1385.919

because if you listen for example to

1388

Hardcore History Dan Carlin sometimes

1390.36

will go a year before he turns another

1392.08

episode out it's still active but it

1394.52

will show is not active because he

1396.36

hasn't cranked one out

1398.36

recently but I did take when I did that

1401.12

I took also copied down the audio for

1403.799

every single episode because I wanted to

1405.799

make sure that I had backups of every

1407.64

one of those if I ever for whatever

1409.48

reason ever needed to go back to them

1412.88

because you may want to repurpose stuff

1415

this is particularly if you go from one

1416.2

company to another now there can be uh

1418.76

licensing and legality issues and stuff

1420.72

like that that it may be that what you

1422.24

built you didn't own and you're not

1423.96

allowed to do that but for the stuff

1426.12

that you did definitely want to do that

1428.4

and a lot of times you need it just

1429.88

again it's almost cya but it's also just

1431.76

to go back if somebody a year later says

1433.76

hey how did you do that or what did you

1436.44

do or who did you email or something

1437.84

like that it is useful to do that that

1439.52

includes like if you're Outlook

1441.799

extracting the little Outlook files your

1443.64

little inbox or whatever I forget PST

1445.48

files I think is what they're called uh

1447.52

if you're whatever you know wherever you

1449.52

can back up and store and archive that

1452.159

information and it may be that you don't

1453.559

hold on to it but put it somewhere there

1455.12

to say hey by the way this is my you

1457.24

know maybe it's your personal network

1458.52

drive out there at the company to say

1460.76

here's all of my stuff so somebody knows

1463.44

where to go for it also be like I said

1466.76

be be prepared to

1469

uh hand some of that stuff off maybe

1470.799

have a a meeting where you can say

1472.24

here's all the code and by the way

1473.559

here's how here's the build scripts

1475.52

here's how you build it knock yourself

1477.799

out something along those

1479.799

lines that's quite a bit but you

1483.52

probably did quite a bit potentially you

1485.32

spent years working there so there could

1487.559

be quite a bit going on and there are

1489.76

people that I've talked to that have

1491.36

that I've been involved with where I've

1492.799

I've helped people shut down their

1495.2

career sometimes in a couple cases where

1497.72

it was basically their entire career was

1500.88

spent in this company 20 30 years and

1505.039

ramping things down and helping find the

1508.679

next person to replace them uh so you

1511.88

know it's I've watched this and a lot of

1513.84

it does come down to unfortunately

1516.159

enough a lot of it comes down to

1517.52

documentation comes down to really

1519.679

making yourself if you're that person

1521.36

making yourself sit down probably on a

1523.48

daily basis and get your thoughts to

1526.48

paper about the things you do and it's

1528.799

helpful if you've been there a long time

1530.44

if you're looking at retiring or

1532.12

shutting a business down take months

1535.72

spend a quarter or more ramping things

1538.48

down making sure that you're taking care

1540.24

of this stuff your you know payments are

1542.52

being dealt with so that you can shut

1543.799

all that stuff down so if there's

1545.559

licenses and stuff like that that those

1547.399

are all being closed down and they're

1549.799

not Auto renewing all of those kinds of

1553.039

things that being said we are wrapping

1556.799

up this pin ultimate episode of this

1559.88

season I could say that at least one

1561.32

more time and I want you still we're not

1565.52

done this is not our last season we are

1567.559

going to step into the next season we're

1569.399

going to have lots of nuggets and

1571.6

challenges and and key things to do each

1574.159

episode a good action item for building

1576.399

a better developer how do you and for

1578.72

you whoever you are yeah you to that guy

1580.76

in the back all of you people including

1583.72

us what are things we can do to become

1586.919

better developers and there will be

1588.72

these shorter term and longer term

1590.76

things a lot of it's going to be about

1592.36

habits and things of that nature so

1594.36

shoot us an email info develop and

1596.159

or.com you can contact us out on

1598.6

developer.com there's a contact form you

1600.84

can check us out on XD developer develop

1603.919

preneur d v l p r Nur R you can also

1609.279

check us out we have a Facebook page we

1610.679

have LinkedIn we have a lot of those

1612.12

things you can leave comments out on

1614

YouTube you can leave comments wherever

1615.44

you get your podcast you can leave those

1617.52

comments out on our our site if you want

1620.12

to do it definitely give us your

1621.88

thoughts what are some things maybe that

1623.679

you would that you have if you have some

1625.32

suggestions or some things that you

1626.84

would like to say hey I struggle with X

1630.08

and I would like not Twitter but like I

1632.679

I struggle with this thing and I would

1635.679

like to figure out how can I better do

1638.159

that how can I become better at it and

1639.76

we're going to have all kinds of

1640.88

suggestions for that related to wherever

1642.76

you are in your career and how you can

1644.159

better yourself that being said why

1647.12

don't you go out there and have yourself

1648.32

great day a great week and we will talk

1650.799

to you on the final the ultimate episode

1654.399

for this season have yourself a good one

1657.96

bonus

1659

material so one thing I want to throw

1661.32

out that I didn't touch on during the

1664.64

podcast is if you are shutting a

1669.2

business down or you're shutting a

1670.799

project

1673.08

down make sure that if you are keeping

1676.679

your intellectual property or you're

1678.399

keeping any of your media your emails

1680.6

things of that nature one make sure that

1683.24

when you store it somewhere you're

1684.88

storing the

1686.88

unsecured information there's been a

1689.72

couple times where I've backed up my

1691.399

email messages and it's tied to an

1693.44

exchange server and even though I've

1695.08

exported them I still can't get them so

1698.559

make sure you export them to a

1700.279

non-secured

1701.919

folder secondly make sure you back up

1705.279

your media to Media that's going to be

1707.679

around

1708.96

if you want to keep looking at it or

1710.919

maintaining it I found floppy

1714.72

discs that I had information on and I

1717.12

had to go buy an external floppy drive

1719.799

thank God to get something that was a

1722.36

little outdated but was actually

1723.559

something really cool I did back in

1725.039

college that I wanted to pull out and

1727.2

show my daughter Well that took about

1730.48

three months to get that one little

1732.08

files in some additional cost so make

1734.88

sure you store it on media that is going

1737.279

to be around if you need to

1739

old-fashioned printer print stuff out

1740.679

you know that lasts for quite a long

1743.24

time you know unless you have a fire or

1744.799

water damage CDs a little more fuzzy

1748.679

since a lot of more computers these days

1750.76

don't have CD or DVD drives or even

1753.279

Blu-ray drives uh definitely hard drives

1757.279

are pretty much de facto they've been

1759.679

around for a long time and there's a lot

1761.399

of adapters and that for using those you

1764.159

have external drives things of that

1766.32

nature be careful of cloud

1769

backup Some Cloud backups that were

1771.6

around 10 years ago are not around today

1774.2

so be very cautious about that so if you

1776.48

back anything up I recommend to do it to

1778.84

something physical and something that is

1781.96

maintainable or at least will be around

1784.399

for at least 20 to 30 years uh because

1787.559

depending upon where you're at within

1788.64

your career you may need to transfer

1790.279

that at some point to maintain that but

1793.039

if you're retired that's probably about

1795.279

all the time you need to really care

1796.72

about it because your kids aren't going

1797.96

to to pick it up and they're not going

1799.88

to care about it the last thing I want

1801.88

to touch on is if you have any type of

1805.12

GitHub or repository where you have

1807.44

source code that you have put a lot of

1810.12

effort into but you're done with

1812.64

it think about open sourcing it maybe

1815.6

find another contributor put it out

1818.64

basically put it out there hey it's like

1820.36

hey this had a good run anyone that

1822.76

wants to continue give it to the

1824.24

community and let it Thrive you never

1826.64

know it could turn out to the next big

1828.64

Blockbuster or you might save someone a

1831.24

headache down the road by them looking

1833.039

at and say hey this is exactly what I

1834.72

need let me go tweak this and hey you

1836.919

just made someone stay so just some

1839

ideas to kind of keep your legacy going

1842.36

or at least keep a backup of it in case

1844.039

you ever need to revisit it I'll keep it

1847

short and follow it up with the Version

1848.84

Control thing is uh well two things I

1851.32

guess I will go back definitely keep an

1854.039

idea an eye on your media devices I have

1857.559

done this same thing I have done stuff I

1860.039

just accidentally I don't know why I

1861.639

raised my hand it was like I have my

1863.159

hand i'm talking with my hands too much

1864.36

I'm sorry I'm just going to sit on my

1865.76

hands um I recently have gone back

1868.96

through because I've been doing some

1869.76

cleaning and I have I've had some stuff

1871.6

I've got five and a quarter inch floppy

1873.559

disc I have got the three and a half

1875.44

inch hard Diss and I have got actually I

1878.799

have what was called a zip Drive which

1881.24

would be one of those things I have the

1883.679

discs the drive piece of crap right now

1887.48

I don't think I could find one anywhere

1889.039

so I should have at some point pulled

1891.6

off of those I also was burning CDs and

1894.76

so I do have cd backups and I have

1897.88

literally just for such an occasion and

1900.84

because I occasionally like to run music

1902.399

on my laptop or something like that when

1903.76

I'm running around I do have a USB CD

1907.6

drive so I can use that and now I've had

1909.36

to it's USB and I think I'm now going to

1911.48

have to change the plugs because I have

1913.88

apple stuff and they keep upgrading

1915.639

these things so you may have to do that

1917.32

you may have to periodically check out

1918.96

your backups if you need them if you're

1922.159

you know if you're riding off into the

1923.36

sunset you probably won't have to worry

1924.799

about it if you're like thinking like

1926.559

Michael like hey I might want to look at

1928.36

this 20 years from now then you may have

1930.12

to continue to move your stuff forward

1932.279

in a similar sense don't try if you

1935.6

whatever you used for your version

1938.159

control back up a withdrawn a pull pull

1942.799

it out and zip up or however you do it

1945.159

compress The Source or ideally don't

1947.96

even compress The Source put it

1949.039

somewhere where you can store it that is

1951.32

not within the Version Control System I

1954.519

happened to actually back up a long time

1957.279

ago my I had an RCS Version Control

1960.96

piece actually I also had a uh Source

1964.559

safe I think is what it was called the

1966.24

old Microsoft I had Source safe stuff

1968.2

that I just backed up the whole kit and

1970.2

Kaboodle the whole server that or that

1972.519

piece of it and then later when I wanted

1975.12

to go digging it up I had to go find the

1978.2

server piece of it to be able to connect

1980.2

to it to be able to pull the stuff out

1982

and extract it all and actually at that

1983.72

point I actually took all that crap and

1985.639

shoved it up into GitHub because I'm

1987.24

like all right I'm going to put it into

1988.48

a git repository and like get it out of

1990.519

the way but you know be careful what you

1993.36

use like Michael said be careful what

1995.12

you use to store your stuff because if

1998

it's a technology that technology might

2000.36

disappear cloud is great but always you

2004.559

should have physical copies somewhere as

2007.48

well and as I say this I sort of panic

2010

because I'm thinking about all the code

2011.2

that I have out in GitHub and other

2012.559

places that I don't actually currently

2014.799

have a physical other than my you know

2017.399

my devices I don't have other physical

2019.039

copies so I may be spending a couple of

2021.639

weekends in the near future pulling

2023.2

stuff down and burning it to a disc or

2025.399

something like that that being said time

2028.48

to wrap this one up we will come back

2031

next time for the ultimate episode of

2033.72

this season the final one we have

2037.039

finished our journey and we're going to

2038.919

talk about that Journey again and maybe

2040.919

do a little bit of a we'll do our you

2042.48

know like a Sprint we're going to get to

2044.559

the end we're going to do a little

2045.48

retrospective and then we'll be into

2047.96

season 23 so as always reach out however

2051.839

you feel like reaching out to us even

2053.399

smoke signals we'll figure it out we'll

2055.119

get that information that'll help us

2057.52

help you as we grow into this next

2060.32

season as always go out there and have

2062.359

yourself a great one and we will talk to

2064.32

you next time

2067.51

[Music]