GoDoc does not support documenting branch code, because go get Does Not Work That WayTM. However, I do need to check the GoDoc result before messing with my git head. Solution?
| Home | Tags | Categories |
I’m the person who like concise, and don’t like the literature style stuffing in lots of irrelevant information to distract you from the main idea. So when I read a book called “No bullshit Java”, I know that’s exactly the kind of writing style I prefer, both reading and writing.
However, that “No bullshit” is kind of stronger than my tolerance. Is there a better phrase that can convey the idea that I don’t like those “bullshit”, but not as strong?
Example usage:
I read a very useful blog, but there are so many distraction there that it is very easy to miss a step. So I’m documenting it again in my (no-)____ style.
I want something more vivid than “concise” (or “distilled”), but not as colorful as “no bullshit”.
I’ve long been enjoying using sfdisk to manipulate my disk partitions. I always use it to,
When my disks are over 2T in size, I can’t use MBR and therefore can’t use sfdisk anymore. I have to use GPT instead. My first GPT partitions was created using GUI tools, but I really hate GUI tools. So this time when I need to partition GPT again, I look for the command line alternative instead.
I’ve long been enjoying using sfdisk to manipulate my disk partitions, especially for creating disk partitions.
This note demonstrates some of what wordpress Markdown is capable of doing.