• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

a nice tip from Mark dalgleish: https://twitter.com/markdalgleish/status/1339863859469955072?s=20

I have no idea where to put this, let me know if you have an idea

DNS preanalyze is a way to reduce DNS analyze time:

<meta http-equiv="x-dns-prefetch-control" content="on" />
<link rel="dns-prefetch" href="http://www.baidu.com" />

cargo new already creates a structured project (folders, etc...).
Wouldn't be it nice to create a section/page/idioms/ devoted to best practices of code organisation? For example how to struct modules, crates, workspaces...how to refer one crate from another or one module from another.
What do you think?

MDN URL: https://developer.mozilla.org/en-US/docs/Glossary/hash

What information was incorrect, unhelpful, or incomplete?

Hash definition includes incorrect glossary link to HMAC's.
Incorrectly links to: https://developer.mozilla.org/en-US/docs/Glossary/HMAC's
should be: https://developer.mozilla.org/en-US/docs/Glossary/HMAC

Specific section or headline?

https://github.c

Currently, we manually append the params to the url / query string using urljoin. Instead, we can send the query params in as a dictionary