Programming

17759 readers

835 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

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]

198

Pointers for writing software tutorials (refactoringenglish.com)

submitted 3 days ago* (last edited 3 days ago) by [email protected] to c/programming

32 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 2 days ago (1 children)

The argument is that a beginner might not notice a command falls. The && prevents further execution.

Personally I've seen that happen several times myself. Beginners are just not used to reading the cmd outputs and I can't blame them. There are many CLI tools with awful error reporting out there.

[–] Tamo240 6 points 2 days ago

That's why showing the expected outcome is also very important. It can feel very verbose, but the number of times I've been unclear as to if something worked because the documentation goes on immediately to the next step without demonstrating the success/failure states is extremely frustrating.