8 Common CLI Mistakes Programmers Make

In today's video we are looking at 8 common mistakes that programmers often make. If you are a beginner or experienced developer, the CLI can be a scary place. One single mistake can lead to a lot of damage.
However, we have you covered! We will help you navigate and use the CLI safely by avoiding these common CLI mistakes that programmers make.
Let us know in the comments what CLI mistake you made in the past.
LINKS
-----
Try Warp now for FREE 👉 bit.ly/warpdotdev
Twitter 🐦
/ warpdotdev
TikTok 📱
/ warp.dev
TIMESTAMPS
---
0:00 Intro (Sunglasses 😎)
0:18 Neglecting to update your packages.
1:22 Failing to back up data
2:23 Unintentionally overwriting files
3:15 Using sudo too often
3:55 Not knowing how to use options or flags
4:41 Not using git commands correctly
5:24 Mistyping your filepaths
6:20 No 8 (Are you skimming this video!?)

[@dopetag]

4:24 how do you display flags like this after tabbing? some plugin?

[@CodingWithLewis]

Learning to use AI tools is so important. When AI replaces me, then I will go on vacation.

[@Sun_Seeker]

There is no “learning” AI. The most powerful AI tools are closed source so there is nothing you can do to learn how it works. The only open source AIs like llama aren’t even that worth using because they lack they aren’t very reliable.

[@CaptainDouchie]

How do i make the terminal open up directly in the path of the working directory of the project im working on in VScode??

[@warpdotdev]

Which CLI error do you run into all the time?

[@Cookiekeks]

Why would I use this terminal when it's not even open source? What benefits does it give me over alacritty? Why is this all so corporate, who funds this?

[@nobytes2]

no one is forcing you to use it, freedom!