HomeVideos

How I Setup My Mac For Coding So It Doesn't Ruin My Life

Now Playing

How I Setup My Mac For Coding So It Doesn't Ruin My Life

Transcript

421 segments

0:01

[music]

0:07

[music]

0:08

>> All right, what is going on, y'all? So,

0:09

we seem to be living in an era where

0:11

there's new apps popping up left and

0:12

right. And I'm someone who loves testing

0:14

out new tools [music] to see if they can

0:15

make me more productive. So, I think

0:17

it's only right that we go over my

0:18

updated MacBook setup for software

0:20

development as well as any other tasks

0:22

that [music] I might be doing on my

0:24

laptop. And hopefully, this video is

0:25

going to give you some inspiration on

0:27

how to set up your own laptop, as well.

0:28

Now, as far as the specs of my work

0:30

machine go, I'm still on the 16-in

0:31

[music]

0:32

M1 Pro MacBook Pro. And this July is

0:34

actually going to be my third-year

0:35

anniversary at my current company. So,

0:37

I'm finally able to upgrade this laptop.

0:39

But as for now, it's been pretty solid,

0:41

and that just goes to show you how good

0:43

the Apple silicon chips are. I mean, an

0:45

M1 Pro still doing fine [music]

0:47

in 2026, that's quite impressive.

0:50

Although, I must say that the 16 gigs of

0:52

RAM has definitely been a bottleneck

0:54

sometimes for me, which is why I like

0:55

testing out my changes on sandbox

0:57

environment rather than on my local

0:59

machine. And sometimes that can be a bit

1:01

of an issue if multiple people are

1:03

wanting to use sandbox at once. Another

1:05

thing I'll be changing with my laptop

1:06

upgrade is definitely [music] the size

1:08

of the machine. The 16-in screen is

1:10

nice. I mean, you get a ton of screen

1:11

real estate, but the 16-in machine is

1:14

proper heavy. And when I compare it to

1:15

the 14-in model, I just I just prefer

1:18

this much more. So, yeah, I'm actually

1:20

going to be downsizing to a 14-in model

1:22

even on my work laptop. Okay, then let's

1:24

get to the actual video, and quickly

1:25

let's go over my system settings so we

1:27

get those out the way. First things

1:28

first, I make sure that all the items

1:30

are hidden on the desktop. I mean, this

1:32

is a must because I accumulate so much

1:35

random stuff here. Then as for the dock

1:36

itself, it stays around the default

1:38

size, but I like bumping up the

1:40

magnification. And of course, the dock

1:42

is positioned at the bottom of the

1:43

screen. If you have the dock on the

1:45

sidebar, then I don't know what you're

1:47

doing. Then as for my hot corners, on

1:49

the bottom left, I have this lock screen

1:51

hot corner. So, whenever I need to go to

1:52

the bathroom or something, I can quickly

1:54

lock the screen. And lastly, this isn't

1:56

really a system setting, but I have this

1:58

app called iStat Menus running, which

2:00

brings these system metrics to the top

2:02

of my MacBook. I like numbers, so it's

2:04

interesting to see how my machine

2:06

behaves under different loads, and it's

2:08

also helpful for my review videos. And

2:10

next, let's go over my coding

2:12

environment, and this is the area where

2:13

I don't like to experiment too much. You

2:15

know, once I get used to an IDE, for

2:17

example, and I switch to a new one,

2:18

[music] then I kind of have to relearn

2:21

how to become productive on that new

2:22

IDE. So, I find that ultimately,

2:26

changing these coding tools can actually

2:27

hold you [music] back. So, as my IDE,

2:29

I'm running VS Code, and this is one of

2:31

them ones that you try to escape, but

2:33

you just can't. A lot of people tried

2:35

switching away from it, but then they

2:37

brought the Claude Code extension into

2:39

VS Code, and now what do you know?

2:40

Everyone's back on VS Code again. I do

2:42

also really like the JetBrains IDEs, but

2:45

when you use them professionally, you

2:46

need a license, and since I don't have a

2:48

huge preference here, I just go with the

2:50

free alternative. And a lot of you have

2:52

been asking for my VS Code theme. Atom

2:55

One Dark theme, which is quite common,

2:57

but I like it as it's not too

2:59

distracting. Then as for the extensions

3:01

in VS Code, I have quite a few of them,

3:03

but let's go over the most important

3:04

ones. And first, we of course got Claude

3:06

Code. We finally got it approved a few

3:08

months back, so that's what I'm on

3:09

currently. I know there's a lot of

3:11

controversial stuff happening with the

3:13

pricing and stuff, but the product

