WEBVTT

00:00:00.000 --> 00:00:03.140
As developers we spend a lot of time

00:00:03.140 --> 00:00:06.120
writing code, guess what, and of course

00:00:06.120 --> 00:00:10.320
we spend that time in code editors on

00:00:10.320 --> 00:00:12.820
our machines, on our Macbooks or

00:00:12.820 --> 00:00:16.120
Windows PCs and therefore of course it's

00:00:16.120 --> 00:00:18.320
absolutely important, at least in my

00:00:18.320 --> 00:00:21.200
opinion, that you set up a development

00:00:21.200 --> 00:00:25.000
environment that you like and that

00:00:25.000 --> 00:00:27.620
works well for you and with

00:00:27.620 --> 00:00:30.080
development environment I don't just

00:00:30.080 --> 00:00:32.200
mean the code editor, though it's

00:00:32.200 --> 00:00:34.520
arguably the most important part, but

00:00:34.520 --> 00:00:37.540
instead I mean the overall environment

00:00:37.540 --> 00:00:40.260
including the hardware you're working

00:00:40.260 --> 00:00:42.420
with, so the laptop or the PC you're

00:00:42.420 --> 00:00:44.920
using, the monitor setup you're using,

00:00:45.360 --> 00:00:49.360
these things all matter because I do

00:00:49.360 --> 00:00:51.860
believe, and I'm pretty sure you could

00:00:51.860 --> 00:00:54.180
find some studies on that as well if you

00:00:54.180 --> 00:00:57.460
wanted to, that you're of course more

00:00:57.460 --> 00:00:59.960
productive if you're working in an

00:00:59.960 --> 00:01:02.000
environment that works well for you,

00:01:02.460 --> 00:01:06.900
but, and that's the big but, not that but,

00:01:07.080 --> 00:01:09.900
but the but, which has to be mentioned,

00:01:10.820 --> 00:01:14.620
of course you can also take it to a point

00:01:14.620 --> 00:01:16.180
where it's too much.

00:01:16.400 --> 00:01:20.260
We probably all know those people who

00:01:20.260 --> 00:01:24.040
spend so much time optimizing their

00:01:24.040 --> 00:01:27.960
workplace and their development

00:01:27.960 --> 00:01:30.660
environment, their setup, that there's

00:01:30.660 --> 00:01:33.300
barely any time left for the actual work

00:01:33.300 --> 00:01:36.720
and you probably also shouldn't try to

00:01:36.720 --> 00:01:38.120
reach that point.

00:01:38.380 --> 00:01:41.220
Instead, as always in life, it's the middle

00:01:41.220 --> 00:01:42.540
you want to aim for.

00:01:42.860 --> 00:01:45.660
You don't want to have that super basic

00:01:45.660 --> 00:01:47.940
setup which you don't like where

00:01:47.940 --> 00:01:50.120
everything is slow and takes you ages

00:01:50.120 --> 00:01:52.540
but you also don't want to spend your

00:01:52.540 --> 00:01:55.400
entire day on cable management and

00:01:55.400 --> 00:01:58.580
monitor setup and installing extensions

00:01:58.580 --> 00:02:00.280
into your Visual Studio code.

00:02:00.900 --> 00:02:04.320
That's probably also not what you should

00:02:04.320 --> 00:02:04.740
do.

00:02:05.080 --> 00:02:07.660
Instead, at least for me, what is super

00:02:07.660 --> 00:02:10.380
important is that I have a machine, a

00:02:10.380 --> 00:02:14.300
MacBook in my case, which is so fast

00:02:14.300 --> 00:02:18.400
that it doesn't get in my way, that things

00:02:18.400 --> 00:02:20.680
happen pretty much instantly, that I

00:02:20.680 --> 00:02:23.020
don't experience any lag or any

00:02:23.020 --> 00:02:26.520
slowdowns, but that I simply don't have

00:02:26.520 --> 00:02:28.280
to worry about the hardware.

00:02:28.540 --> 00:02:30.900
That is important to me and I would

00:02:30.960 --> 00:02:33.840
think that this is probably important for

00:02:33.840 --> 00:02:36.940
most people because who likes working

00:02:36.940 --> 00:02:38.780
with slow hardware?

00:02:39.240 --> 00:02:40.880
We probably have all been there.

00:02:41.280 --> 00:02:46.200
I definitely have in internships and back

00:02:46.200 --> 00:02:48.580
then when I was employed, I had to

00:02:48.580 --> 00:02:51.860
work with slow machines and I do know

00:02:51.860 --> 00:02:53.580
that therefore, of course, you might not

00:02:53.580 --> 00:02:56.620
be able to choose your machine, your

