📺 Develpreneur YouTube Episode

Video + transcript

Decluttering Your Code and Digital Life

2024-07-25 •Youtube

Detailed Notes

Welcome back to our ongoing series exploring the developer journey! Today, we're diving into a topic that affects every coder's life: digital clutter. As developers, we often start our careers bright-eyed and eager, only to find ourselves buried under mountains of code, tabs, and digital debris years later. Clutter can significantly impede our productivity and creativity, whether in our codebases or desktops. This episode will explore practical strategies for decluttering your digital life, from cleaning messy code to organizing your workspace. We'll share real-world examples of clutter nightmares and provide actionable tips to help you streamline your development process.

Whether you're a seasoned developer drowning in legacy code or a newcomer looking to establish good habits early, this episode is for you. Let's dive in and learn how to cut through the digital noise, allowing us to focus on what truly matters - writing great code and building amazing software.

Read More... https://develpreneur.com/decluttering-your-code-and-digital-life

As developers, our work lives are intrinsically tied to the digital realm. By taking control of our digital environments and cultivating habits that promote organization and cleanliness, we become more efficient coders and create a more enjoyable and less stressful work experience. So, take a moment to assess your digital clutter – your future self will thank you.

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

* Balance Your Time in a Busy World: Tools and Techniques (https://develpreneur.com/balance-time-busy-world/)

* Boost Your Developer Efficiency: Automation Tips for Developers (https://develpreneur.com/boost-your-developer-efficiency-automation-tips-for-developers/)

* Code Refactoring: Maintaining Clean, Efficient Code (https://develpreneur.com/code-refactoring-maintaining-clean-efficient-code/)

* Cleaning Your Task List (https://develpreneur.com/cleaning-your-task-list/)

Transcript Text
[Music]
hello and we've hit record actually we
hit record then we pause and forget it
we're here we're here you're here let's
get that next episode going uh one
things we were we discussed last time as
the potential was one that was a good
one and now I got to go figure out where
that went
uh you had it somewhere around here oh
there it
is this is a nice thing use little bonus
thing use like slack or something like
that where you've got an easy way to
keep track of conversations because it
does make life so much better cutting
the Clutter that's it cutting the
Clutter this is a good one
because it's actually I just had a saw a
project come across that people were
looking for some stuff and I'm like oh
wow that is a fun little project that
you guys have put together and it's it's
a clutter related thing so I think let's
go ahead and dive into this one and
we're going to talk about clutter sound
good all right
well hello and welcome back we are
continuing our season where we're
talking about the developer Journey we
are here at develop anur also building
better developers which hopefully is
going to happen to you as you go through
your developer journey is that you're
going to start you know young and and
widey and all that kind of stuff and
you're GNA get old but you're going to
know a lot of crap because that's the
only I guess that's the benefit of being
old is somebody other than just now you
have all kinds of new pains every day
when you get up I am your pain for the
next little bit here one of the two my
name is Rob Broadhead I am a founder of
developing North also a founder of RB
Consulting where we do software
Solutions we look at simplification
Automation and integration to find ways
to take your technology sprawl simplify
it and give you a solution that works
which funny enough is going to be very
similar to the topic we're going to hit
before I introduce Mike I do want to
mention because sometimes I mix it up
today we're going to focus on cutting
the Clutter we're going to talk about as
a developer we're going to talk about
like the clutter not like necessarily
around your desk or that may be
something that comes up but really more
like the developer clutter that you have
to deal with but before we get into that
we'll tease it a little bit and we'll
send it out to Mike to introduce himself
hey everyone my name is Mike MOS I'm one
of the co-founders a developer ner I'm
also the founder of Invision QA so if
you're small to midsize business or a
clinician looking for software custom
software or just need help figuring out
what you currently have we do software
assessments and we also PR ourselves on
quality software so we write a lot of
software built on integration test unit
testing and system
testing clutter clutter clutter clutter
clutter boy our lives would be so much
easier if we didn't have clutter and
this is particularly code oh my gosh and
this is where this like where it's a
perfect like you know dovetail into a
recent project I saw it was described as
and we've talked about these sort of
like nightmarish type things is that it
was originally built and I guess I can
give some of the specifics of it it
won't matter to it it was originally
built in like python one or version one
or two which for those of you that
aren't python people that has not really
been like that that's a long long time
ago like 10 plus years ago um but then
it's somewhere along the way got
upgraded to Python 3 they also somewhere
along the way upgraded their user
interface and a couple years ago is when
they did this and they did it I don't
remember what they said but it's
basically like you know pick your your
CSS Library if they did they did it all
in this new CSS library and they don't
like that so they're going to throw that
out but all the code's still there and
it hasn't been completely ported over
along the way they also had two or three
other like halfed runs at doing some
features that the code is still there
but it's not complete and now it sits in
Version Control but even that it sounds
like there's like a couple of different
branches and they're not really sure
which Branch they
on that would be an example of clutter
and this is where I want to talk code in
particular because this is something
that I think is a it really is like a
developer habit or
standard and it is about keeping your
clo your code tight and clean in
particular when you're in development
mode and you're you're writing stuff and
then you realize maybe that you don't
need it or that you know like you've got
a big section a code and you realize I'm
going to simplify that I'm going to
refactor it into something
smaller I know a lot of people I know
and several developers that never delete
everything anything comment comment
comment comment
comment that is a total nightmare to go
through you have no idea unless you've
actually maintained your type of code
and had to pick it up and go search for
something like for example is because
most searches are going to just be text
based search
and so you're going to go search through
code for this stuff and you're going to
find this method like 18 different times
and it's all commented out and you're
going to go what the what is it where's
the one you're you're having a dig
through it Version Control will allow
you to go back to that you don't have to
comment it out to save it if you feel
that strongly about it pull it out shove
it into a little text file that is like
my critical Snippets or something like
that and then you're off and running I
do this with datab work I do it all the
time I have these long SQL files that
all they are is all these different like
queries and weird stuff that I've done
for that client that database so I can
go back to it and sometimes I have notes
around it so I can go track track it I
don't need to like shove it into some
big skip script and have it all
commented
out Delete the code don't sit there and
then have these big com particularly
functions oh it drives me nuts you this
big function it's commented out
particularly if you use multi-line
comments where you can have like a you
know a slash asterisk and then there's
nothing and then there's a slash
asterisk somewhere at the end and you
got to go find that now granted if you
use an IDE usually you can find that
stuff but still it's a pain and it gives
you like files grow to these huge things
just don't be afraid to delete it if
you're using Version Control properly
then you're going to be okay that stuff
will disappear likewise
extra files I don't know how many times
I've like I've gone in and I've taken a
you know like maybe there's an HTML file
and I'm going to play around with it so
I'll make it you know test copy or I'll
I'll do something it be like I'll rename
the file and I'll have it there if you
leave those things sitting around it
drives people nuts it is ridiculously
that's not how you Version Control do
not Version Control by doing like index
one index two index 3 index four because
nobody knows what the top number is I
have I worked in a project that that was
what this guy did and sometimes he had
version two and sometimes it's version
three and sometime he would just do V2
V3 V4 V5 you never knew what the top
number was and they would be mixed so
the V2 file would call a V5 which would
call a V3 which would call a
V4
and it was all just too painful so there
is some clutter that you can definitely
make some changes on is clean up the
crap that you're not using don't be
afraid to use like if you use git don't
be AF afraid to use G ignore and don't
store all that crap out in the
repository if it's not needed or bonus
material if it's private information
don't put it out in your GitHub
repository keep that stuff in the get
ignore so you shouldn't have like your
you know your local passwords and stuff
like that yeah you can be like me and be
lazy occasionally say okay here's a
development database and I'll give you
this information but generally speaking
that should not be there shove that
stuff out into a settings file or
something that you deal with locally and
then you don't have to worry about like
for example a security breach because
somebody breaks into your code out on
GitHub I'm going to step off of my Soap
Box because I was like I I just got a
little bit into a tear there and I'm GNA
let Michael like take a take us down a
notch and a little feedback on that and
then what's a like what's a clutter that
that gets your head all you know about
to explode because apparently that's the
direction I'm
taken oh so much to unpack it's really
funny that you mentioned that so the
first thing that comes to my mind are
possible additional solutions to that so
you you mentioned you know make sure you
commit your code into GitHub there's
things of code reviews uh other things
look at using like sonar Q sonar lint uh
any type of code static review tool
they'll highlight things like that
they'll say like hey you have all code
out there that might not be used or dead
code remove it you have Source
control make a comment when you commit
your code that hey I'm removing this for
now it's still in history you also don't
need to keep your branches kicking
around so I get I guess I have two kind
of soap boxy things myself so the big
clutter the first clutter that comes to
mind with get or with any Source control
is a lot of
managers like to keep old branches out
there because they want to keep the
conversation history of the changes that
went on within the source code I don't
know about you but I can't remember what
I did three months ago and typically
code moves so fast that code from a
month ago that stuff doesn't matter
anymore you're beyond you're past that
get rid of that stuff make sure when you
do commit your code you commit with
solid comments in your commit and when
you merge that code in that goes with it
you have a history you can view the
source code history there's all your
notes so don't keep your Source you know
don't keep all those brances around
forever it also takes up space and your
devops people will be very thankful if
you manage that and maintain that
well so kind of following on that
soapbox of comments and like dead code
being around in you know making our
lives hell the additional piece so the
flip side of that is copying and pasting
code all over the
place I have worked on so many projects
where this one method is in six places
doing the exact same thing in six places
ready utility file call the utility file
once uh a project I'm currently working
on with spreadsheets we have certain uh
reports that we do and and the logic
right now is every report has a
different set of sheets but in reality
we actually have a template sheet for
each sheet that's being reused by these
different reports so what we really
should be doing is writing a template
sheet for like a summary and then
extending it for each report and reusing
it that way I ran across this because
trying to write the unit test and
integration test I found I had to to
write six different tests on six
different classes that did the exact
same thing so when you're trying to find
the logic for something and something's
not working oh one method had the
calculation backwards but everywhere
else it was right so now you're going
through all these places well this is
right this is it makes life hell to try
and track down a problem if it's all
over the
place the other problem with copying and
pasting is you might be copying bad code
into another project or into another
class so be very careful with the whole
copy paste thing if you need to make a
copy step back and think to yourself is
this a utility is this a parent class is
this you know a standalone object or
even it's own project that or you can
move to a module and call a module for
multiple
projects look at streamlining it that
way and the last thing before I throw it
back to you Rob is as you're going
through this not only avoid the copy
paste but avoid the long methods or the
long functions Write Clean code if you
start walking through and you find a
method does four different tasks write
that out into four methods or four
functions each function is a different
task and then you
call the uh the methods that you need
that way you never know because that
function that one task could be reused
for something else so therefore again
you're not duplicating code all over the
place but if you don't separate those
into separate methods you don't know
because you're hiding that logic within
this big nasty
method what are your thoughts on that
Rob I think with those I'm going to go
ahead and just I'm going to let that sit
because it is those are all like very
good those are excellent points um I do
want to switch a little bit out of the
the the code Realm when we talk about
clutter and two things that I think are
are very common now is tab clutter is
people have browsers open and you've got
400 tabs and also it's we'll call it it
used to be desktop clutter you could sit
down to somebody's desktop and they
would have 400 icons sitting up on that
that desktop but now we also get it with
our phone or our tablet where you'll
have all these applications you'll be
scrolling through like page after page
after page of icons and and apps and
being like hey I need to go do this I
need to go do that I where is it at how
am I going to go get there there are all
kinds of methods to reduce that clutter
whether it's as simple as put it all in
put these things into folders so you
have like maybe on your phone maybe you
have your work folder your personal
folder your your workout folder your
hobby folder that kind of stuff put
those apps in there so at least you're
not having the scroll scroll scroll
scroll scroll same thing on your desktop
I know that
it's it's easy to have a desktop that's
full of shortcuts and you know that like
over here in the top left is always
where that one thing is or down there in
the bottom right is where that one is
but as soon as something happens with
your desktop icons the like the best
example is when like the sort changes so
they were all sorted by maybe not at all
and now somebody these somewhere along
the way you sorted all those things by
name and now blowing your head up
because you don't know where that icon
is anymore so you're having to search
through all this stuff use folders use a
better organization because it really is
it's just like your actual desk just
throwing a bunch of crap out there and
then going to find it yes there may be
method to your Madness but if you have
folders or something like that some sort
of grouping it will make the method your
Madness a lot easier for you to get
through don't beat your head over where
did I put that where did I put that
where did I put that once you found that
that's an
issue put it set aside like you know
earmark some time to go clean that stuff
up and again it is it's really it's
reducing clutter reduce the Clutter of
your icons reduce the Clutter of all
those tabs that you have open every time
you open a browser uh one of the things
that we've lost because now machines
pretty much can stay up almost all the
time was the idea it used to be in the
day that you would get done with your
workday and you would shut your machine
off and the next day you would turn your
machine on and so you had to worry about
boot times and you may still do that
somewhere but there are a lot of places
where it don't where we don't and that
allows us bad habits of having 400
different applications up and all these
other things that yeah it's worth it
like again if you have a defined end of
the day which you should shut stuff down
close stuff up things like that to just
get yourself in the habit of
decluttering your Digital Life as well
as your physical life uh last thoughts
from you
yeah in addition to that declutter your
desk and your desktop if you are in like
healthcare you have to worry about Hippa
and things of that nature the clean desk
policy is not just a habit it's becoming
mainstream so if you are in an office
keeping stuff off your desk is pretty
much key to ensuring that privac privacy
private information isn't lifted or
stolen or inadvertently seen and now
you've got a legal issue
additionally uh the last thing I would
like to touch on is within the idea of
organization and kind of
clutter uh one of the additional things
we come come across is your idea of boot
times right having to reboot and shut
down your computer the other thing to
think about as you are testing your
software or you are building
software think about writing tests or
testing stuff make sure you clean up
after yourself so if you're going to
insert a whole bunch of test data into a
table make sure you also have delete
statements to delete that test data back
out when you're done so that you don't
basically you leave your test
environment in the same state it was
before and after you test it this also
allows you to test different things you
can do load testing uh systems testing
and some other features there but just
kind of be cautious and think about that
whole continuous integration continuous
deployment but also think about cleaning
up after yourself within your scripts
and your
tests yeah data Colter is probably one
of the most uh painful things to go
through and it definitely can it can
really slow down uh development
environments and things of that nature I
don't know how often I've I've worked
with situations it's like we need a way
to like do a a delete or if you can't
delete data then an archive or something
because you've you you get uh like daily
dashboards and stuff that suddenly have
or not suddenly but grow and now they've
got thousands and thousands of records
and the whole thing is slow because
you're you're hitting all of that data
all the time and you need ways to like
you know ignore some of it whether it's
delete it clean it up filter it things
like that that being said you don't need
to delete clean up filter anything else
the stuff we said you should just so
ahead go ahead and just like sit back
and just consume it and you know like
how does that taste it should taste
pretty good because we're suggesting
that you declutter your life and and
find some simplification trust me a
little bit of work on this if you're at
all like me it actually becomes sort of
addictive because you realize that you
put a little bit of time in and now you
saved a whole lot of time and the next
thing you know you're like well what if
I put a lot of time in maybe I'm going
to save so much time I'm going to start
getting younger again or something like
that there is Magic in declutter just
getting rid of the Clutter and and
realizing how much easier and simpler
your life your tasks become at that
point for example that would free up
time so that you can send us comments
and feedback and things like that and
you can do that at info@ develop or.com
we have a for out there on develop
or.com so you can send us information
there you can leave us comments whether
it's at wherever your podcast wherever
you gather podcasts and listen to them
out on YouTube on our YouTube channel uh
you can check out school. developer.com
we also have comment for there you can
sign in and give us feedback as well as
there go out to our site blog articles
we have comments turned on all that good
stuff so you can give us feedback and
let us know what you like what you don't
like and recommendations for future
topics that you might have that being
said we're ready to bring this one to a
close we are not done with the season
we're like chugging along here like you
roughly I don't know a 30ish maybe
through with it so we got plenty to come
we're going to continue that developer
Journey uh as you guys do as well as
well as you're continuing your journey
we're going to talk about these things
that we've hit hit on and even some
things that we see coming up however it
is you have the rest of your day going
coming up so why don't you go out there
and have yourself a great day a great
week and we will talk to you next
time bonus clutter stuff for these the
people that are still sitting around and
haven't left
yet so I have two one especially if you
have mobile devices lots of apps you
don't need to
buy a device that has a terabyte of
storage on you don't need to pay for
cloud information for terabytes of
storage get in the habit of cleaning up
your stuff if you have thousands of
photos do you need a thousand photos no
chances are you're only going to look at
them once in a while pick your favorite
photos dump them off to a computer print
them out move them you know move move
them to something more
permanent the flip side of that is look
around your house is there anything you
haven't touched in a year or two get rid
of it we don't need to pay for storage
we don't need storage facilities you
know the whole idea of unpacking and
cleaning up the Clutter doesn't just
apply the code you can do that with
everything in your life and by doing
that you get rid of something that
you've been staring at for six months or
a year and it's like you know I really
need to get rid of that or you know I
really don't have room for all this new
stuff I bought well get rid of some of
the old stuff so the new stuff can find
a better
place your thoughts I think that the
first part is you you really don't need
all that space now you can be like me
you can like be a little pack ratty and
you can save but you can save old emails
and so old images and all that kind of
stuff you can save that stuff and just
shove it off somewhere it you will be
happier for it because sooner or later
your devices are going to get really
really expensive because you're just
storing crap there that you can find
easier ways to do it whether it is
offline in a cloud storage somewhere
where you just you know you've got that
away or at least not offline but you
know that it's on cloud storage
somewhere where you have access to it
but at least it's not on your device
where it is much more you know expensive
to keep buying that storage over and
over again or whether you want to store
it somewhere on have a you know a big
server at home that you can take a look
at it you know it's that kind of stuff
just pull that stuff off because it does
slow down your devices also like if you
don't have a lot of space on them then
it's going to slow them down they're
going to start griping and have issues
so get that crap off periodically pull
it off you utilize things like you know
even the Apple like they've got the uh
on the Apple devices they have like the
store the app in the cloud if you don't
use it for a while they'll basically
pull it off of your device and you can
always bring it back down again when you
use it but if you haven't used it in a
while just delete that thing if you if
you don't need it don't use it
General clutter
is one of the things that I found is
notes is where you're wherever you're
taking note take taking notes make sure
you like pick one there's so many places
do it but like find a way to whether you
you have like a little Journal book that
you keep all your notes in or whether
you use Evernote or whether you use one
of these list device you know list apps
whatever it
is try to stick to one because the
Clutter of having too many places to
enter information can really become a
pain when you're like where did I put
that and I've done that a few times
because I've been forced by clients and
access and all that kind of stuff to
have four or five different places and
it'll be like where did I put that IP
address for that server ah crap it's
nope not there oh nope nope so the
better the more you can simplify down
your places that you store these things
the easier it is to know that well I
don't know how even if it's difficult to
find it in that place at least you know
you're looking in the right place so
there's a couple for you you are looking
in the right place if you want to become
a better developer so you're here you're
out on the developer n Channel as we've
mentioned before you can check out our
website I don't know why I'm pointing
over here like the websites over here
like on the internet go out to the
YouTube channel take a left go five
blocks and a right from there and boom
you're at the developer Nur site
something like that check us out on the
developer Nur site we've got a lot of
stuff there lots and lots and lots of
material there as well uh if you're
especially if you're trying to get away
from the dig the video side of YouTube
stuff lots of videos here but also we've
got all kinds of like downloads and
written content and things like that as
well as the audio content of over 700
different episodes of the podcast we've
been just like cranking through this
there's a lot out there if you go out
because some of these places don't even
store some of the older stuff if you
need an older one let us know if you
want to go find out like what season one
looked like shoot us an email and we
will send you some audio files or a link
to them that being said it is time for
us to wrap this one up because we got to
go out to our day and we got to work on
becoming better developers ourselves
besides just sharing these conversations
even though they are very productive for
us as well but we'll let you get out
there thank you so much for your time
and spending some time with us and uh
we'll be here right around the corner
we'll be yet another episode and we'll
dive into all the ways that you can
become a better developer have a good
one
[Music]
Transcript Segments
1.35

[Music]

27.48

hello and we've hit record actually we

30.32

hit record then we pause and forget it

32.96

we're here we're here you're here let's

35.559

get that next episode going uh one

37.84

things we were we discussed last time as

39.719

the potential was one that was a good

42.879

one and now I got to go figure out where

44.64

that went

48.6

uh you had it somewhere around here oh

51.64

there it

52.6

is this is a nice thing use little bonus

55.64

thing use like slack or something like

58.68

that where you've got an easy way to

60.199

keep track of conversations because it

61.84

does make life so much better cutting

64.439

the Clutter that's it cutting the

66.96

Clutter this is a good one

69.24

because it's actually I just had a saw a

72.88

project come across that people were

74.439

looking for some stuff and I'm like oh

76.24

wow that is a fun little project that

79.2

you guys have put together and it's it's

81.04

a clutter related thing so I think let's

84.2

go ahead and dive into this one and

85.64

we're going to talk about clutter sound

88.52

good all right

90.479

well hello and welcome back we are

92.36

continuing our season where we're

93.84

talking about the developer Journey we

95.88

are here at develop anur also building

97.96

better developers which hopefully is

100.119

going to happen to you as you go through

101.399

your developer journey is that you're

103.04

going to start you know young and and

106.56

widey and all that kind of stuff and

108

you're GNA get old but you're going to

109.119

know a lot of crap because that's the

111.6

only I guess that's the benefit of being

113.2

old is somebody other than just now you

115.439

have all kinds of new pains every day

117.079

when you get up I am your pain for the

119.28

next little bit here one of the two my

121.36

name is Rob Broadhead I am a founder of

123.039

developing North also a founder of RB

125.96

Consulting where we do software

128.16

Solutions we look at simplification

129.92

Automation and integration to find ways

132.8

to take your technology sprawl simplify

135.08

it and give you a solution that works

137.08

which funny enough is going to be very

139.16

similar to the topic we're going to hit

141.04

before I introduce Mike I do want to

142.44

mention because sometimes I mix it up

144.8

today we're going to focus on cutting

146.239

the Clutter we're going to talk about as

148.04

a developer we're going to talk about

149.519

like the clutter not like necessarily

151.92

around your desk or that may be

153.56

something that comes up but really more

155.04

like the developer clutter that you have

157.28

to deal with but before we get into that

159.4

we'll tease it a little bit and we'll

160.56

send it out to Mike to introduce himself

163.4

hey everyone my name is Mike MOS I'm one

165.239

of the co-founders a developer ner I'm

167.239

also the founder of Invision QA so if

169.319

you're small to midsize business or a

171.12

clinician looking for software custom

173.48

software or just need help figuring out

175.84

what you currently have we do software

177.72

assessments and we also PR ourselves on

180.519

quality software so we write a lot of

182.36

software built on integration test unit

184.879

testing and system

187.92

testing clutter clutter clutter clutter

190.68

clutter boy our lives would be so much

194.36

easier if we didn't have clutter and

195.879

this is particularly code oh my gosh and

199.799

this is where this like where it's a

201.48

perfect like you know dovetail into a

203.84

recent project I saw it was described as

207.2

and we've talked about these sort of

208.64

like nightmarish type things is that it

211.2

was originally built and I guess I can

214.4

give some of the specifics of it it

215.64

won't matter to it it was originally

217.08

built in like python one or version one

219.72

or two which for those of you that

221.04

aren't python people that has not really

223.36

been like that that's a long long time

225.599

ago like 10 plus years ago um but then

229.64

it's somewhere along the way got

230.799

upgraded to Python 3 they also somewhere

233.48

along the way upgraded their user

235.159

interface and a couple years ago is when

236.92

they did this and they did it I don't

238.959

remember what they said but it's

240.12

basically like you know pick your your

242.079

CSS Library if they did they did it all

244.04

in this new CSS library and they don't

246.799

like that so they're going to throw that

248

out but all the code's still there and

249.799

it hasn't been completely ported over

251.84

along the way they also had two or three

255.239

other like halfed runs at doing some

258.16

features that the code is still there

261.4

but it's not complete and now it sits in

264.68

Version Control but even that it sounds

266.72

like there's like a couple of different

268.08

branches and they're not really sure

269.36

which Branch they

271.36

on that would be an example of clutter

274.639

and this is where I want to talk code in

277.88

particular because this is something

279.16

that I think is a it really is like a

282.039

developer habit or

284.36

standard and it is about keeping your

287.72

clo your code tight and clean in

290.919

particular when you're in development

292.8

mode and you're you're writing stuff and

296.16

then you realize maybe that you don't

297.479

need it or that you know like you've got

299.039

a big section a code and you realize I'm

300.68

going to simplify that I'm going to

301.919

refactor it into something

304.08

smaller I know a lot of people I know

307.759

and several developers that never delete

309.6

everything anything comment comment

312

comment comment

313.28

comment that is a total nightmare to go

317.639

through you have no idea unless you've

320.84

actually maintained your type of code

323.16

and had to pick it up and go search for

324.96

something like for example is because

327.56

most searches are going to just be text

329.199

based search

330.28

and so you're going to go search through

331.36

code for this stuff and you're going to

332.36

find this method like 18 different times

334.4

and it's all commented out and you're

336.36

going to go what the what is it where's

338.6

the one you're you're having a dig

340.08

through it Version Control will allow

342.8

you to go back to that you don't have to

345.759

comment it out to save it if you feel

348.6

that strongly about it pull it out shove

351.759

it into a little text file that is like

353.68

my critical Snippets or something like

355.84

that and then you're off and running I

358.84

do this with datab work I do it all the

360.68

time I have these long SQL files that

363.52

all they are is all these different like

365

queries and weird stuff that I've done

366.96

for that client that database so I can

369.36

go back to it and sometimes I have notes

371.44

around it so I can go track track it I

373.919

don't need to like shove it into some

375.84

big skip script and have it all

377.36

commented

378.72

out Delete the code don't sit there and

382.52

then have these big com particularly

384.319

functions oh it drives me nuts you this

386.72

big function it's commented out

389.08

particularly if you use multi-line

390.72

comments where you can have like a you

392.96

know a slash asterisk and then there's

395.12

nothing and then there's a slash

396.4

asterisk somewhere at the end and you

398.08

got to go find that now granted if you

400.199

use an IDE usually you can find that

402.199

stuff but still it's a pain and it gives

405.319

you like files grow to these huge things

409.639

just don't be afraid to delete it if

412.759

you're using Version Control properly

415.16

then you're going to be okay that stuff

416.84

will disappear likewise

420.16

extra files I don't know how many times

422.639

I've like I've gone in and I've taken a

424.479

you know like maybe there's an HTML file

425.96

and I'm going to play around with it so

427.639

I'll make it you know test copy or I'll

430.16

I'll do something it be like I'll rename

431.8

the file and I'll have it there if you

434.56

leave those things sitting around it

436.319

drives people nuts it is ridiculously

438.84

that's not how you Version Control do

440.56

not Version Control by doing like index

442.879

one index two index 3 index four because

446.319

nobody knows what the top number is I

448.879

have I worked in a project that that was

451.199

what this guy did and sometimes he had

455.039

version two and sometimes it's version

457.12

three and sometime he would just do V2

458.84

V3 V4 V5 you never knew what the top

461.599

number was and they would be mixed so

463.879

the V2 file would call a V5 which would

465.919

call a V3 which would call a

467.919

V4

469.52

and it was all just too painful so there

474.759

is some clutter that you can definitely

477.599

make some changes on is clean up the

479.72

crap that you're not using don't be

482.159

afraid to use like if you use git don't

484

be AF afraid to use G ignore and don't

486.56

store all that crap out in the

488.08

repository if it's not needed or bonus

491.08

material if it's private information

493.8

don't put it out in your GitHub

495.96

repository keep that stuff in the get

498.639

ignore so you shouldn't have like your

501.24

you know your local passwords and stuff

503.28

like that yeah you can be like me and be

504.879

lazy occasionally say okay here's a

506.4

development database and I'll give you

508.479

this information but generally speaking

510.8

that should not be there shove that

512.959

stuff out into a settings file or

514.519

something that you deal with locally and

517.039

then you don't have to worry about like

519.32

for example a security breach because

521.399

somebody breaks into your code out on

523.519

GitHub I'm going to step off of my Soap

525.839

Box because I was like I I just got a

528.04

little bit into a tear there and I'm GNA

530.12

let Michael like take a take us down a

532.16

notch and a little feedback on that and

535.48

then what's a like what's a clutter that

537.68

that gets your head all you know about

539.64

to explode because apparently that's the

541.12

direction I'm

543

taken oh so much to unpack it's really

547.44

funny that you mentioned that so the

549.8

first thing that comes to my mind are

551.8

possible additional solutions to that so

554.44

you you mentioned you know make sure you

556.36

commit your code into GitHub there's

558.36

things of code reviews uh other things

561.399

look at using like sonar Q sonar lint uh

564.399

any type of code static review tool

566.76

they'll highlight things like that

567.959

they'll say like hey you have all code

569.72

out there that might not be used or dead

571.6

code remove it you have Source

575.04

control make a comment when you commit

577.36

your code that hey I'm removing this for

579.04

now it's still in history you also don't

582

need to keep your branches kicking

584.839

around so I get I guess I have two kind

587.56

of soap boxy things myself so the big

590.079

clutter the first clutter that comes to

592.04

mind with get or with any Source control

595.12

is a lot of

596.72

managers like to keep old branches out

600.48

there because they want to keep the

601.72

conversation history of the changes that

604.839

went on within the source code I don't

607.2

know about you but I can't remember what

610.04

I did three months ago and typically

611.839

code moves so fast that code from a

614.8

month ago that stuff doesn't matter

617.04

anymore you're beyond you're past that

619.399

get rid of that stuff make sure when you

622.16

do commit your code you commit with

624.12

solid comments in your commit and when

626.44

you merge that code in that goes with it

629.519

you have a history you can view the

631.64

source code history there's all your

633.36

notes so don't keep your Source you know

636.839

don't keep all those brances around

638.92

forever it also takes up space and your

642.6

devops people will be very thankful if

644.6

you manage that and maintain that

647.079

well so kind of following on that

650.76

soapbox of comments and like dead code

653.959

being around in you know making our

656.76

lives hell the additional piece so the

660.56

flip side of that is copying and pasting

663.399

code all over the

665.12

place I have worked on so many projects

668.12

where this one method is in six places

672.519

doing the exact same thing in six places

674.88

ready utility file call the utility file

679.24

once uh a project I'm currently working

682.639

on with spreadsheets we have certain uh

687.48

reports that we do and and the logic

690.88

right now is every report has a

693.72

different set of sheets but in reality

697.36

we actually have a template sheet for

700.72

each sheet that's being reused by these

702.839

different reports so what we really

704.76

should be doing is writing a template

707.68

sheet for like a summary and then

710.519

extending it for each report and reusing

712.76

it that way I ran across this because

715.8

trying to write the unit test and

717.399

integration test I found I had to to

719.36

write six different tests on six

722.32

different classes that did the exact

724.44

same thing so when you're trying to find

726.92

the logic for something and something's

728.839

not working oh one method had the

732.32

calculation backwards but everywhere

734.6

else it was right so now you're going

736.519

through all these places well this is

737.959

right this is it makes life hell to try

740.76

and track down a problem if it's all

743.199

over the

744.199

place the other problem with copying and

746.36

pasting is you might be copying bad code

748.56

into another project or into another

750.56

class so be very careful with the whole

752.959

copy paste thing if you need to make a

756.6

copy step back and think to yourself is

759.32

this a utility is this a parent class is

762.48

this you know a standalone object or

764.68

even it's own project that or you can

766.959

move to a module and call a module for

769.519

multiple

770.72

projects look at streamlining it that

774.199

way and the last thing before I throw it

776.6

back to you Rob is as you're going

779.399

through this not only avoid the copy

782.32

paste but avoid the long methods or the

785.48

long functions Write Clean code if you

789.92

start walking through and you find a

791.56

method does four different tasks write

795

that out into four methods or four

797.8

functions each function is a different

800.32

task and then you

801.76

call the uh the methods that you need

805.24

that way you never know because that

807.12

function that one task could be reused

810

for something else so therefore again

812.8

you're not duplicating code all over the

815.04

place but if you don't separate those

817.12

into separate methods you don't know

819.24

because you're hiding that logic within

820.92

this big nasty

823

method what are your thoughts on that

827.36

Rob I think with those I'm going to go

829.44

ahead and just I'm going to let that sit

831

because it is those are all like very

832.759

good those are excellent points um I do

835.959

want to switch a little bit out of the

837.8

the the code Realm when we talk about

840.399

clutter and two things that I think are

844.56

are very common now is tab clutter is

848.839

people have browsers open and you've got

850.32

400 tabs and also it's we'll call it it

854.24

used to be desktop clutter you could sit

855.92

down to somebody's desktop and they

857.16

would have 400 icons sitting up on that

860.399

that desktop but now we also get it with

862.04

our phone or our tablet where you'll

863.519

have all these applications you'll be

865.519

scrolling through like page after page

867.44

after page of icons and and apps and

870.8

being like hey I need to go do this I

873.12

need to go do that I where is it at how

875.199

am I going to go get there there are all

879.12

kinds of methods to reduce that clutter

881.36

whether it's as simple as put it all in

883.639

put these things into folders so you

885.88

have like maybe on your phone maybe you

887.48

have your work folder your personal

889

folder your your workout folder your

891.399

hobby folder that kind of stuff put

893.44

those apps in there so at least you're

896.12

not having the scroll scroll scroll

897.759

scroll scroll same thing on your desktop

900.16

I know that

901.6

it's it's easy to have a desktop that's

904.92

full of shortcuts and you know that like

908.24

over here in the top left is always

909.72

where that one thing is or down there in

911.24

the bottom right is where that one is

912.72

but as soon as something happens with

914.68

your desktop icons the like the best

918.24

example is when like the sort changes so

920.92

they were all sorted by maybe not at all

923.48

and now somebody these somewhere along

925.519

the way you sorted all those things by

927.759

name and now blowing your head up

930

because you don't know where that icon

931.56

is anymore so you're having to search

932.8

through all this stuff use folders use a

936

better organization because it really is

938.399

it's just like your actual desk just

940.639

throwing a bunch of crap out there and

942.12

then going to find it yes there may be

944.399

method to your Madness but if you have

946.319

folders or something like that some sort

948.319

of grouping it will make the method your

951.04

Madness a lot easier for you to get

953.12

through don't beat your head over where

955.199

did I put that where did I put that

956.639

where did I put that once you found that

959.399

that's an

960.48

issue put it set aside like you know

963.16

earmark some time to go clean that stuff

965.759

up and again it is it's really it's

968

reducing clutter reduce the Clutter of

970

your icons reduce the Clutter of all

972.279

those tabs that you have open every time

973.92

you open a browser uh one of the things

976.079

that we've lost because now machines

978.199

pretty much can stay up almost all the

980.12

time was the idea it used to be in the

982.16

day that you would get done with your

983.56

workday and you would shut your machine

985.92

off and the next day you would turn your

987.8

machine on and so you had to worry about

990.199

boot times and you may still do that

991.92

somewhere but there are a lot of places

993.839

where it don't where we don't and that

995.519

allows us bad habits of having 400

998.399

different applications up and all these

1000.12

other things that yeah it's worth it

1003.68

like again if you have a defined end of

1005.56

the day which you should shut stuff down

1008.519

close stuff up things like that to just

1010.44

get yourself in the habit of

1012.6

decluttering your Digital Life as well

1015.12

as your physical life uh last thoughts

1018.12

from you

1019.56

yeah in addition to that declutter your

1022.839

desk and your desktop if you are in like

1025.64

healthcare you have to worry about Hippa

1027.559

and things of that nature the clean desk

1029.64

policy is not just a habit it's becoming

1033.4

mainstream so if you are in an office

1035.959

keeping stuff off your desk is pretty

1038.319

much key to ensuring that privac privacy

1042.28

private information isn't lifted or

1045.079

stolen or inadvertently seen and now

1047.679

you've got a legal issue

1050.48

additionally uh the last thing I would

1052.52

like to touch on is within the idea of

1056.24

organization and kind of

1058.24

clutter uh one of the additional things

1061.64

we come come across is your idea of boot

1065.84

times right having to reboot and shut

1067.76

down your computer the other thing to

1070.72

think about as you are testing your

1072.88

software or you are building

1077

software think about writing tests or

1080.679

testing stuff make sure you clean up

1083

after yourself so if you're going to

1084.4

insert a whole bunch of test data into a

1086.32

table make sure you also have delete

1088.36

statements to delete that test data back

1090.4

out when you're done so that you don't

1093.48

basically you leave your test

1095.559

environment in the same state it was

1097.72

before and after you test it this also

1100.64

allows you to test different things you

1102.6

can do load testing uh systems testing

1105.36

and some other features there but just

1108.2

kind of be cautious and think about that

1111.08

whole continuous integration continuous

1112.96

deployment but also think about cleaning

1115.08

up after yourself within your scripts

1117.159

and your

1118.28

tests yeah data Colter is probably one

1120.799

of the most uh painful things to go

1123.4

through and it definitely can it can

1125.679

really slow down uh development

1128

environments and things of that nature I

1129.4

don't know how often I've I've worked

1131.32

with situations it's like we need a way

1133.2

to like do a a delete or if you can't

1136.2

delete data then an archive or something

1138.12

because you've you you get uh like daily

1141.24

dashboards and stuff that suddenly have

1143.919

or not suddenly but grow and now they've

1145.559

got thousands and thousands of records

1147.36

and the whole thing is slow because

1149.96

you're you're hitting all of that data

1152.32

all the time and you need ways to like

1154.919

you know ignore some of it whether it's

1156.559

delete it clean it up filter it things

1159

like that that being said you don't need

1162.4

to delete clean up filter anything else

1164.64

the stuff we said you should just so

1166.559

ahead go ahead and just like sit back

1169.039

and just consume it and you know like

1171.12

how does that taste it should taste

1172.52

pretty good because we're suggesting

1174.039

that you declutter your life and and

1176.12

find some simplification trust me a

1178.84

little bit of work on this if you're at

1180.799

all like me it actually becomes sort of

1182.64

addictive because you realize that you

1183.919

put a little bit of time in and now you

1185.32

saved a whole lot of time and the next

1187

thing you know you're like well what if

1188.28

I put a lot of time in maybe I'm going

1189.679

to save so much time I'm going to start

1191.48

getting younger again or something like

1193.039

that there is Magic in declutter just

1196.88

getting rid of the Clutter and and

1199.84

realizing how much easier and simpler

1202.799

your life your tasks become at that

1205.159

point for example that would free up

1207.64

time so that you can send us comments

1209.6

and feedback and things like that and

1211.32

you can do that at info@ develop or.com

1213.6

we have a for out there on develop

1215.12

or.com so you can send us information

1217.36

there you can leave us comments whether

1219.28

it's at wherever your podcast wherever

1221.08

you gather podcasts and listen to them

1223.4

out on YouTube on our YouTube channel uh

1225.64

you can check out school. developer.com

1227.44

we also have comment for there you can

1229.64

sign in and give us feedback as well as

1231.559

there go out to our site blog articles

1234.52

we have comments turned on all that good

1236.36

stuff so you can give us feedback and

1238.36

let us know what you like what you don't

1239.919

like and recommendations for future

1242.32

topics that you might have that being

1244.919

said we're ready to bring this one to a

1246.919

close we are not done with the season

1248.799

we're like chugging along here like you

1250.96

roughly I don't know a 30ish maybe

1253.039

through with it so we got plenty to come

1255.08

we're going to continue that developer

1256.52

Journey uh as you guys do as well as

1258.72

well as you're continuing your journey

1260

we're going to talk about these things

1261.159

that we've hit hit on and even some

1263.76

things that we see coming up however it

1266.48

is you have the rest of your day going

1268.4

coming up so why don't you go out there

1270.2

and have yourself a great day a great

1272.279

week and we will talk to you next

1276.159

time bonus clutter stuff for these the

1280.4

people that are still sitting around and

1281.72

haven't left

1283.72

yet so I have two one especially if you

1288.76

have mobile devices lots of apps you

1291.88

don't need to

1293.48

buy a device that has a terabyte of

1296.96

storage on you don't need to pay for

1299.279

cloud information for terabytes of

1302

storage get in the habit of cleaning up

1305.88

your stuff if you have thousands of

1308.2

photos do you need a thousand photos no

1310.08

chances are you're only going to look at

1311.279

them once in a while pick your favorite

1313.559

photos dump them off to a computer print

1316.36

them out move them you know move move

1318.76

them to something more

1320.96

permanent the flip side of that is look

1324.32

around your house is there anything you

1326.88

haven't touched in a year or two get rid

1329.279

of it we don't need to pay for storage

1331.159

we don't need storage facilities you

1333

know the whole idea of unpacking and

1336.08

cleaning up the Clutter doesn't just

1337.559

apply the code you can do that with

1339.52

everything in your life and by doing

1341.76

that you get rid of something that

1343.159

you've been staring at for six months or

1344.6

a year and it's like you know I really

1346.32

need to get rid of that or you know I

1348.159

really don't have room for all this new

1350.279

stuff I bought well get rid of some of

1351.76

the old stuff so the new stuff can find

1353.679

a better

1355.12

place your thoughts I think that the

1358.52

first part is you you really don't need

1361.48

all that space now you can be like me

1364.2

you can like be a little pack ratty and

1365.799

you can save but you can save old emails

1368.72

and so old images and all that kind of

1370.48

stuff you can save that stuff and just

1371.919

shove it off somewhere it you will be

1374.2

happier for it because sooner or later

1375.84

your devices are going to get really

1378.679

really expensive because you're just

1379.88

storing crap there that you can find

1382.159

easier ways to do it whether it is

1385.279

offline in a cloud storage somewhere

1386.88

where you just you know you've got that

1388.279

away or at least not offline but you

1390.679

know that it's on cloud storage

1392.12

somewhere where you have access to it

1393.52

but at least it's not on your device

1394.919

where it is much more you know expensive

1397.039

to keep buying that storage over and

1398.72

over again or whether you want to store

1400.919

it somewhere on have a you know a big

1403.44

server at home that you can take a look

1405.039

at it you know it's that kind of stuff

1406.44

just pull that stuff off because it does

1408.88

slow down your devices also like if you

1411.32

don't have a lot of space on them then

1412.919

it's going to slow them down they're

1413.799

going to start griping and have issues

1415.44

so get that crap off periodically pull

1418.24

it off you utilize things like you know

1422.12

even the Apple like they've got the uh

1424

on the Apple devices they have like the

1425.279

store the app in the cloud if you don't

1426.84

use it for a while they'll basically

1428.72

pull it off of your device and you can

1430.4

always bring it back down again when you

1431.96

use it but if you haven't used it in a

1433.96

while just delete that thing if you if

1436.24

you don't need it don't use it

1439.44

General clutter

1442.44

is one of the things that I found is

1445.4

notes is where you're wherever you're

1447.24

taking note take taking notes make sure

1449.88

you like pick one there's so many places

1452

do it but like find a way to whether you

1454.64

you have like a little Journal book that

1456.12

you keep all your notes in or whether

1457.559

you use Evernote or whether you use one

1459.32

of these list device you know list apps

1461.96

whatever it

1463.52

is try to stick to one because the

1467.279

Clutter of having too many places to

1470.159

enter information can really become a

1472.84

pain when you're like where did I put

1475.039

that and I've done that a few times

1476.84

because I've been forced by clients and

1479.159

access and all that kind of stuff to

1480.279

have four or five different places and

1481.96

it'll be like where did I put that IP

1483.44

address for that server ah crap it's

1485.64

nope not there oh nope nope so the

1488.88

better the more you can simplify down

1491.279

your places that you store these things

1494.72

the easier it is to know that well I

1496.64

don't know how even if it's difficult to

1498.399

find it in that place at least you know

1500.32

you're looking in the right place so

1503.799

there's a couple for you you are looking

1505.76

in the right place if you want to become

1507.44

a better developer so you're here you're

1509.52

out on the developer n Channel as we've

1512.2

mentioned before you can check out our

1513.6

website I don't know why I'm pointing

1514.799

over here like the websites over here

1516.399

like on the internet go out to the

1518.88

YouTube channel take a left go five

1520.919

blocks and a right from there and boom

1522.48

you're at the developer Nur site

1524.6

something like that check us out on the

1526.679

developer Nur site we've got a lot of

1528

stuff there lots and lots and lots of

1529.919

material there as well uh if you're

1532.279

especially if you're trying to get away

1533.52

from the dig the video side of YouTube

1536.12

stuff lots of videos here but also we've

1538.399

got all kinds of like downloads and

1539.76

written content and things like that as

1541.559

well as the audio content of over 700

1545.12

different episodes of the podcast we've

1548.36

been just like cranking through this

1550.799

there's a lot out there if you go out

1553.279

because some of these places don't even

1554.679

store some of the older stuff if you

1555.96

need an older one let us know if you

1557.919

want to go find out like what season one

1559.679

looked like shoot us an email and we

1561.559

will send you some audio files or a link

1563.76

to them that being said it is time for

1566.12

us to wrap this one up because we got to

1567.96

go out to our day and we got to work on

1569.44

becoming better developers ourselves

1571.24

besides just sharing these conversations

1573.32

even though they are very productive for

1575.32

us as well but we'll let you get out

1577.32

there thank you so much for your time

1579.159

and spending some time with us and uh

1581

we'll be here right around the corner

1582.36

we'll be yet another episode and we'll

1584.039

dive into all the ways that you can

1586.44

become a better developer have a good

1588.84

one

1591.27

[Music]