3:14

itself is just too good to ignore at the

3:16

moment. With Claude Code, you of course

3:18

get the chat window, and you can switch

3:20

between different modes, so agentic mode

3:22

or ask mode, et cetera. But what takes

3:24

things to the next level are the

3:26

different that you can create.

3:27

Basically, with these skills, you can

3:29

tell Claude how to handle certain tasks,

3:31

which makes it more efficient. Also,

3:33

with Claude Code, you get a CLI tool, so

3:34

if you prefer working in the terminal,

3:36

then you can also use that. Then another

3:38

extension that's a must-have for me is

3:40

the Vim plugin for VS Code, which

3:42

basically brings the Vim key binds into

3:44

the IDE itself. I think an underrated

3:46

benefit for me with this extension

3:48

specifically is that whenever I connect

3:49

to a remote server and need to edit

3:51

files there, then I'm already familiar

3:53

with the Vim key binds as I use them on

3:55

my local as well. But of course, the

3:57

main benefit here is that it makes

3:58

[music] editing files way faster because

4:00

I can bounce around the file, edit

4:02

multiple lines at the same time, and

4:03

things of this nature. I'm by no means

4:05

am I a Vim expert, but it still does

4:08

speed things up a lot. Then the rest of

4:10

the extensions are kind of language

4:12

specific things, you know, regular stuff

4:13

related to testing, etc. Next we got

4:16

Warp, which is kind of a whole coding

4:17

environment nowadays, but I use the

4:19

terminal feature the most. In all

4:21

honesty, I don't get the hate on Warp. I

4:23

think it's a great product, and recently

4:25

they even open-sourced it. So, I mean,

4:27

you kind of have to respect it. Anyways,

4:29

with Warp, you get a terminal and a

4:30

coding environment in one place, which

4:32

they call the [music] agentic

4:33

development environment. Basically, you

4:35

can run agents in parallel that do

4:37

coding work, but you can also edit the

4:39

files yourself whenever you need to do

4:41

some manual fixes. But yeah, like I

4:42

said, my favorite part is for sure the

4:44

terminal interface. It's just so clean,

4:46

has good auto complete, and also allows

4:49

you to chat to an LLM right then and

4:50

there in the terminal, which makes it so

4:52

that I don't need to switch to ChatGPT

4:54

or something when I'm in the terminal

4:55

and I have a question in mind. Then when

4:57

it comes to running containers locally,

4:59

I don't know many reasons you would use

5:01

Docker Desktop anymore, at least on your

5:03

personal machine. It eats a ton of

5:05

resources, and unless you have your own

5:06

data center, then saving resources where

5:09

possible just seems logical nowadays.

5:11

So, for running containers, I personally

5:13

use OrbStack, but if you're doing

5:14

commercial work, then go with Podman

5:16

instead. OrbStack is basically a

5:18

lightweight version of Docker Desktop,

5:20

and it works pretty much the same as

5:21

Docker Desktop. Podman on the other hand

5:23

is more security-focused with it being

5:25

demonless, and by default runs rootless

5:28

containers. So, in simple terms, pretty

5:29

much all the containers run under your

5:31

user account on your host machine. And

5:33

lastly, on the coding apps, I wanted to

5:35

highlight Bruno, which is, in simple

5:36

terms, a Postman alternative. Basically,

5:39

the story here is that all my teammates

5:40

moved away from Postman, and one of my

5:42

teammates has been using Bruno for a

5:44

long time. So, he already had the Bruno

5:46

templates for a lot of the things that

5:47

we do, which made switching to Bruno

5:49

just make sense. And this collaboration

5:52

stuff is actually one of Bruno's biggest

5:53

selling points, as well as the fact that

5:55

you can easily migrate to it from

5:57

Postman. And yeah, Bruno is also open

5:59

source, which is cool. And the stuff

6:00

that kind of goes hand in hand with my

6:02

coding apps are going to be my

6:03

productivity apps. So this going to

6:05

include all the apps that I use to

6:06

manage the work that I do within my

6:08

coding apps, and I really look at the

6:10

productivity [music] apps as kind of the

6:11

glue that brings everything together.

6:13

First things first, one app that's

6:15

become an absolute must for me here is

6:16

monday.com. This is the platform I use

6:18

to keep track of all my tickets related

6:20

to my portfolio tracking app that I've

6:22

been building on the channel lately.

6:23

Anyways, you probably know monday.com as

6:25

this kind of task management platform,

6:27

but they've built so much more on top of

6:29

that. For example, recently they rolled

6:31

out their Monday AI agents. And yes, I

6:33

know, I know, more AI. Trust me, this is

