2 hours ago · Tech · hide · Fediverse post

Whenever possible, I avoid using abbreviated forms of commands and commandline flags. I see them all the time in readmes, in blog posts, in pairing sessions. When I do not know what is being abbreviated: I can miss the author’s point, and I can get distracted in my attempt to follow along. Custom command aliases also function as abbreviations, and I often feel the same way about them. With NPM, install is often shortened to i: npm i glob@^14.0.0 Anyone with experience using package managers can adapt to this shortform version. Meanwhile, someone just learning, who doesn’t know what a package manager is, or what glob@ could mean, or what npm is, may need a few moments to think through it, or a lot of expository information about the purpose of this command. Writing out install instead of i is remarkably helpful for the someone just learning. Git has many unholy subcommands, none of which can be abbreviated.1 Its commandline flags, though, are often abbreviated: git checkout -p -- spec/…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town