Me, every time I want to do a symlink.
Every. Single. Time.
QT n0x13: I have been in the IT industry for almost 2 decades and it has been 0 days since the last time I had to look up the order of some function call. If you’re starting out in tech and feel bad for looking everything up: don’t. Everybody googles everything
@ColinTheMathmo @neil that’s a cool mnemonic
Mine is; which argument could be optional? The source could not, so it goes first
@ColinTheMathmo @neil You could add clock_gettime to that - the advantage generally is it always returns the same format struct timespec (with ns) for all clock types.
@penguin42 Not one I've ever used ... interesting. Thanks.
CC: @neil
@neil It always matches copying, whether it's ln vs cp; or symlink() vs memcpy().
For me, it helps to remember that its like the cp command. cp <from> <to> and that <to> is the place where the filesystem is modified, and <from> is the place where it isn't. that helps me :ablobderpy:
ln -s <from(unmodified file )> <to(modified file)>
@neil
I'm with you, Neil. It means that your memory is being used with far more complex things.
Correction: Not completely with you because I don't google, I searx everything.
@manuelcaeiro I have an instance of searx, but I tend to use DDG
@neil every time. Remembering which is source and which is the link is impossible. No one does.
I look it up every time.
@neil
Used to be me, until I switched to Fish shell, which now hints me into the right order based on past executions.
@neil
Fish is, yeah! Big fan
@neil I agree entirely with the sentiment, but thought I would share my mnemonic for the symlink.
The number of things you want to set to point at the target is variable, so you put the target first, and then can list as many things as you like to point to it.
That's at least one thing I don't have to look up.
Now Time Functions in Python ... I even made a diagram for them:
https://www.solipsys.co.uk/new/TimeFunctions.html?UC27MN