Bad terminal habits

・1 min read

Recently I realised how poor my terminal etiquette really is. I seem to run clear just about every other line. I think this is probably the dev's equivalent to the english filler word 'um' - usually used when actually thinking about what to say next.

Do you have any bad terminal habits?

Did you find this post useful? Show some love!
DISCUSSION (8)
 

I have hardcoded one.

alias rm 'rm -rf'
funcsave rm

See, you are not so bad at all :)

 

Ha! That's an interesting one... personally aliases account for a lot of my terminal laziness/bad habits but at the end of the day, they save a few keystrokes!

 

Though I wouldn't recommend my mentioned alias. Still I cannot get rid of it and I personally don't know why Β―_(ツ)_/Β―

 

ctrl-l is a faster clear. I don't use it often, but I do use it.

bad habit which annoys me to see: needlessly cd into a dir when you could tab complete a command for actions on files in that dir.

My bad habit: relying on shell history instead of saving aliases and scripts. I'll write a 300+ character chain of shell commands and not save it anywhere, just ctrl-r to find it in my history... until its a year later and I wonder wtf I did with it.

 

I've piped curl into bash once or twice. It's so convenient, and it's not like I'd have rigorously inspected every line of a downloaded install script anyway.

 

The CLI equivalent of hitting "yes" on an EULA page. =)

Though, less so if it's your URL you're piping to an interpreter.

 
  • Alias all the things. So if I'm in a new env I usually type commands that aren't there due to muscle memory.
  • Not being more deliberate in fine tuning file/dir permissions.
 

Does using cheat.sh/ via the terminal count as 'bad habit'?

Classic DEV Post from Oct 4 '18

Did you know that Oracle owns the trademark to Javascript?

Did you know that Oracle owns the trademark to Javascript?

Jesse Sibley

Do you write code almost every day?

Join dev.to ❀️