I modify “cd” so that every time I change directory it calls “ok” and thus I get a pretty print of the most useful 1-line commands for that folder. I have .ok i

I modify “cd” so that every time I change directory it calls “ok” and thus I get a pretty print of the most useful 1-line commands for that folder. I have .ok in all my projects. Some of those have makefiles, some have cake, some have grunt, some have npm scripts. Many are pure documentation folders (books etc). ok isn’t primarily a build system or a task runner, it’s a folder profile. Asking “what can x do that y cannot do?” invokes the Turing tarpit. A better question is “why is it more pleasant to use x with or instead of y?” ...particularly since they can be used together.