00:02:56.620 --> 00:03:00.400
laptop, because you might need to work

00:03:00.400 --> 00:03:02.240
with whatever you get from your

00:03:02.240 --> 00:03:04.380
employer, but if you have a choice and if

00:03:04.380 --> 00:03:07.000
there is at least some way of making it

00:03:07.000 --> 00:03:10.900
happen, investing in good hardware is

00:03:10.900 --> 00:03:13.820
definitely worth it in my opinion and it

00:03:13.820 --> 00:03:17.500
doesn't have to be the latest high-end

00:03:17.500 --> 00:03:21.160
MacBook which is absurdly expensive.

00:03:21.900 --> 00:03:24.520
It just has to be a decent machine that

00:03:24.520 --> 00:03:25.840
gets out of your way.

00:03:26.140 --> 00:03:29.000
Now another important hardware topic

00:03:29.000 --> 00:03:32.740
of course are monitors and we probably

00:03:32.740 --> 00:03:35.440
also all know these setups where people

00:03:35.440 --> 00:03:38.160
have like three or even four monitors

00:03:38.160 --> 00:03:41.080
and hey, if that works for you, awesome,

00:03:41.240 --> 00:03:43.680
perfect, let's do it, but at least for me, I

00:03:43.680 --> 00:03:46.640
found out that it's one external monitor

00:03:46.640 --> 00:03:49.200
and then the monitor of my MacBook

00:03:49.200 --> 00:03:51.420
and for me that is enough.

00:03:51.440 --> 00:03:53.860
If I have more monitors, I'm not using

00:03:53.860 --> 00:03:54.100
them.

00:03:54.780 --> 00:03:57.720
However, the external monitor should be

00:03:57.720 --> 00:03:58.460
big enough.

00:03:58.660 --> 00:04:00.540
I don't want to have a super small

00:04:00.540 --> 00:04:03.160
monitor, but with that I'm fine.

00:04:03.380 --> 00:04:05.940
I can then have like my code editor on

00:04:05.940 --> 00:04:07.980
one monitor, the preview page on the

00:04:07.980 --> 00:04:10.360
other one or have them side by side and

00:04:10.360 --> 00:04:13.140
have some browser open for doing the

00:04:13.140 --> 00:04:14.760
research and for looking up stuff.

00:04:14.900 --> 00:04:17.540
That works absolutely well for me and

00:04:17.540 --> 00:04:20.079
that is therefore the hardware setup I

00:04:20.079 --> 00:04:21.860
work with well.

00:04:22.360 --> 00:04:25.400
Now when it comes to the software, I'm

00:04:25.400 --> 00:04:27.560
not that complicated.

00:04:27.800 --> 00:04:30.180
I know that there are people who spend

00:04:30.180 --> 00:04:33.560
lots of time on installing just the right

00:04:33.560 --> 00:04:36.400
themes for their code editor and the

00:04:36.400 --> 00:04:40.020
operating system that install alternative

00:04:40.020 --> 00:04:42.140
terminals because they don't want to

00:04:42.140 --> 00:04:44.180
use with the default system command

00:04:44.180 --> 00:04:47.140
prompt or terminal and so on and you

00:04:47.140 --> 00:04:49.900
can do all these things if that is what you

00:04:49.900 --> 00:04:51.220
need, definitely do it.

00:04:51.680 --> 00:04:54.320
For me, that all doesn't matter too

00:04:54.320 --> 00:04:54.580
much.

00:04:55.000 --> 00:04:59.320
I use the default macOS terminal for all

00:04:59.320 --> 00:05:02.020
the commands I run because I don't

00:05:02.020 --> 00:05:05.840
tend to do super complex work in the

00:05:05.840 --> 00:05:08.900
terminal, so I don't need any fancy setup

00:05:08.900 --> 00:05:11.260
there and yeah, it's ugly, but I'm fine with

00:05:11.260 --> 00:05:11.520
that.

00:05:12.360 --> 00:05:16.140
When it comes to the code editor, I do

00:05:16.140 --> 00:05:19.520
want to make sure that it looks nice, that

00:05:19.520 --> 00:05:21.840
I like working in it, that I have a nice font,

00:05:22.120 --> 00:05:25.640
that I have a theme which I want to look

00:05:25.640 --> 00:05:29.940
at and where I don't destroy my eyes,

00:05:30.020 --> 00:05:33.640
but I don't change that theme every four

00:05:33.640 --> 00:05:34.860
weeks, for example.

00:05:35.060 --> 00:05:37.060
I know that there are people who really

00:05:37.060 --> 00:05:39.660
like mixing it up there and that's of

00:05:39.660 --> 00:05:40.140
course fine.

