dev-cheatsheets

dev-cheatsheets

A collection of code snippets and CLI guides for quick and easy reference while coding

Dev Cheatsheets

A collection of code snippets and CLI guides for quick and easy reference while coding

Preview

Screenshots of the website:

sample cheatsheets sample cheatsheets shell

Contents

An idea of what to expect in this guide.

  • Languages - Syntax and functions across languages. Including how to operate on an array in JavaScript, available Jekyll filters and common and specialized uses of Markdown. Most code snippets here are only one line.
  • CLI tools - Terminal commands and flags that are useful to me, including listing what they are, what they mean and an example of how to use them. Especially using versatile/complex tools like sed or git.
  • Help - Portions of the man pages, to make it easier to read about command in the browser without going through the entire manpage on the terminal.
  • Resources - There are some details for external resources.

The idea for the first two types is that the code here is generic. There are placeholder values or made-up use-cases for demonstration. You'll need to change them for your own situation.

See also my Code Cookbook project. It has Recipes which structured similarly to Cheatsheets here, except that the Recipes are usually longer blocks of code to be copied and they focus on real-world use-cases.

Documentation

To set up and run this project (or a fork), see the project docs:

Contributing

Contributions are welcome. See instructions:

License

Released under MIT by @MichaelCurrin.

This site has content written and owned by me. Except where external links are provided to the original code author or website. Or if someone contributes a PR with their own content.

If use a significant portion of it in your own repo, you must include a copy of this license in your repo. Please link back to the original repo in your own repo, or blog post, etc. that mentions this.

Forks will by default include a copy of the license.

If you adapt this repo not intended to contributing back from your fork, then you need to add a copy of the orignal license as LICENSE-source and then you only need your own name only in LICENSE.