6:35

an actual useful use case of AI that

6:38

boosts your productivity, and it's not

6:40

just another chatbot feature. You can

6:42

think of Monday agents as kind of like

6:44

interns working for you that live inside

6:46

of the monday.com [music] ecosystem. So

6:48

they have the full context across your

6:50

workspace and have access to your

6:51

projects, flagging delays, writing

6:53

reports, etc. They have a bunch of

6:56

pre-built agents that you can choose

6:57

from, but of course you can also build

6:59

your own agent for your specific needs.

7:01

For example, like I said, I plan all my

7:03

tickets here, and I can assign the

7:04

tickets a label, you know, whether it's

7:06

a task or a bug or something else. And

7:08

my Monday AI agent can assign the ticket

7:10

a priority, as well as points. Also, I

7:12

have my research agent that I can

7:14

delegate research tasks to, for example,

7:16

related to best practices when it comes

7:18

to UI/UX, architecture, and things of

7:21

this nature. So in a nutshell, with

7:23

Monday AI agents, the entire project

7:25

management side of the process is taken

7:27

care of for me, and I can just focus on

7:29

the stuff that actually moves the

7:30

needle, which for me is building the

7:32

actual app. And yeah, that's kind of my

7:34

project management setup currently. So

7:35

if you're looking for a platform for

7:37

managing your projects, then highly

7:38

recommend you give monday.com and Monday

7:40

AI agents a shot. They even offer a free

7:43

trial, so there's literally no risk for

7:44

you. Anyways, I'll leave the first link

7:46

in the description where [music] you can

7:47

sign up for monday.com, and a big thank

7:49

you to monday.com for supporting the

7:51

channel and sponsoring the [music]

7:52

video. The next a bit of a more

7:53

controversial app is going to be my

7:55

browser, and yeah, I'm back on Arc. I

7:57

know, I know. I tried switching to Zen,

7:59

but some stuff just didn't work properly

8:02

on Zen like shortcuts on some web apps I

8:04

was using, and other random stuff like

8:06

this kept popping up. So, eventually I

8:07

just switched back to Arc. Maybe you'd

8:09

be able to configure Zen to fix those

8:11

things, but I don't know. I never took

8:13

the time to do so. Anyways, Arc is

8:15

Chromium-based, and the UI is just by

8:17

far the cleanest I've seen on any

8:18

browser. Also, you get these different

8:20

spaces that you can set up. So, for

8:22

example, you can have your own space for

8:23

your personal stuff where you're logged

8:25

into your personal accounts, and then

8:27

you have another space for your

8:28

professional stuff. Not going to lie,

8:29

Arc in 2026 is probably a big offset

8:32

violation now that they stopped actively

8:34

developing it. They say they'll still do

8:36

security patches whenever needed, but I

8:38

do use Chrome for all my banking and

8:40

other more important stuff. I don't

8:42

know, man. The whole browser situation

8:44

is annoying because I really love the

8:45

user experience on Arc, and I just

8:47

[music] haven't found a replacement for

8:49

it yet. So, if you know some good

8:50

browsers out there, then please let me

8:52

know. The next we still have Raycast,

8:54

which I mainly use for navigating across

8:56

apps, resizing windows, and other stuff

8:58

like if I need to make calculations

9:00

fast, for example. It's really become

9:02

the cornerstone for my productivity, and

9:04

it speeds things up a lot once you get

9:06

used to it. It's kind of the same story

9:08

I have with the Vim extension in VS

9:10

Code, where I'm not a Raycast Pro, but I

9:12

think I still get really good value out

9:14

of it. Apple's improved Spotlight can do

9:16

most of the stuff that Raycast does, but

9:18

in typical Apple fashion, the Spotlight

9:20

isn't as customizable as Raycast. So,

9:22

this comes down to personal preference

9:24

really at the end of the day. But yeah,

9:26

my favorite example I always use for

9:27

Raycast is the quick link feature that I

9:29

use for opening up my projects inside of

9:32

my IDE quickly. So, yeah, all [music] I

9:33

need to do is type in the name of the

9:35

project, and then Raycast is going to

9:36

open it up inside of my IDE. Then I

9:38

still use Notion for all of my

9:40

note-taking related things. I really

9:42

have no issues with Notion, so I just

9:44

haven't felt the need to switch away

9:45

from it. Things simply just work, and

9:47

they keep bringing out new features all

9:49

the time, so I like it. They also have

9:51

agents in the app that help you build

9:53

different dashboards, etc. And many of

9:55

my friends even wipe code apps using

9:57

Notion as a database, which has been fun

9:59