00:05:40.160 --> 00:05:42.620
It's no big deal to change the theme, but

00:05:42.620 --> 00:05:44.980
you should definitely try to find a setup

00:05:44.980 --> 00:05:47.340
that works well for you once and then

00:05:47.340 --> 00:05:50.120
not spend too much time on optimizing

00:05:50.120 --> 00:05:53.780
it in the future, I guess, because that

00:05:53.780 --> 00:05:56.160
would really be unnecessary work.

00:05:56.700 --> 00:05:58.520
However, if you of course like switching a

00:05:58.520 --> 00:06:00.560
theme every four weeks or so, that's

00:06:00.560 --> 00:06:01.420
absolutely fine.

00:06:01.660 --> 00:06:04.300
Again, it's a super quick process, so

00:06:04.300 --> 00:06:05.680
nothing wrong with that.

00:06:05.860 --> 00:06:09.580
Of course, the code editor optimization

00:06:09.580 --> 00:06:12.480
or setup doesn't stop there, you can do

00:06:12.480 --> 00:06:13.000
much more.

00:06:13.300 --> 00:06:16.260
You can install extensions, you can learn

00:06:16.260 --> 00:06:19.660
about all the shortcuts it offers so that

00:06:19.660 --> 00:06:23.180
you can get more productive and here is

00:06:23.180 --> 00:06:26.020
the one thing, probably the most

00:06:26.020 --> 00:06:29.360
important thing I'd argue you should do.

00:06:29.860 --> 00:06:34.360
You should take your time and learn the

00:06:34.360 --> 00:06:37.400
shortcuts offered by your code editor.

00:06:37.720 --> 00:06:39.740
Not all of them of course, there's an

00:06:39.740 --> 00:06:42.220
endless amount of shortcuts, but the

00:06:42.220 --> 00:06:45.160
important ones and also some shortcuts

00:06:45.160 --> 00:06:47.460
you probably didn't know before, like for

00:06:47.460 --> 00:06:50.320
example a shortcut for selecting

00:06:50.320 --> 00:06:53.020
multiple occurrences of the same word.

00:06:53.360 --> 00:06:55.640
You should learn about multi-cursor

00:06:55.640 --> 00:06:57.580
features that might be offered by your

00:06:57.580 --> 00:07:00.680
code editor because all these things can

00:07:00.680 --> 00:07:02.040
make you much more productive.

00:07:02.420 --> 00:07:05.960
And there are people who basically say

00:07:05.960 --> 00:07:09.160
that a good developer never uses a

00:07:09.160 --> 00:07:11.340
mouse and I don't agree with those

00:07:11.340 --> 00:07:11.640
people.

00:07:11.900 --> 00:07:15.500
I do use the mouse and I do call myself a

00:07:15.500 --> 00:07:18.920
good developer, but what is true is that

00:07:18.920 --> 00:07:22.500
you're typically quicker with shortcuts

00:07:22.500 --> 00:07:25.200
and with the keyboard if you know those

00:07:25.200 --> 00:07:26.760
shortcuts, if you know essential

00:07:26.760 --> 00:07:29.100
shortcuts and that's why you should

00:07:29.100 --> 00:07:30.580
spend some time learning them

00:07:30.880 --> 00:07:32.820
because it will make you more

00:07:32.820 --> 00:07:35.620
productive and at least for me, it also

00:07:35.620 --> 00:07:38.080
makes writing code more fun because

00:07:38.080 --> 00:07:40.380
scrolling around with a mouse and

00:07:40.380 --> 00:07:44.020
manually selecting stuff, that's not a lot

00:07:44.020 --> 00:07:46.820
of fun, that is not the part about

00:07:46.820 --> 00:07:48.380
development which I enjoy.

00:07:48.560 --> 00:07:51.640
Instead I enjoy solving problems and the

00:07:51.640 --> 00:07:54.600
faster I can do that, the better it is.

00:07:54.760 --> 00:07:57.460
So that is the one thing you should

00:07:57.460 --> 00:07:59.640
definitely spend some time on and

00:07:59.640 --> 00:08:02.680
where you should also be prepared to

00:08:02.680 --> 00:08:05.300
continue learning because at least for

00:08:05.300 --> 00:08:09.920
me, I still learn about some new trick or

00:08:09.920 --> 00:08:12.260
some new shortcut from time to time

00:08:12.260 --> 00:08:16.760
and of course code editors also often are

00:08:16.760 --> 00:08:19.160
still under active development like Visual

00:08:19.160 --> 00:08:21.780
Studio Code, so new features are added

00:08:21.780 --> 00:08:23.640
all the time and therefore sometimes

