500 chars is an awful lot.
140 chars is too little (though I have long admired https://twitter.com/MicroSFF writing entire stories in single tweets). 500 chars is enough for me to dither over what I've written.
140 chars enables you to write and edit in a short period. That said, I'm forced to ask 'which abbrevation / grammar fault is least irritating?' regularly.
miniblog.
Related Posts
It seems really odd to me that git uses 'cached' terminology for staging. For example, `git add somefile.rs; git diff --cached`.
Caching implies state that you don't mind losing. There's very little state I want to lose in version control!
GNU Make defaults to a single worker, and newer build tools (e.g. ninja) default to the number of physical CPUs. I wish there was an option for 'leave me a little bit of my machine to do stuff'.
I'm experimenting with syntax in examples. I don't really like Rust's `assert(inc(1) == 2)` syntax, I find it a little distracting.
I'm trying `inc(1) //-> 2`. The comment is rendered differently, and there's nothing before the sample code. What do you think?

