Create a new key shortcut

alt + shit + ;

send escape sequence + "."

find . -printf "%T@ %Tc %p\n" | sort -n

printf arguments from man find:

%Tk: File's last modification time in the format specified by k.

@: seconds since Jan. 1, 1970, 00:00 GMT, with fractional part.

c: locale's date and time (Sat Nov 04 12:02:33 EST 1989).

%p: File's name.

Add this to your user's ~/.gitconfig under [alias] to make it globally available:

lsch = "!f() { git diff --name-status -r "HEAD~$1"; }; f"

You can invoke this to retrieve all affected files in the last 7 commits like so:

$ git lsch 7

this is insane

31
down vote
accepted

Both forms are valid. However, for an API, I would recommend the second form. The reason is that it gives you a path for expansion of your API.

For example, if you have an API getUsersInGroup which returns an array of user objects, and later you decide you want to include, say, some aggregate statistics about the users being returned, there's no easy way to do that without breaking existing clients (or including lots of redundant data in each user object). If you use an object, you simply add another field to the object which is silently ignored by clients on a previous version of the API.

In short, try to avoid top-level primitives wherever possible in your API, and you'll find it easier to expand in the future.

interessant, ça a l'air sympa comme job!

TIL : strings command