to see. Mind you, these guys don't know

10:01

anything about coding, and they're still

10:02

able to build stuff using Notion. Then

10:04

up next, we have Miro. This is something

10:06

I still use on a weekly basis to this

10:08

day. For example, whenever I'm writing a

10:10

technical spec on a feature I'm working

10:12

on, then I can easily showcase how the

10:14

feature is going to work using Miro, and

10:16

other people can immediately see what

10:17

I'm trying to go for without even having

10:19

to read the whole spec yet. But Miro

10:21

also allows your team to collaborate on

10:23

the same board together. So, for

10:24

example, we host our sprint retros in

10:26

Miro, and everyone can write these

10:28

sticky notes about things that went

10:30

well, what needs to be improved, and

10:31

things of this nature. And yeah, then we

10:33

go over those sticky notes together. So,

10:35

it really is a great tool for teams. For

10:37

running local LLMs, I still use Ollama,

10:40

which basically makes it super easy to

10:41

[music] manage these models on your

10:43

local laptop. Of course, my current

10:45

machine isn't powerful enough to run the

10:47

best models out there, but I like

10:48

testing stuff out every now and then and

10:50

see how the open-source models are

10:52

evolving. If you have like 64 plus gigs

10:54

of RAM, then you could even run a decent

10:56

local model and hook that up to Claude

10:58

Code, and you won't have to worry about

11:00

token usage anymore. So, that's

11:02

ultimately my goal as well. Just imagine

11:04

coding in a plane or a train without

11:06

having an internet connection and still

11:08

having access to AI. And lastly, on the

11:09

productivity app section, we have Slack,

11:11

which I basically use to communicate

11:13

with my teammates. This is pretty

11:14

standard stuff, and I personally prefer

11:16

Slack over something like Microsoft

11:18

Teams. I don't know, Slack just feels a

11:20

little bit less bloated. Then let's

11:22

quickly go over my creative apps, and

11:23

not much has changed here, honestly. But

11:25

these are basically all the apps that I

11:27

use to create [music] these videos here

11:29

on the channel. So, these apps kind of

11:31

have a special place in my heart. As my

11:33

main editing app, I'm still on DaVinci

11:35

Resolve. I prefer it over something like

11:36

Premiere Pro since DaVinci Resolve

11:38

[music] just has this one-time fee

11:39

instead of a monthly subscription. And

11:41

the color grading features are really

11:43

next-level on DaVinci Resolve. Also,

11:45

DaVinci Resolve uses this node system,

11:47

which just feels very natural to me. But

11:49

yeah, with DaVinci Resolve, you can cook

11:50

up pretty much anything you want, and

11:52

even their free tier is really good. You

11:54

only really need the paid tier once you

11:56

upgrade to a proper camera. Next, we

11:58

have Lightroom, which is my go-to app

12:00

for color grading pictures. Blackmagic

12:02

recently introduced a competitor to

12:03

Lightroom inside of DaVinci Resolve,

12:05

which I haven't tried yet, but I might

12:07

move away from Lightroom soon if that's

12:09

good enough. As of right now, though,

12:11

Lightroom just simply is the best app

12:13

I've tried for specifically color

12:14

grading pictures. It's not meant for

12:16

making proper edits like adding text and

12:18

stuff to the photos, but it gives you

12:20

such good tooling for adjusting the

12:22

brightness, colors, masking things, and

12:25

stuff like this that it's really hard to

12:27

move away from. And lastly, for the

12:28

quote-unquote proper photo edits, I use

12:30

Affinity Photo. This is the same case as

12:32

with DaVinci Resolve. So, the reason I

12:34

prefer this over something like

12:35

Photoshop is simply the fact that it

12:37

doesn't require a subscription. You can

12:39

do pretty much all the same stuff as you

12:40

do on Photoshop, but yeah, it's just

12:42

cheaper. But yeah, that's been my

12:44

current MacBook setup for 2026. Let me

12:46

know what you would change, and also let

12:48

me know if you got some inspiration for

12:49

your own setup as well. And as always,

12:51

thank you so much for watching all the

12:52

way to the end, [music] and I'll see you

12:54

in the next one.

12:55

Peace.

Interactive Summary

The video outlines the presenter's updated MacBook setup for software development and creative work in 2026. The creator discusses their hardware choice, preferring the 14-inch model over the 16-inch, and details their essential software stack, including IDE configurations, terminal tools, productivity applications like monday.com, and creative software. The focus is on balancing productivity, efficiency, and cost-effectiveness through open-source or one-time payment alternatives to expensive subscriptions.

Suggested questions

4 ready-made prompts