this post was submitted on 18 Aug 2023
35 points (92.7% liked)

Programming

17669 readers
171 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
35
What helps people get comfortable on the command line? (jvns.ca)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/programming
40 comments fedilink hide all child comments
 

Sometimes I talk to friends who need to use the command line, but are intimidated by it. I never really feel like I have good advice (I’ve been using the command line for too long), and so I asked some people on Mastodon:

if you just stopped being scared of the command line in the last year or three — what helped you?

This list is still a bit shorter than I would like, but I’m posting it in the hopes that I can collect some more answers. There obviously isn’t one single thing that works for everyone – different people take different paths.

I think there are three parts to getting comfortable: reducing risks, motivation and resources. I’ll start with risks, then a couple of motivations and then list some resources.

I'd add ImageMagick for image manipulation and conversion to the list. I use it to optimize jpg's which led me to learn more about bash scripting.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

Electroshock. I that is too "harsh" or "inhumane" then a cheat sheet.

At the end of the day the command line is a tool that you are using to do something. If I have to google "how to commit file changes to bitbucket using the command line", I'm probably just going to use whatever GUI tool is available. Or I may do something really silly like manually copy the changes into bitbucket's web interface. If I had a cheat sheet easily available, then I would just look at that. The rest is just practice and repetition.

Just throwing this out there. It really helps if everyone on the team is comfortable enough to ask for help. If you are a manager, it's your job to create this kind of environment. And if you see some newbie data analyst that just learned python and is intimidated by a bunch of software engineers copying a bunch of changes into bitbucket's web interface. Don't tell them that they are doing it wrong or they don't know what they are doing. Just say "hey, there is a much easier way to do that" and then show them. If a tool makes somebody's job easier then they will use it.