I maintain a daily code/admin log; when I make decisions I'll document the reasons for it, excerpts from log files and every measurement I take gets copied to it, little…
I expect software to work the way that I want it too; my tools exist to help me do my work, so they need to work my way.
When I release software, I generally categorize it according to how I care about its use. Example code or anything small (e. g.
I'm letting users POST data to a web application, which is then stored in my database.
I'm currently working on two applications, one a web application and the other a server communicating with various non-browser clients over HTTP, and using Rust for both.
I once created a cross-platform test runner for CLI applications, using an embedded Lua interpreter to execute the application then check its output, filesystem changes, etc.
I use both Bash and ZSH as my shells; I want to keep their configurations as similar as possible, avoid duplicating configuration, and still be able to take advantage of…
I just realized that I never committed my syntax highlighting setup in git or documented it in any way.
See information about the Vim Improvement Plan here. The RulesWe'll start with an empty ~/. vimrc and ~/. vim; the system vimrc will be untouched from installation.