00:08:23.640 --> 00:08:26.320
there is a feature which is helpful which I

00:08:26.320 --> 00:08:29.220
then pick up and continue to use in the

00:08:29.220 --> 00:08:31.280
future because it might make me more

00:08:31.280 --> 00:08:34.520
productive and therefore as you can tell

00:08:34.520 --> 00:08:38.059
by how much time I spend on this topic,

00:08:38.659 --> 00:08:41.159
this really is one of the most important

00:08:41.159 --> 00:08:43.280
parts of the development environment

00:08:43.280 --> 00:08:45.280
setup in my opinion even though it's

00:08:45.280 --> 00:08:47.520
technically not part of the setup, but it's

00:08:47.520 --> 00:08:51.180
still part of the setup process I would say

00:08:51.180 --> 00:08:53.400
because you need to know how to work

00:08:53.400 --> 00:08:55.920
with the tools you installed, you need to

00:08:55.920 --> 00:08:58.240
know how to work with them efficiently

00:08:58.240 --> 00:09:01.180
and therefore besides having a fast

00:09:01.180 --> 00:09:03.300
machine and a sufficient amount of

00:09:03.300 --> 00:09:05.500
monitors and a theme that looks good,

00:09:05.860 --> 00:09:08.060
you should make sure that you know

00:09:08.060 --> 00:09:10.660
how to work with the tools you installed

00:09:10.660 --> 00:09:13.860
because if they just look good, that's

00:09:13.860 --> 00:09:16.100
nice but arguably not the most

00:09:16.100 --> 00:09:16.820
important part.

00:09:17.320 --> 00:09:20.760
Now I will say that of course that's not

00:09:20.760 --> 00:09:24.220
necessarily all you should consider when

00:09:24.220 --> 00:09:25.780
setting up your development

00:09:25.780 --> 00:09:28.480
environment, for example when using

00:09:28.480 --> 00:09:31.580
Visual Studio Code or actually for most

00:09:31.580 --> 00:09:34.680
code editors I guess you can install

00:09:34.680 --> 00:09:37.020
extensions which also might make you

00:09:37.020 --> 00:09:39.260
more productive because they might

00:09:39.260 --> 00:09:42.160
offer features which were not built into

00:09:42.160 --> 00:09:44.760
the code editor which do allow you to

00:09:44.760 --> 00:09:48.380
save some time or which add something

00:09:48.380 --> 00:09:50.060
that makes the development process

00:09:50.060 --> 00:09:52.740
more fun because that is also important

00:09:52.740 --> 00:09:55.900
and that's also where we come back to

00:09:55.900 --> 00:09:58.220
the looks of the tools for example.

00:09:58.520 --> 00:10:01.160
If you're working in an environment

00:10:01.160 --> 00:10:04.760
that's not fun to work with, you also will

00:10:04.760 --> 00:10:07.720
not be as productive as possible because

00:10:07.720 --> 00:10:10.580
in my opinion you need all these things,

00:10:10.680 --> 00:10:12.960
you need hardware that works well for

00:10:12.960 --> 00:10:16.040
you, you need software that works well

00:10:16.040 --> 00:10:18.120
for you and where you know how to use

00:10:18.120 --> 00:10:20.660
it and how to use it efficiently and you

00:10:20.660 --> 00:10:22.760
need an overall environment which

00:10:22.760 --> 00:10:24.720
includes the hardware and the software

00:10:24.720 --> 00:10:27.360
and even things like your chair or what's

00:10:27.360 --> 00:10:29.860
on the wall you're also looking at the

00:10:29.860 --> 00:10:32.780
entire day that makes you feel good and

00:10:32.780 --> 00:10:35.900
that makes you like your environment

00:10:35.900 --> 00:10:39.340
because the fun part is also important.

00:10:39.360 --> 00:10:41.420
If you're in a spot where you don't feel

00:10:41.420 --> 00:10:43.960
comfortable you also won't be too

00:10:43.960 --> 00:10:48.080
productive but then at some point you

00:10:48.080 --> 00:10:50.800
also should consider stopping

00:10:50.800 --> 00:10:52.980
optimizing your setup and your

00:10:52.980 --> 00:10:54.580
environment and you should just make

00:10:54.580 --> 00:10:56.580
tweaks here and there from time to time

00:10:56.580 --> 00:11:00.220
and instead use it and work in it because

00:11:00.220 --> 00:11:02.840
if you spend your entire day optimizing

00:11:02.840 --> 00:11:06.000
it as some people seem to do you might

00:11:06.000 --> 00:11:09.460
feel productive but you aren't productive

00:11:09.460 --> 00:11:10.620
I would argue.