Recent searches
Search options
One way to improve your team's productivity and to document your project's processes is to give the command line commands you use names that are descriptive and if possible, consistent across projects.
This blog post was inspired by a recent discussion started by @mhoye about using make to give often run commands easier to remember names.
https://hamatti.org/posts/give-your-commands-consistent-names/
@hamatti a very, very powerful community-accessibility addition to that idea is to say in the documentation up front, “if these commands don’t work for you that’s a bug and we want to hear about it”.
A set of copypasted commands that don’t work feels like the person failing; a two word command that doesn’t work feels like the program failing. They’re the same thing but only one feels like something you have permission to file a bug about.
@mhoye Very well put!