If you're using a GUI, that means whatever you're doing you're not doing a lot of it, since you don't need to automate it. I would expect a world-class enterprise engineer to be able to automate most tasks, and from that they would be very comfortable with the command line.

Can you do everything with a GUI that you can on a command line? Yeah probably, if the developer is at all the features properly. Can you automate it easily? No not at all. So the more you do something the more you tend to want to deal with the vocabulary of the command line because it's more expressive and allows for automation.

I will die on this hill!

[–] nottheengineer@feddit.de 2 points 1 year ago

Documentation too. Frontends change all the time, but CLI tools usually don't, so you can usually rely on old documentation. But have you ever tried googling how to do something in MS office, found and article from half a year ago and found that none of the things it mentions exist anymore? It's ridiculous how much time people waste trying to figure out stuff multiple times because it changes so much.

[–] Venomnik0@lemmy.world 1 points 1 year ago (1 children)

Honestly, some things can be done faster/as fast on GUI. So really just use whatever increases your productivity.

[–] MangoPenguin@lemmy.blahaj.zone 1 points 1 year ago

IMO GUIs are always faster when it's something you've never used before, or use very infrequently.

CLI is better if you're used to the task you're doing, or automating things. But for infrequent tasks looking up the commands (or looking at old notes to find it) is very slow and rather annoying.

[–] BravoVictor@programming.dev 0 points 1 year ago (1 children)

Pshaw! CLI and GUI? Real network engineers make hand crafted API calls!

[–] andrew@lemmy.stuart.fun 1 points 1 year ago

https://xkcd.com/378/