C, Embedded

How I ended up writing a new real-time kernel
Unit-testing (embedded) C applications with Ceedling: let's write C code that doesn't suck
Object-oriented techniques in C: my experience on the topic, plus an utility for autogeneration of boilerplate code
Visualizing the Heap on Embedded Devices, and getting highly efficient heap manager for memory-constrained devices
TNeo RTOS: well-formed and carefully tested real-time kernel for 16- and 32-bit MCUs
Bmp writer: C module for painless generation of bmp screenshots (mainly for embedded usage)
DFTrig: C module for calculation of trigonometric functions by lookup table, table generator included.
Indent with tabs, align with spaces

Vim

Vim: convenient code navigation for your projects: thorough explanation of advanced Indexer + Vimprj usage
Vim-Indexer: plugin for Vim that provides painless transparent tags generation
Vimprj: plugin for Vim that helps you manage options for multiple projects
Quit another window: plugin for Vim that helps you close arbitrary window without bothering to leave the current one

Docker: Printable Quick Reference (Cheat Sheet)

I use Docker, but not often enough to memorize even basic Dockerfile instructions and CLI commands. After all I got so annoyed by being unable to quickly sketch some Dockerfile or to do something with the existing containers occasionally, so I decided to write a concise cheat sheet which I can print once and constantly keep on my desktop:

(click the thumbnail to download pdf)

I wasn't satisfied with the existing Docker cheat sheets which I've come across, since I find them more cute than useful; for example, this or this one.

The appearance of the card is largely inspired by the GDB Quick Reference: I was using it for a long time already, and it was a very pleasant experience. It is clear and concise. Personally, I just print it on both sides of a single A4 sheet.

The card is written in LaTeX. Not everything was smooth. Probably that's because my LaTeX-fu is too weak, but in my opinion, LaTeX shines best for the cases when the user believes that LaTeX knows better. This was not the case here, since I had to pack lots of stuff in two pages, and I had to fight with LaTeX a lot, rather than embracing it. If anyone knows how to structure the document better, your comments are appreciated.

And in general, your contributions are welcome: fork it at GitHub!

License: MIT.

docker, cheat-sheet, programming, latex

Discuss on Hacker News: Vote on HN
Donate

Discussion

Jobin Jacob Kavalam, 2018/03/04 04:10

I use the quick reference often. It's awesome !

Dmitry Frank, 2018/03/04 09:52

Cool, glad it helps!

Vasyl, 2018/04/19 13:15

Hello Dmitry,

Thanks for the quick reference.

According to http://docs.docker.com/storage/bind-mounts/#choosing-the--v-or---mount-flag it is preferred to use –mount flag. How do you feel about it?

K. East, 2018/10/31 17:31

This is excellent. Refreshing actually - I am so tired of the overly graphical, information sparse, cheatsheets that seem to be the current trend. Can't beat an information dense, concise, LaTeX-based sheet like yours. Thank you very much.

Dmitry Frank, 2018/10/31 18:50

Thanks! Happy it's helpful.

Nicholas, 2019/12/10 11:06

Perfect, thanks for taking the time to put this up. It's now on the side of my desktop tower!

Theo, 2020/03/11 16:46

Excellent presentation. Especially like concise formatting. As a newbie, I call it a LEARNING sheet. Thank You!

Dmitry Frank, 2020/03/11 19:42

Glad it helps, thanks for the comment!

Vasiliy, 2020/05/04 07:27

Thank you, its very useful!

Prashant Dawar, 2021/08/05 06:53

Reference like presented here are gems.

Real name:

E-Mail:

Website (optional):

Enter your comment (please, English only). Wiki syntax is allowed:

Please fill all the letters into the box to prove you're human.

 __  __   ___    ___   ____   _____
 \ \/ /  / _ |  / _ | / __ \ / ___/
  \  /  / __ | / __ |/ /_/ // /__  
  /_/  /_/ |_|/_/ |_|\___\_\\___/

Please keep this field empty:

Subscribe to comments