Skip to content

Conversation

@nick-ulle
Copy link
Contributor

This PR adds text for the topic "Document the workflows & code."

Feedback appreciated!

bundling all of the commands in a workflow into a single command.


### Make Workflow Diagrams
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might consider mentioning how workflow diagrams can happen at different "levels", the function level, the script level, the workflow level etc. I often find I have one overarching workflow diagram and then more detailed diagrams of individual steps in the overarching diagram.

inputs, assumptions, outputs, and any pitfalls. If the code is organized into
functions, do the same for each function.

Comments are a good way to document code, but some programming languages also
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would differentiate between using comments to state in plain english what a given line of code is trying to accomplish and documenting the purpose of a script or function at the top of it. While these two things are related, they are often useful in different settings and doing one does not absolve you from doing the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants